Package: wdm Version: 1.28-2.4 Severity: important User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency
I got a report from a Debian user about problems with wdm with dependency based boot sequencing, and had a look. The init.d/wdm dependency information look like this: ### BEGIN INIT INFO # Provides: wdm # Required-Start: $remote_fs # Required-Stop: $remote_fs # Should-Start: console-screen # Should-Stop: console-screen # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: start or stop the WINGs display manager ### END INIT INFO This will make it start very early in the boot. The report indicated that X now need dbus and hal, and the gdm init.d script depend on acpid and network-manager as well. If wdm need the same dependencies, I recommend changing the should-start line to look like this: # Should-Start: console-screen kbd acpid dbus hal network-manager This will move the init.d script further back in the boot sequence, and might increase the chance of wdm starting as it should during boot. It will also solve bug #548105. I do not really know the requirement fo wdm, so I hope you as the maintainer can review this list and adjust it to better fit the need of wdm. <URL: http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html > documents the LSB header format. Some debian notes are available from <URL: http://wiki.debian.org/LSBInitScripts >. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
