Norbert Preining wrote: > severity 527872 serious > title 527872 restarting dbus kills X and kills keyboard > thanks > > On Sa, 09 Mai 2009, Michael Biebl wrote: >> Hm, I can not reproduce this problem here, restarting dbus does not kill my X >> session. >> >> Could you check/attach your Xorg log file please > > Even worse, I just tried it and then I remembered that I wanted to > report the bug already some weeks ago. When calling > /etc/init.d/dbus restart > from a running X it restarts X and gdm, but the keyboard is not working. > I cannot switch to console, it is all a mystery. > > I managed to capture everything, the problem is that X reboots but > fortunately the old Xorg.0.log is saved. Then the kbd does not work but > Sysrq at least. > > Ok, short: > - boot > - gdm pops up > - I login as user > - open a xterm, su, and call /etc/init.d/dbus restart > - X dies -> the log file of that X is attached as > Xorg.0.log-dbus-killed-X > - X restarts but the kbd does not work, the log is attached as > Xorg.0.log-X-session-after-debus-kill-without-kbd > - I sysrq out (sync, remount ro, reboot), the end of the syslog of that > kernel run is attached as > syslog > > The only errors in the "Missing kbd session" is > (EE) config/hal: couldn't initialise context: (null) ((null))
Looks like hal is not correctly started when you restart dbus, and X is hal to get it's input devices (thus no keyboard or mouse). So imho we have two problems here (not really problems in dbus itself) 1.) hal does not seem to come up properly after dbus has been restarted 2.) I Xorg can't connect to hal, it should gracefully fall back to a basic kbd/mouse configuration. Could you investigate if hald is started correctly when dbus is restarted and running afterwards? Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
