Ubuntu – How to install 32-bit libraries when they keep having uninstallable dependencies

Couldn't install doesn't mean dpkg didn't try and give up half-way

There's nothing complicated about it. Observe this re-enactment:

$ sudo dpkg -i --force-architecture google-earth-stable_current_i386.deb
...
Errors were encountered while processing:
 google-earth-stable:i386

$ dpkg --list | grep google-earth
iU  google-earth-stable:i386               6.0.3.2197-r0                        

The iU tells you that you wanted this package i-nstalled, but dpkg couldn't configure it, so it was leaving it U-nconfigured, waiting for you to fix it. The error you got dpkg: error processing google-earth-stable:i386 (--configure): dependency problems - leaving unconfigured tells you as much in simpler language.

dpkg must be explicitly told to remove a failed install

Just tell dpkg to not bother and remove the package:

sudo dpkg --remove google-earth-stable:i386

And then try installing the 64-bit package again.

Synaptic and apt-get don't care about one-off debs

You got nothing out of Synaptic or apt-get because they aren't aware of your problem. They concern themselves primarily with packages available in the repositories, which you manage through them. They are higher level tools which use dpkg under the hood, but don't care about any problems you create with dpkg unless it concerns them. If you tried to install any package, or Google Earth 64-bit if it was in some repository, with Synaptic or apt-get, they would definitely have whined about it.

Other helpful references

• The .deb file name and package name are usually different. You need the package name to do any operations with dpkg. Use dpkg --list | grep xxxxx where xxxxx is a small part of the file name sure to be in there, like google or earth.

• See this answer for a great explanation of all the two-letter dpkg status flags.

You can recover or set root password without knowing the current one by starting mysql without loading the grant-tables.

Please note the $ in the commands. This is specifying the terminal prompt you see when typing in the command. It's showing it's a line of text, but and actual typed terminal command. The "mysql>" prefix is also a prompt. That is the prompt you get when running mysql interactivately.

This is the cli (command line) to do this:
(Be sure to stop the current server before performing the steps. Only one server can run at a time.)

$ sudo mkdir /var/run/mysqld; sudo chown mysql /var/run/mysqld
$ sudo mysqld_safe --skip-grant-tables&

Now you can log in as root without a password and perform all commands, as in this case, set the root password as root.

$ sudo mysql --user=root mysql

This is the set root password that you will perform inside mysql if you have MySQL 5.6 or below:

mysql> update user set Password=PASSWORD('new-password') where user='root';
flush privileges;

In MySQL 5.7 or above

mysql> update user set authentication_string=PASSWORD('new-password') where user='root';
flush privileges;

From there, quit (kill the running msqld) mysql and start it as normal.

Notes on starting and stopping the mysql service:

Stop mysql:

$ sudo service mysql stop

Start mysql (normal):

$ sudo service mysql start

Kill the temporary mysql safe mode session:

$ sudo mysqladmin shutdown