Re: gdm3 issue

2013-12-18 Thread Tom H
On Fri, Dec 13, 2013 at 6:08 PM, Ralf Mardorf wrote: > On Fri, 2013-12-13 at 16:49 +, Tom H wrote: >> On Fri, Dec 13, 2013 at 4:25 PM, PaulNM wrote: >>> On 12/13/2013 10:03 AM, Tom H wrote: On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf wrote: > On Tue, 2013-12-10 at 02:25 +0100

Re: gdm3 issue

2013-12-15 Thread Tom H
On Fri, Dec 13, 2013 at 4:35 PM, Ralf Mardorf wrote: > On Fri, 2013-12-13 at 11:25 -0500, PaulNM wrote: >>> >>> The "single" kernel cmdline option would never launch GDM. >> >> I believe that was his point, and the reason for the smiley ;). >> Most would say preventing something from happening is

Re: gdm3 issue

2013-12-13 Thread Reco
Hi. On Fri, 13 Dec 2013 19:08:07 +0100 Ralf Mardorf wrote: > > Except that "single" doesn't make GDM fail, it doesn't even launch it. > > It's not the same thing. > > The result is the same, you won't end up with the option to launch > Iceweasel by a launcher on the GNOME desktop ;). It was jus

Re: gdm3 issue

2013-12-13 Thread Ralf Mardorf
On Fri, 2013-12-13 at 16:49 +, Tom H wrote: > On Fri, Dec 13, 2013 at 4:25 PM, PaulNM wrote: > > On 12/13/2013 10:03 AM, Tom H wrote: > >> On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf > >> wrote: > >>> On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 19:08

Re: gdm3 issue

2013-12-13 Thread Tom H
On Fri, Dec 13, 2013 at 4:25 PM, PaulNM wrote: > On 12/13/2013 10:03 AM, Tom H wrote: >> On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf >> wrote: >>> On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: On Mon, 2013-12-09 at 19:08 +, Tom H wrote: > > The Ubuntu-created grub.cfg

Re: gdm3 issue

2013-12-13 Thread Ralf Mardorf
On Fri, 2013-12-13 at 11:25 -0500, PaulNM wrote: > > The "single" kernel cmdline option would never launch GDM. > > > > I believe that was his point, and the reason for the smiley ;). > Most would say preventing something from happening is a form of > affecting it. Correct, that's why I was thin

Re: gdm3 issue

2013-12-13 Thread PaulNM
On 12/13/2013 10:03 AM, Tom H wrote: > On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf > wrote: >> On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: >>> On Mon, 2013-12-09 at 19:08 +, Tom H wrote: The Ubuntu-created grub.cfg cannot be blamed for a GDM problem. If GDM is bei

Re: gdm3 issue

2013-12-13 Thread Tom H
On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf wrote: > On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: >> On Mon, 2013-12-09 at 19:08 +, 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 secon

Re: gdm3 issue

2013-12-13 Thread Tom H
On Tue, Dec 10, 2013 at 1:25 AM, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 19:08 +, 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,

Re: (SOLVED) Re: gdm3 issue

2013-12-10 Thread Zenaan Harkness
On 12/10/13, Kailash Kalyani wrote: > 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 +, Tom H wrote: The Ubuntu-created grub.cfg cannot be blamed for a GDM problem. If GDM is being la

Re: (SOLVED) Re: gdm3 issue

2013-12-10 Thread Ralf Mardorf
On Tue, 2013-12-10 at 17:31 +0530, Kailash Kalyani wrote: > 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. I didn't think of it, but (somebody e

(SOLVED) Re: gdm3 issue

2013-12-10 Thread Kailash Kalyani
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 +, 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.

Re: gdm3 issue

2013-12-09 Thread Ralf Mardorf
On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 19:08 +, 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,

Re: gdm3 issue

2013-12-09 Thread Ralf Mardorf
On Mon, 2013-12-09 at 19:08 +, 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 alre

