*** This bug is a duplicate of bug 969359 ***
https://bugs.launchpad.net/bugs/969359
Thank you for your bug report, it seems likely to be bug #969359
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => High
** This bug has been marked a duplicate of bug 969359
[keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1028416
Title:
gnome-settings-daemon high CPU usage and keeps overwriting
.config/dconf/user
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “gnome-settings-daemon” package in Fedora:
New
Bug description:
Unfortunately not much more informations at this time but this is what
I have.
1. At some point the gnome-settings-daemon will start utilising about 95% of
one CPU core, iotop will show dconf-services hovering around 3 place and lsof
will show show gnome-settings-daemon using .config/dconf/user.
2. This has happened five times now every time on a fairly busy system e.g
Firefox and Chromium multiple tab some with active content like flash and
html5, one or more virtualbox machines and a terminal or two.
3. the first three times were weeks apart but the last two was on the same
day after a reboot for the kernel update.
4. sudo kill -9 PID of gnome-settings-daemon restores the system to normal.
(Works somtimes)
5. Afterwards the .config/dconf/ folder will have several user.????? files.
If you need me to collect specific information next time let know.
Happened again but this time no.4 did not work the gnome-settings-daemon was
killed and "/usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch -background none" started maxing out the one CPU core. After awhile
gnome-settings-daemon restarted and continued maxing out the core.
"sudo restart lightdm" did however bring the system back.
"sudo restart dbus" was tried one time it worked but killed the wifi all my
running program survived at leased allowing me to save and reboot.
Mmm this may have something to do with using a Bluetooth numpad as the bug
started happening regularly this week and only happens during working hours. I
started doing data entry this week in a VM, using the numpad more than normal.
PS. Is it better or update the bug info here or in the comments?
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Tue Jul 24 12:44:59 2012
InstallationMedia: This
ProcEnviron:
LANGUAGE=en_ZA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_ZA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028416/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
