Follow-up: I believe I found the problem - KDM is being started way too early in the boot process, well before HAL is started. It's been my experience in the past that HAL must be started first, or KDE will not sense its presence. I modified my boot order slightly, by removing /etc/rc2.d/S13kdm and /etc/rc3.d/S13kdm (since I wasn't sure which runlevel was correct, and neither one was appropriately numbered anyway), and adding a line to /etc/rc.local to start KDM from there.
I suspect a "proper" fix would entail merely renaming the /etc/rc?.d/S13kdm symlinks to some value that puts it nearly last in the boot order. Problem seems to be solved. This also fixes "host not found" errors that kmail throws now and again at startup, since the network was also being brought up after KDE was up. Recommend pushing this fix out ASAP, as it may fix boot-order-sensitive other bugs as well. -- USB device doesn't mount if plugged in at KDE startup https://bugs.launchpad.net/bugs/262893 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
