On Tuesday 10 December 2013 07:27 AM, Ralf Mardorf wrote:
On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote:On Mon, 2013-12-09 at 19:08 +0000, Tom H wrote:The Ubuntu-created grub.cfg cannot be blamed for a GDM problem. If GDM is being launched, grub's job has been done many seconds ago.This seems to be true here, but you're mistaken, a boot option could still cause something when a DE session already is running, e.g. "threadsirq", "noatime", sure, "noatime" won't brake something, but "threadirqs" at least could slow down GUI performance, assumed it's a lowlatency kernel.PS: Let alone options such as e.g. "single" ;).
Thank you all for your assistance!After reading your posts, I decided to tentatively look at causes other than grub. I searched the gnome.org mailing archives and googled the issue some more. The solution that worked for me was to run check the debian boot partition with gparted (e2fsck -cfkp). While I did not note any addition bad sectors, etc. the issue seems to have been resolved.
Thanks again, Kailash