*** This bug is a duplicate of bug 969359 ***
https://bugs.launchpad.net/bugs/969359
** This bug has been marked a duplicate of bug 969359
gnome-settings-daemon consumes 100% cpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is definitely the same as #483719 - which is classified as a
duplicate of #969359.
So should I mark as duplicate?
I cannot reproduce. If it happens again I will obtain a backtrace
following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attac
Thank you for your bug report, could you get a gdb stacktrace? is the
numlock status changing when that happens? seems similar to bug #969359
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Incomple
BTW the reason I post this is because I cant logout using gnome. (see
CannotLogout Screenshot).
Also, I had VMware running ( but no VM was currently active )
** Attachment added: "Cannot Logout Screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/990695/+attachmen
** Attachment added: "Screenshot of System Monitor"
https://bugs.launchpad.net/bugs/990695/+attachment/3113254/+files/GnomeDeamonSettingsMemoryLeak.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
