On Sat, May 9, 2009 at 23:00:54 +0200, Michael Biebl wrote:
2.) I Xorg can't connect to hal, it should gracefully fall back to a basic
kbd/mouse configuration.
If X can't connect to hal right away, it listens for a startup
notification so you can eventually get your devices even if hal
On Sat, May 9, 2009 at 21:40:40 +0200, Norbert Preining wrote:
The errors when dbus is restarted is a bit more cryptic, but it seems
that the whole stuff of modules is unloaded and then everything hangs:
(II) UnloadModule: synaptics
(II) Sony Vaio Keys: Close
(II) UnloadModule: evdev
(II)
On Sa, 09 Mai 2009, Michael Biebl wrote:
Could you investigate if hald is started correctly when dbus is restarted and
running afterwards?
How can I check that? I cannot get access to a console and cannot ...
wait, maybe I can do on the console a
sleep 120 ; /etc/init.d/gdm stop
and
tags 527872 moreinfo unreproducible
thanks
Norbert Preining wrote:
Package: dbus
Version: 1.2.14-2
Severity: important
Just upgraded two times dbus and both times I was kicked out of my
X (Gnome) session when X restarted.
That is not acceptable behaviour, and I tend to raise the
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
Michael Biebl wrote:
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
6 matches
Mail list logo
