https://bugzilla.novell.com/show_bug.cgi?id=406676
User mmeeks@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=406676#c4
Michael Meeks changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|fresh install, run 'keyboard' capplet ... bang |Zapping X server breaks Gnome.
--- Comment #4 from Michael Meeks 2008-07-07 02:36:12 MDT ---
The strace shows it connecting to the wrong dbus session bus:
spawned gnome-keyboard-properties:
6786 1215419316.607169 connect(14, {sa_family=AF_FILE,
path=@/tmp/dbus-Rppokg2vfj}, 23) = 0
gnome-control-center:
(gdb) p (char *)getenv ("DBUS_SESSION_BUS_ADDRESS")
$2 = 0xbfebdf28
"unix:abstract=/tmp/dbus-Rppokg2vfj,guid=c4857fe5db3b135820b98b77487092bb"
newly launched gnome-terminal:
julia@linux-37cr:~/Desktop> echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-mwelosnMPv,guid=2cda5e834e7592366859acb14870e5f1
Sooo ... it seems we have some environment poisoning: most likely related to
the zap, and/or a surviving b-a-s across sessions.
What I guess is most interesting, is that it seems we have an 'old' dbus
session bus that is still in use too:
julia@linux-37cr:~/Desktop> ps ax | grep dbus
2708 ? Ss 0:09 /bin/dbus-daemon --system
3368 ? S 0:00 dbus-launch --autolaunch
1fc20e05305a3e5d1a1fd32a484e714c --binary-syntax --close-stderr
3369 ? Ss 0:00 /bin/dbus-daemon --fork --print-pid 6
--print-address 8 --session
3472 ? Ss 0:00 dbus-daemon --fork --print-address 18 --print-pid 20
--session
6875 pts/2 R+ 0:00 grep dbus
8495 ? Ss 0:00 dbus-daemon --fork --print-address 19 --print-pid 21
--session
Which points to some pretty hideous non-cleaning up on Zap.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
