https://bugzilla.novell.com/show_bug.cgi?id=782909 https://bugzilla.novell.com/show_bug.cgi?id=782909#c3 --- Comment #3 from Jean Delvare <jdelvare@suse.com> 2012-12-06 08:42:16 UTC --- Something I noticed: the following dbus-daemon processes are running when the gdm login prompt is displayed: 100 1460 1 0 07:55 ? 00:00:00 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation gdm 3602 1 0 14:36 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session gdm 3641 3636 0 14:36 ? 00:00:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 The following dbus-daemon processes are running after Gnome 3 is started: 100 1359 1 0 07:30 ? 00:00:02 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation khali 4463 1 0 07:30 ? 00:00:01 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session That is, the gdm instances are gone and a user instance has started. When the CPU usage jumps to 100%, I see the following dbus-daemon processes running: 100 1329 1 0 07:49 ? 00:00:00 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation gdm 2664 1 99 07:49 ? 02:00:03 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 gdm 4368 2664 0 07:49 ? 00:00:00 [dbus-daemon] <defunct> khali 4456 1 0 07:49 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session That is, the gdm instances are still present, while I think they shouldn't. So the issue could be that gdm sometimes fails to properly stop its dbus-daemon instances when starting the Gnome 3 session. -- 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.