*** This bug is a duplicate of bug 969359 ***
https://bugs.launchpad.net/bugs/969359
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 969359 ***
https://bugs.launchpad.net/bugs/969359
Backtrace for /usr/lib/gnome-settings-daemon/gnome-settings-daemon
hum, that stacktrace has no useful info, it seems to just be waiting in
poll() which it what it does when not busy
Funny thing is that I
*** This bug is a duplicate of bug 969359 ***
https://bugs.launchpad.net/bugs/969359
Merging the bugs, will link to your backtrace,
thanks
** This bug has been marked a duplicate of bug 969359
gnome-settings-daemon consumes 100% cpu
--
You received this bug notification because you are
Backtrace for /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Funny thing is that I wasn't able to attach to the process unless I used
sudo (although the process was owned by my user!!)
Another funny thing is that after detaching (or maybe that happened
after attaching), the process stopped
** Description changed:
While I am on a GNOME Shell session, gnome-settings-daemon would start
hogging the CPU (using 100% of a CPU core). This doesn't necessarily
from the beginning of the session, rather it usually happens after an
hour or so of the session.
+
+ Note, I have been
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
