Hi all,
Just to re-iterate from a release team PoV, this could really do with
fixing.
(for d-d readers, this is a awesome bug, where dbus upgrades kill X)
This is holding up xcb-util, which is holding up python-visual, which is
preventing the removal (finally!) of GTK 1
Thanks,
Neil
--
pixie
On Fri, Jul 24, 2009 at 01:50:02PM +0100, Neil McGovern wrote:
Just to re-iterate from a release team PoV, this could really do with
fixing.
(for d-d readers, this is a awesome bug, where dbus upgrades kill X)
This is holding up xcb-util, which is holding up python-visual, which is
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 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
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
