[Gutsy] Worked for me - info/Gnome

NoOp glgxg at sbcglobal.net
Mon Oct 15 22:42:20 UTC 2007


Following the gutsy updgrades a few days ago all went well with the
exception of my A21M Thinkpad laptop. On reboot I would get the gdm
splash & after a considerable amount of time I would eventually get the
Gnome background, but no Gnome panels. I could ssh into the machine & do
just about anything except run gnome.

Booted into recovery mode and find that I'm getting exception Emask 0x0
errors:

<https://bugs.launchpad.net/bugs/+bugs?field.searchtext=Emask+0x0&search=Search+Bug+Reports&field.scope=all&field.scope.target=>
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133666
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129709
etc., etc.

Check the hard drive & all is well via fsck smartctl etc. So I try doing
a apt-get install --reinstall ubuntu-minimal ubunutu-standard
ubuntu-desktop & run into:

Updating fontconfig cache...
Bus error
dpkg: error processing ttf-opensymbol (--configure):
 subprocess post-installation script returned error exit status 135

Try purging & reinstalling ttf-opensymbol blah.

The only way that I *finally* got everything back to normal was to:
mv .gnome .gnome_old
mv .gnome2 .gnome2_old
mv .gnome2_private .gnome2_private_old
mv .gconfd .gconfd_old

then reooted and all was well again. Of course did the standard sudo
apt-get update etc after reboot to make sure all stick.

I've no idea what initially went wrong, but it was only after renaming
the above (via mv) that all returned to normal. Strange but true... so I
thought I'd pass that along in case anyone else runs into the same problem.





More information about the ubuntu-users mailing list