Launchpad has imported 42 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=811902.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-04-12T09:36:10+00:00 Mikhail wrote: Description of problem: When I leave the computer on overnight, it is often in the morning discover the computer hangs and constantly swap, and the processes of gnome-settings-daemon and dconf consume all CPU resources. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/7 ------------------------------------------------------------------------ On 2012-04-12T09:40:06+00:00 Mikhail wrote: Created attachment 577019 htop Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/8 ------------------------------------------------------------------------ On 2012-05-05T10:14:41+00:00 Mikhail wrote: Created attachment 582274 htop Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/27 ------------------------------------------------------------------------ On 2012-05-14T11:15:16+00:00 Fabio wrote: Same bug on Ubuntu: https://bugs.launchpad.net/fedora/+source/gnome- settings-daemon/+bug/969359 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/35 ------------------------------------------------------------------------ On 2012-05-29T08:14:16+00:00 Mikhail wrote: Created attachment 587339 backtrace for gnome-settings-daemon 1-process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/51 ------------------------------------------------------------------------ On 2012-05-29T08:15:09+00:00 Mikhail wrote: Created attachment 587340 backtrace for gnome-settings-daemon 2-process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/52 ------------------------------------------------------------------------ On 2012-05-29T08:16:08+00:00 Mikhail wrote: Created attachment 587342 backtrace for dconf-service process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/53 ------------------------------------------------------------------------ On 2012-05-29T08:17:33+00:00 Mikhail wrote: Created attachment 587343 backtrace for dbus-daemon process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/54 ------------------------------------------------------------------------ On 2012-06-04T04:49:45+00:00 Mikhail wrote: Created attachment 589027 backtrace for gnome-settings-daemon Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/67 ------------------------------------------------------------------------ On 2012-06-04T04:50:49+00:00 Mikhail wrote: Created attachment 589028 backtrace for dconf worker process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/68 ------------------------------------------------------------------------ On 2012-06-04T04:51:53+00:00 Mikhail wrote: Created attachment 589033 backtrace for Compositor Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/69 ------------------------------------------------------------------------ On 2012-06-04T04:52:49+00:00 Mikhail wrote: Created attachment 589035 backtrace for dconf-service Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/70 ------------------------------------------------------------------------ On 2012-06-04T04:55:14+00:00 Mikhail wrote: when it occurs Num Lock indicator is often blink. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/71 ------------------------------------------------------------------------ On 2012-07-12T13:17:58+00:00 Mikhail wrote: Killing dconf worker process seems stop this, but something wrong after this: Not work hot keys (Ctrl +Shift + L - lock comkputer, Prt Scr - make screenshot), decrease font... Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/102 ------------------------------------------------------------------------ On 2012-07-12T13:18:19+00:00 Mikhail wrote: Killing dconf worker process seems stop this, but something wrong after this: Not work hot keys (Ctrl +Shift + L - lock computer, Prt Scr - make screenshot), decrease font... Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/103 ------------------------------------------------------------------------ On 2012-07-12T13:19:01+00:00 Mikhail wrote: Created attachment 597807 backtrace for dconf worker process Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/104 ------------------------------------------------------------------------ On 2012-07-12T13:20:31+00:00 Mikhail wrote: Created attachment 597808 proof screenshot Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/105 ------------------------------------------------------------------------ On 2012-07-15T18:35:58+00:00 Tobias wrote: see also this GNOME bug: https://bugzilla.gnome.org/show_bug.cgi?id=679151 FWIW: Affects me, too. pkill -STOP gnome-settings lets me use my computer again... Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/106 ------------------------------------------------------------------------ On 2012-07-16T13:25:34+00:00 udo wrote: Even happens during teh day when I am away for work. killall -9 gnome-settings-daemon helps, but is it the right way? dconf is indeed active as well. (noticed after killing) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/107 ------------------------------------------------------------------------ On 2012-07-16T13:27:36+00:00 udo wrote: Comment 12 was observed here as well. Comment 14 was observed here as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/108 ------------------------------------------------------------------------ On 2012-07-16T13:35:47+00:00 udo wrote: I am on x86_64. You too? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/109 ------------------------------------------------------------------------ On 2012-07-19T13:18:16+00:00 udo wrote: This bug makes working cumbersome. The machine is ok in the early morning. I leave home for work and return after 9.5-10 hours. gnome-settings-daemon is making the numlock blink feverishly and the system slowish. So we kill gnome-settings-daemon. Also we kill the dconf thing. We log out. The machine completes slowly. We log in and stuff is mostly fine again for the rest of the day and next morning. But is this a nice way to work with the box? Therefor I increased severity again. Mikhail created a very nice bug report. Bastien: please come and help fix this. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/110 ------------------------------------------------------------------------ On 2012-07-20T11:49:07+00:00 udo wrote: I tried the dconf-editor workaround from comment 17 yesterday. Today I found my box without the blinking numlock. gnome-settings-daemon was still consuming one full core. So we killed that stuff. Logged out and logged in. Can someone please fix this without mentioning the `upstream` mantra? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/111 ------------------------------------------------------------------------ On 2012-07-22T09:46:44+00:00 Mikhail wrote: Sorry my previous backtraces not contain debugging symbols. Now I'm fixed. Another well-reproduced the bug on my laptop on kitchen (it has little memory, and he constantly swaps) when I started google-chrome and evolution, and pressed the Num Lock situation is reproduced. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/114 ------------------------------------------------------------------------ On 2012-07-22T09:47:27+00:00 Mikhail wrote: Created attachment 599575 proof screenshot Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/115 ------------------------------------------------------------------------ On 2012-07-22T09:48:55+00:00 Mikhail wrote: Created attachment 599576 new backtrace with all debug symbols Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/116 ------------------------------------------------------------------------ On 2012-07-22T09:50:46+00:00 Mikhail wrote: Created attachment 599577 new backtrace with all debug symbols making minute later Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/117 ------------------------------------------------------------------------ On 2012-07-22T10:38:38+00:00 Mikhail wrote: udo: may be better report to upstream? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/118 ------------------------------------------------------------------------ On 2012-07-22T14:20:30+00:00 Mikhail wrote: Created attachment 599614 backtrace for dconf-service Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/119 ------------------------------------------------------------------------ On 2012-07-22T15:19:47+00:00 udo wrote: Mikhail, in comment 17 Tobias mentions an upstream bug that doesn't show progress yet. So how do we improve from here? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/120 ------------------------------------------------------------------------ On 2012-07-25T13:28:20+00:00 udo wrote: This afternoon I found a blinking numlock LED again. So comment 22's workaround did not help at all. What is the progress? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/121 ------------------------------------------------------------------------ On 2012-07-30T17:21:04+00:00 Dag wrote: Hi all, this bug shows up for me as well. FC17 x86_64 up to date. dconf-service and gnome-settings-daemon are taking 100% CPU and doing a lot of I/O on disk. For me it was triggered, _each time_, when using vino-server (Gnome 3 remote desktop) on the local machine (the one having the problem). I was connected from a distant client (this one did not malfunction ever) to this local machine. I was killing both services to restore the usability of the remote machine, and it oftently crashes the session. Eventually both services were automatically restarted and the problem was here again, and I had to kill both services again and risking a session crash. Temporary fix : Using dconf-editor : uncheck the check-box from org.gnome.settings-daemon.peripherals.keyboard.remember-numlock-state. This temporary fix works for me. (source: https://bugzilla.gnome.org/show_bug.cgi?id=679151) Same problem on Ubuntu : https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359 Bye for now Dag Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/124 ------------------------------------------------------------------------ On 2012-08-09T14:39:39+00:00 Mikhail wrote: Created attachment 603269 new backtrace for gnome-settings-daemon Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/128 ------------------------------------------------------------------------ On 2012-08-09T15:19:36+00:00 udo wrote: For me a workaround (!) was the disabling of 'remember numlock state' or whatever it was called. The issue hasn't happened for a few days now since I did that. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/129 ------------------------------------------------------------------------ On 2012-08-09T15:20:10+00:00 udo wrote: (so yes I can confirm the Dag comment number 31) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/130 ------------------------------------------------------------------------ On 2012-09-14T19:05:55+00:00 Tobias wrote: FWIW: abrt choses my crashing g-s-d to be a dup of bug 716357. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/149 ------------------------------------------------------------------------ On 2012-10-30T02:46:30+00:00 Mamoru wrote: Created attachment 635290 gdb backtrace when g-s-d consumes 100% cpu I've encountered the similar issue. g-s-d now consumes 100% cpu. gdb log attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/166 ------------------------------------------------------------------------ On 2012-10-30T03:40:27+00:00 Mamoru wrote: Looks like 100% reproducible when pressing NumLock key twice. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/167 ------------------------------------------------------------------------ On 2012-11-09T01:48:10+00:00 Francisco wrote: This has been fixed at g-s-d 3.6.2 upstream: https://bugzilla.gnome.org/show_bug.cgi?id=679151#c34 http://git.gnome.org/browse/gnome-settings- daemon/commit/?id=15baf34186c6b5886b26e5a37698893be36f510b http://git.gnome.org/browse/gnome-settings- daemon/commit/?id=5e2ab43195b0522489e17c4daef5f4b391222eae Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/171 ------------------------------------------------------------------------ On 2012-12-31T15:30:30+00:00 Tobias wrote: Still an issue with 3.4.2 with currently stable F17. So a backport would be appreciated. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/189 ------------------------------------------------------------------------ On 2013-07-03T20:27:31+00:00 Fedora wrote: This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/200 ------------------------------------------------------------------------ On 2013-07-31T20:26:54+00:00 Fedora wrote: Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/969359/comments/201 ** Changed in: gnome-settings-daemon (Fedora) Status: Unknown => Won't Fix ** Changed in: gnome-settings-daemon (Fedora) Importance: Unknown => Critical -- 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/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Precise: Fix Released Status in gnome-settings-daemon source package in Quantal: Fix Released Status in gnome-settings-daemon package in Fedora: Won't Fix Bug description: Impact: gnome-settings-daemon uses 100% cpu for ever in some cases Test Case: Seems to happen sometimes after docking or connecting with vnc, try to connect to the machine using a vnc client a few times and check there is no numlock cycle and cpu usage loop starting Regression potential: The numlock state could be wrongly set,restored on login in some cases ----------------- Original message: ----------------- I don't know how to reproduce this bug, but after varying amounts of normal usage of my laptop, I notice gnome-settings-daemon is consuming 100% (approx) CPU. I am not sure how to restart gnome-settings-daemon, I tried opening a terminal and running gnome-settings-daemon again but this crashes my system - my external monitor switches off and my laptop locks up. I am able to reboot with SysRq+REISUB. Sorry I cannot provide more information - it happens twice now, maybe someone can tell me how to get more information for the next time this happens. $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.4.0-0ubuntu2 Candidate: 3.4.0-0ubuntu2 Version table: *** 3.4.0-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 17:16:02 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.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/gnome-settings-daemon/+bug/969359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