Re: gdm3 issue [boot loader digression]

2013-12-09 Thread Tom H
On Mon, Dec 9, 2013 at 5:04 PM, Neal Murphy wrote: > > Grub 2 is, as far as I know, still broken. This is the kind of statement that makes me laugh, this case or NM's or... 1) The silent majority of grub2 users have no problems. 2) File a bug report if grub2 (or any other package) fails for you

Re: gdm3 issue

2013-12-09 Thread Tom H
On Mon, Dec 9, 2013 at 2:30 PM, Kailash Kalyani wrote: > > Here's the boot.cfg (attached). Since 10_linux has Debian entries, it's Debian that created this grub.cfg. But it might be that the Ubuntu grub.cfg is the one that's loaded from the MBR. -- To UNSUBSCRIBE, email to debian-user-requ...@

Re: gdm3 issue

2013-12-09 Thread Tom H
On Mon, Dec 9, 2013 at 11:06 AM, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 15:15 +0530, Kailash Kalyani wrote: >> >> The issue started when I removed old linux images from Ubuntu which is >> on another partition. That resulted in a grub update from ubuntu and >> since then I've had this issue. >

Re: gdm3 issue [boot loader digression]

2013-12-09 Thread Neal Murphy
On Monday, December 09, 2013 06:06:24 AM Ralf Mardorf wrote: > On Mon, 2013-12-09 at 15:15 +0530, Kailash Kalyani wrote: > > The issue started when I removed old linux images from Ubuntu which is > > on another partition. That resulted in a grub update from ubuntu and > > since then I've had this i

Re: gdm3 issue

2013-12-09 Thread Kailash Kalyani
On Monday 09 December 2013 08:47 PM, Ralf Mardorf wrote: menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-686-pae' --class debian --class gnu-linux --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd1,msdos3)'

Re: gdm3 issue

2013-12-09 Thread Ralf Mardorf
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-686-pae' --class debian --class gnu-linux --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd1,msdos3)' search --no-floppy --fs-uuid --set=root ddea8c2f-f4b3-4c3

Re: gdm3 issue

2013-12-09 Thread Kailash Kalyani
On Monday 09 December 2013 07:35 PM, Ralf Mardorf wrote: On Mon, 2013-12-09 at 19:25 +0530, Kailash Kalyani wrote: Thanks, I tried that using update-grub2 from my Debian install. That did not resolve the issue :( JFTR did you install GRUB by Debian. If not, at least copy the /boot/grub/grub.cf

Re: gdm3 issue

2013-12-09 Thread Ralf Mardorf
On Mon, 2013-12-09 at 19:25 +0530, Kailash Kalyani wrote: > Thanks, I tried that using update-grub2 from my Debian install. That > did not resolve the issue :( JFTR did you install GRUB by Debian. If not, at least copy the /boot/grub/grub.cfg to the Ubuntu install. > I think it's a PAM issue with

Re: gdm3 issue

2013-12-09 Thread Kailash Kalyani
On Monday 09 December 2013 04:36 PM, Ralf Mardorf wrote: On Mon, 2013-12-09 at 15:15 +0530, Kailash Kalyani wrote: The issue started when I removed old linux images from Ubuntu which is on another partition. That resulted in a grub update from ubuntu and since then I've had this issue. So the

Re: gdm3 issue

2013-12-09 Thread Ralf Mardorf
On Mon, 2013-12-09 at 15:15 +0530, Kailash Kalyani wrote: > The issue started when I removed old linux images from Ubuntu which is > on another partition. That resulted in a grub update from ubuntu and > since then I've had this issue. So the answer already seems to be there. Ubuntu did likely au

gdm3 issue

2013-12-09 Thread Kailash Kalyani
Hi All, Issue: This issue started the day before. I log into Debian and instead of a login screen I get a message about gnome-fallback session failing to load and an alert asking me to contact the administrator. The issue started when I removed old linux images from Ubuntu which is on anothe