** Description changed:
Binary package hint: gdm
When fsck runs on boot it triggers a failsafe x session every time on
all of my machines running lucid. Coupled with the fact failsafeX uses
vesa which does not work when i915 is loaded with KMS as well as the
fact fsck's happen without any visual feedback when plymouth is
installed it is a pretty nasty bug when it happens. I have filed a
seperate bug regarding possibly adding a check in
/etc/gdm/failsafeXStart to use fbdev instead of vesa already. (lp:
#496773)
Steps to reproduce:
1) Set the mount count flag on a partition higher than the maximum mount
count line dumpe2fs lists.
(for example: sudo tune2fs -C 200 /dev/sda1)
2) Reboot
- Changing /etc/init/gdm.conf so it checks "and stopped udevtrigger"
- instead of "or stopped udevtrigger)" after the graphics-device-added or
- drm-device-added section fixes the problem for me
+ Changing /etc/init/gdm.conf so it checks "and stopped udevtrigger)"
+ instead of "or stopped udevtrigger))" fixes it for me.
+
+ Not working default /etc/init/gdm.conf, failsafeX after fsck:
start on (filesystem
and (graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1
- or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1)
- and stopped udevtrigger
- or build-successful MODULE=nvidia
- or build-successful MODULE=fglrx)
+ or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
+ or stopped udevtrigger))
+ stop on runlevel [016]
+
+ Working gdm.conf, no failsafe X after fsck:
+
+ start on (filesystem
+ and (graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1
+ or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1)
+ and stopped udevtrigger)
stop on runlevel [016]
ProblemType: Bug
Architecture: i386
Date: Mon Dec 14 19:55:01 2009
DistroRelease: Ubuntu 10.04
Package: gdm 2.29.1-0ubuntu7
ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-8.12-generic
SourcePackage: gdm
Tags: ubuntu-unr lucid
Uname: Linux 2.6.32-8-generic i686
--
fsck on boot triggers failsafe x 100% of the time
https://bugs.launchpad.net/bugs/496796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs