Comment 54 for bug 136529

Oh well, it seems my problem regarding the not-starting GNOME session is only the tip of the iceberg. Remember you told me to remove gdm from being automatically started at boot time jtholmes? Well, I did this yesterday and after it didn't work out the way it should, I restored the settings with "update-rc.d gdm defaults". Afterwards I didn't boot the kernel 2.6.24-3 anymore - until now. It seems that the running order of the programs at boot time has changed now (which isn't a problem at all) and now cupsys gets loaded before gdm. That shouldn't be a problem, only that now my systems stops booting when trying to load cupsys and GDM doesn't show up anymore. So I switched to a console, only to find out that the cups daemons are obviously running, but so is also the S20cupsys script (which should have long exited by now).
Okay, I thought that maybe it's all the fault of the printer service and deactivated it (via "update-rc.d -f cupsys remove") and rebooted my machine. GDM started up then, I logged in - and still the GNOME session just stops loading after a few seconds. So I switched to a console, did "ps -e" - only to see that now the NFS autostart script (S20nfs-kernel-service) stopped responding. The nfsd daemons were loaded, but the script didn't exit. So I also deactivated nfs, only to see that after a reboot it showed the same behaviour with the Samba daemons. And now I'm really at a loss here. To me it seems that the system just doesn't boot completely and maybe that's exactly the problem with my not-starting GNOME session. I don't know for sure though - for that I'm just too unexperienced.