Re: gdm3 issue
On Fri, Dec 13, 2013 at 6:08 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Fri, 2013-12-13 at 16:49 +, Tom H wrote: On Fri, Dec 13, 2013 at 4:25 PM, PaulNM deb...@paulscrap.com wrote: On 12/13/2013 10:03 AM, Tom H wrote: On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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. 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 ;). 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. 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 just an ironical explanation what a single boot option could cause and it's too funny, since the option is called single. You can change init level once in runlevel 1 so this situation has nothing to do with GDM failing. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SySAk_MWDMqefUABAkgHQhX195v+8ZQR-fPX=61xup...@mail.gmail.com
Re: gdm3 issue
On Fri, Dec 13, 2013 at 4:35 PM, Ralf Mardorf ralf.mard...@alice-dsl.net 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 a form of affecting it. Correct, that's why I was thinking about GRUB2, when the OP mentioned that an Ubuntu kernel was removed, before the issue appeared. I don't know how the auto-thingy is set up, what options will be add and how they affect or don't affect a Debian install. single for sure would get a name such as Single or Recovery for the menu entry, but there are or sure other options that could prevent GDM from running. 1) grub-mkconfig won't change the kernel cmdline options, unless /etc/default/grub has been edited. 2) If grub's controlled from within Ubuntu (as it seems to be), the Debian entries will be option-less if there's no grub.cfg on the Debian install or with the options in /etc/default/grub within the Debian install if there's a grub.cfg on the Debian install. 3) This isn't about GDM being prevented from running; it's about GDM failing after being launched. 4) What kernel option is there that: a) If it's added to the kernel cmdline, GDM crashes. But if it's removed from the kernel cmdline, GDM starts normally. Or b) If it's added to the kernel cmdline, GDM starts normally. But if it's removed from the kernel cmdline, GDM crashes. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxq+apome1uc_zkhqzr0rwv_wdq0aakverifunrbiv...@mail.gmail.com
Re: gdm3 issue
On Tue, Dec 10, 2013 at 1:25 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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, 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. ! I've never heard of the threadsirq kernel cmdline setting. noatime is a filesystem setting not a kernel cmdline one. Whether a kernel's low-latency or not isn't a grub concern. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szzmxc979d2-8ypgh4uurldz0on18cf7aqmb5tezx6...@mail.gmail.com
Re: gdm3 issue
On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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. 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 ;). The single kernel cmdline option would never launch GDM. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SyO4f4C=sepyajsqeuuyh7yez6pp31k08g0gsl9zp4...@mail.gmail.com
Re: gdm3 issue
On 12/13/2013 10:03 AM, Tom H wrote: On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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. 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 ;). 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. -PaulNM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52ab3505.5080...@paulscrap.com
Re: gdm3 issue
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 thinking about GRUB2, when the OP mentioned that an Ubuntu kernel was removed, before the issue appeared. I don't know how the auto-thingy is set up, what options will be add and how they affect or don't affect a Debian install. single for sure would get a name such as Single or Recovery for the menu entry, but there are or sure other options that could prevent GDM from running. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386952511.688.219.camel@archlinux
Re: gdm3 issue
On Fri, Dec 13, 2013 at 4:25 PM, PaulNM deb...@paulscrap.com wrote: On 12/13/2013 10:03 AM, Tom H wrote: On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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. 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 ;). 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. Except that single doesn't make GDM fail, it doesn't even launch it. It's not the same thing. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sy-yaenukbfhrmajfzfmv1y9ebdc_-xsf2nw5twpnk...@mail.gmail.com
Re: gdm3 issue
On Fri, 2013-12-13 at 16:49 +, Tom H wrote: On Fri, Dec 13, 2013 at 4:25 PM, PaulNM deb...@paulscrap.com wrote: On 12/13/2013 10:03 AM, Tom H wrote: On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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. 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 ;). 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. 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 just an ironical explanation what a single boot option could cause and it's too funny, since the option is called single. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386958087.688.236.camel@archlinux
Re: gdm3 issue
Hi. On Fri, 13 Dec 2013 19:08:07 +0100 Ralf Mardorf ralf.mard...@alice-dsl.net 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 just an ironical explanation what a single boot option could cause and it's too funny, since the option is called single. You're wrong here: - Nobody forbids the user to start GDM from single-user. - User can press Ctrl+D to escape single-user and proceed to runlevel 2, where GDM will try to start. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131213221655.eca7e61a7c2cffba550ea...@gmail.com
(SOLVED) Re: gdm3 issue
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. 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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a702a6.2060...@gmail.com
Re: (SOLVED) Re: gdm3 issue
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 else or) I should have mentioned to check the partition :S. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386678224.23432.20.camel@archlinux
Re: (SOLVED) Re: gdm3 issue
On 12/10/13, Kailash Kalyani listskail...@gmail.com 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 launched, grub's job has been done many seconds ago. Thank you all for your assistance! 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. I had a gdm problem - it looked really ugly and kept defaulting to gnome3 desktop when I wanted XFCE So then I stuck a kdm up my install, and PURGED GDM MWUAHAHAH! /ducks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSRyGF=6fxyvaedgbn9n33dya6hjqgr3aateurv7596...@mail.gmail.com
gdm3 issue
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 another partition. That resulted in a grub update from ubuntu and since then I've had this issue. Ubuntu has its own swap and home directories. Looking at the error messages I found this in auth.log: Dec 9 14:25:57 Sthir gdm-welcome][3599]: pam_unix(gdm-welcome:session): session opened for user Debian-gdm by (uid=0) Dec 9 14:25:57 Sthir gdm-welcome][3599]: pam_ck_connector(gdm-welcome:session): nox11 mode, ignoring PAM_TTY :0 Dec 9 14:29:40 Sthir polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.42 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_IN) Dec 9 14:29:42 Sthir dbus[2670]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.43 (uid=113 pid=3818 comm=/usr/lib/gdm3/gdm-simple-greeter ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=3534 comm=/usr/sbin/console-kit-daemon --no-daemon ) Dec 9 14:29:42 Sthir dbus[2670]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.43 (uid=113 pid=3818 comm=/usr/lib/gdm3/gdm-simple-greeter ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=3534 comm=/usr/sbin/console-kit-daemon --no-daemon ) Dec 9 14:29:42 Sthir dbus[2670]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.43 (uid=113 pid=3818 comm=/usr/lib/gdm3/gdm-simple-greeter ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=3534 comm=/usr/sbin/console-kit-daemon --no-daemon ) Dec 9 14:29:42 Sthir dbus[2670]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.43 (uid=113 pid=3818 comm=/usr/lib/gdm3/gdm-simple-greeter ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=3534 comm=/usr/sbin/console-kit-daemon --no-daemon ) Dec 9 14:29:42 Sthir dbus[2670]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.43 (uid=113 pid=3818 comm=/usr/lib/gdm3/gdm-simple-greeter ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=3534 comm=/usr/sbin/console-kit-daemon --no-daemon ) Dec 9 14:29:48 Sthir gdm3][3827]: pam_unix(gdm3:session): session opened for user kailash by (uid=0) Dec 9 14:29:48 Sthir gdm3][3827]: pam_ck_connector(gdm3:session): So the error appears with the gdm greeter being rejected. nox11 mode, ignoring PAM_TTY :0 Dec 9 14:29:48 Sthir gdm-welcome][3599]: pam_unix(gdm-welcome:session): session closed for user Debian-gdm Dec 9 14:29:48 Sthir polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.42, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_IN) (disconnected from bus) Dec 9 14:29:52 Sthir polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session2 (system bus name :1.63 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_IN) Dec 9 14:30:04 Sthir login[3617]: pam_unix(login:session): session opened for user kailash by LOGIN(uid=0) Dec 9 14:32:08 Sthir sudo: kailash : TTY=tty1 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/less auth.log Dec 9 14:32:08 Sthir sudo: pam_unix(sudo:session): session opened for user root by kailash(uid=0) Dec 9 14:33:00 Sthir sudo: pam_unix(sudo:session): session closed for user root Is this relevant? If not, what should I be looking at? Sincerely, Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5913c.6000...@gmail.com
Re: gdm3 issue
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 automatically write a broken grub.cfg with what ever obscure boot option that does break to log in your Debian. If possible you should use a good boot loader instead of GRUB, e.g. Syslinux. I use GRUB 2 just for fun too, but edit grub.cfg manually. Use GRUB 2 from Debian, hopefully it's defaults are more sane than those of *buntus and automatically generate a saner grub.cfg. Regards, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386587184.14806.69.camel@archlinux
Re: gdm3 issue
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 answer already seems to be there. Ubuntu did likely automatically write a broken grub.cfg with what ever obscure boot option that does break to log in your Debian. If possible you should use a good boot loader instead of GRUB, e.g. Syslinux. I use GRUB 2 just for fun too, but edit grub.cfg manually. Use GRUB 2 from Debian, hopefully it's defaults are more sane than those of *buntus and automatically generate a saner grub.cfg. Regards, Ralf Hi Ralf, Thanks, I tried that using update-grub2 from my Debian install. That did not resolve the issue :( I think it's a PAM issue with gdm - can't say if I'm making any sense, but I haven't found a explanation of how they hang together. Sincerely, Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5cbbf.7090...@gmail.com
Re: gdm3 issue
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 gdm - can't say if I'm making any sense, but I haven't found a explanation of how they hang together. I don't know. http://www.debian.org/doc/manuals/securing-debian-howto/ch4.en.html But at least removing the Ubuntu kernel wouldn't cause to change something for the Debian install. You could take a look and/or post the /boot/grub/grub.cfg entry that is used by grub to boot Debian, maybe there is a bad boot option. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386597934.14806.117.camel@archlinux
Re: gdm3 issue
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.cfg to the Ubuntu install.
I think it's a PAM issue with gdm - can't say if I'm making any sense,
but I haven't found a explanation of how they hang together.
I don't know.
http://www.debian.org/doc/manuals/securing-debian-howto/ch4.en.html
But at least removing the Ubuntu kernel wouldn't cause to change
something for the Debian install.
You could take a look and/or post the /boot/grub/grub.cfg entry that is
used by grub to boot Debian, maybe there is a bad boot option.
Hi Ralf,
Here's the boot.cfg (attached).
Thank you for the link! It will at the very least give me some
understanding of PAM.
Sincerely,
Kailash
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
set locale_dir=($root)/boot/grub/locale
set lang=en_IN
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
insmod png
if background_image /usr/share/images/desktop-base/joy-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
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-4c3f-8809-a3c6c1309776
echo'Loading Linux 3.2.0-4-686-pae ...'
linux /boot/vmlinuz-3.2.0-4-686-pae
root=UUID=ddea8c2f-f4b3-4c3f-8809-a3c6c1309776 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-686-pae (recovery mode)'
--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-4c3f-8809-a3c6c1309776
echo'Loading Linux 3.2.0-4-686-pae ...'
linux /boot/vmlinuz-3.2.0-4-686-pae
root=UUID=ddea8c2f-f4b3-4c3f-8809-a3c6c1309776 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-686-pae
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root
ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
linux16 /boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root
ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
menuentry Memory test (memtest86+, experimental multiboot) {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root
ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
multiboot /boot/memtest86+_multiboot.bin
}
menuentry Memory test (memtest86+, serial console 115200, experimental
multiboot) {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root
ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
multiboot /boot/memtest86+_multiboot.bin
Re: gdm3 issue
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-4c3f-8809-a3c6c1309776
echo'Loading Linux 3.2.0-4-686-pae ...'
linux /boot/vmlinuz-3.2.0-4-686-pae
root=UUID=ddea8c2f-f4b3-4c3f-8809-a3c6c1309776 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-686-pae
}
I can't speak for such default crap as load_video, but at least the
options ro and quiet shouldn't cause an issue.
My grub.cfg does start with
$ cat /mnt/saucy/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set color_highlight='light-cyan/blue'
# 2013-Dec-05
menuentry
and then there are only menu entries, nothing more. I also don't add the
quiet option and should delete the set default line.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1386602246.14806.146.camel@archlinux
Re: gdm3 issue
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)'
search --no-floppy --fs-uuid --set=root
ddea8c2f-f4b3-4c3f-8809-a3c6c1309776
echo'Loading Linux 3.2.0-4-686-pae ...'
linux /boot/vmlinuz-3.2.0-4-686-pae
root=UUID=ddea8c2f-f4b3-4c3f-8809-a3c6c1309776 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-686-pae
}
I can't speak for such default crap as load_video, but at least the
options ro and quiet shouldn't cause an issue.
My grub.cfg does start with
$ cat /mnt/saucy/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set color_highlight='light-cyan/blue'
# 2013-Dec-05
menuentry
and then there are only menu entries, nothing more. I also don't add the
quiet option and should delete the set default line.
Thank you for your feedback Ralf,
Yeah grub as a culprit would've been nice and easier to tackle. :)
I've also tried the following:
apt-get install gdm3 metacity --reinstall
But that did not resolve the issue. I'll keep looking.
From my research it seems that switching display managers will remove
my problem, however, for now I'd rather stick to gdm3 and figure out the
issue.
Sincerely,
Kailash
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52a5ed32.8030...@gmail.com
Re: gdm3 issue [boot loader digression]
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 issue. So the answer already seems to be there. Ubuntu did likely automatically write a broken grub.cfg with what ever obscure boot option that does break to log in your Debian. If possible you should use a good boot loader instead of GRUB, e.g. Syslinux. I use GRUB 2 just for fun too, but edit grub.cfg manually. Use GRUB 2 from Debian, hopefully it's defaults are more sane than those of *buntus and automatically generate a saner grub.cfg. Syslinux is nice, but it has its own problems and limitations. I couldn't get it to work on ISO installer, ISO converted-to-flash install and the system runtime. Grub 2 is, as far as I know, still broken. I once spent 2-3 weeks trying to change my firewall system from isolinux/lilo/grub to grub2 for all booting. I couldn't get it to work on ISO and it simply refused to install on the disk I told it to (it always used the first disk it found that had some form of grub2 on it). I finally quit and went back to grub legacy with all of redhat's patches. I had it re-integrated and running in about a half hour: booting the ISO and the ISO equivalent on flash/rotating drives--which entails copying the tree from the ISO, changing '(cd)' to '(hd0,0)' in the config file(s), and installing grub in the boot loader--and booting the runtime system. The firewall system now has a consistent boot presentation. Since then, I've fixed a few bugs in it; it now displays background images very nicely, handles multiple linked config files, works very well on serial consoles, and the 'hit a key to continue' works reliably to select the serial or VESA console when it finds both. My tuppence. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201312091204.21162.neal.p.mur...@alum.wpi.edu
Re: gdm3 issue
On Mon, Dec 9, 2013 at 11:06 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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 answer already seems to be there. Ubuntu did likely automatically write a broken grub.cfg with what ever obscure boot option that does break to log in your Debian. 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szlhsdqsamhhy6gmk9d7xolvk+eazh4xtzpyq7tdsv...@mail.gmail.com
Re: gdm3 issue
On Mon, Dec 9, 2013 at 2:30 PM, Kailash Kalyani listskail...@gmail.com 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...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=syhl6rnnyarrzcvkv7xm36pah-swomsw+o-mjg9hac...@mail.gmail.com
Re: gdm3 issue [boot loader digression]
On Mon, Dec 9, 2013 at 5:04 PM, Neal Murphy neal.p.mur...@alum.wpi.edu 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxyxrboqmphsgaohwgvs6u8g-ja7oz6+g8rinzzy-q...@mail.gmail.com
Re: gdm3 issue
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 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386638754.14806.174.camel@archlinux
Re: gdm3 issue
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, 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 ;). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386640642.14806.193.camel@archlinux
