UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I was working with the Image Magick(v.6.0.6-2) program that came with Ubuntu5.04 and had saved several images. Then I noticed it was due for an upgrade so I successfully upgraded Image Magick using the synaptic package manager. Afterwards I noticed that I couldn't open Gimp or even my terminal window- it would try to load for a few seconds but then just quit. Not knowing what was going on I logged off and rebooted. When I tried to log back in I got this message:
Your session only lasted less than 10 sec. If you have not logged out
yourself this could mean that there is some installation problem or that
you may be out of diskspace. Try logging in with one of the failsafe
sessions to see if you can fix this.
I shouldn't be running out of disk space as I've only used about 2 1/2G on a 4G hard drive. I'm running on a intel 686 with a 400MHz Celeron processor and 190MB of RAM. Clicking on the view details window I get this:
/etc/gdm/Presession/Default:Registering your session wtmp and utmp
/etc/gdm/Presession/Default: running: /usr/bin/x11/sesreg -a -w/var/
log/wtmp -u /var/run/utmp -x "/var/lib/gdm/: 0.xservers " -h " " -1 ":
0 " " ["My log in name"]
etc/gdm/xsession: beginning setup
usr/bin/dbus -launch: error while loading shared libraries: libSM.so.6:
cannot open shared object file: No such file or directory.
I googled libSM.so.6 which gives me all the rpm resources but none for ubuntu or debian. The imagemagick site mentions some security problems if GDM is installed on SuSe. I'm not that familiar with the command line yet to trouble shoot this so any suggestions on how to approach this in the failsafe mode would be appreciated - the more explicit the better.