seems I have the same problem on Ubuntu 16.04.5 LTS
--
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
I've just encountered this today with 18.04, all updates installed both
gsd-color and gsd-keyboard and gsd-clipboard all maxing out CPU leading
to 60 seconds of non-interactive machine (I know lots of people that
would have simply power-cycled, but I wanted to know if it was a
separate issue).
--
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
Just to mention that I encountered the same problem on Ubuntu 16.04 with
GNOME. I checked the permissions on ~/.cache/dconf and indeed, it was
owned by root. I've updated it as described in #170. I hope it will fix
the problem.
--
You received this bug notification because you are a member of
#170 works for me also. unity-settings-daemon was producing a lot of io
disk activity when starting the system after upgrading to 16.04 and that
fixes it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Bug exists on Ubuntu 12.04 with MATE - mate-settings-daemon and dconf-
service eat CPU and NumLock blinking.
--
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:
Noticed Ubuntu getting unbearably slow after upgrading from 15.10 to
16.04. Gnome-settings-daemon was on top of processes list with 30% CPU.
The ownership of .cache/dconf was root, changed it with chown and the
problem seems to have gone away. Thanks Marcel!
--
You received this bug notification
And thank you from me, too, Marcel Miguel, comment #170.
chgrp and chown of .cache/dconf in each user's home directory worked me
as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Thank you, Marcel Miguel, comment #170.
I had the same problem after upgrading to Ubuntu 15.10. Changing the
ownership of .cache/dconf, as you suggested, did the trick.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello This issue occurs when i try to connect via google remote desktop, only
option to overcome is to kill gnome-settings-demon,
the version i am using is 15.10, may be the fix is not merged with this version
?
--
You received this bug notification because you are a member of Desktop
Same thing for me in WIly 15.10.
gnome-settings-daemon - 3.16.3-0ubuntu1
I have 12GB RAM and i7 4700MQ cpu and my laptop is stuck.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Still hapenning in Ubuntu 15.10, gnome-settings-daemon 3.16.3-0ubuntu1.
The problem on my installation was that ~/.cache/dconf was owned by root. I
changed it:
sudo chgrp myuser .cache/dconf
sudo chown myuser .cache/dconf
Then dconf-editor was able to change confguration.
No need to change
** Please change the status of this bug to Confirmed
I can confirm that this is still happening in Utopic.
My story is same as Ritberg's.
After I connect via VNC to my vinagre daemon the io usage slowly (during approx
20 hours) climbs to 100% and the system proceeds to hang while excessively
I am on 14.04 LTS and using Gnome. I encountered severe and frequent
high CPU consumption caused by gnome-settings-daemon process. I then
deleted /usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-
plugin. I also applied the num lock fix as explained in #107.
I noticed improved (less
I am using Linux Mint 17 64 bit.
After login with VNC/Vino, numlock began flicker and mate-settings-
daemon was using 100 % CPU/Core.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
the Bug seems to persist on saucy (13.10) but i don't have a blinking
numlock.
furthermore, it seems like the goa-daemon comsumes 90-100% on a cpu for
every user that is logged in, therefore locking a cpu per user that is
logged in.
$ dpkg -l | grep gnome-settings-daemon
ii
Comment #107 did not work for me.
dpkg -l | grep gnome-settings-daemon
ii gnome-settings-daemon 3.6.4-0ubuntu8
amd64daemon handling the GNOME session settings
Running Linux Mint 15 on Acer Aspire 5730z
Kernel 3.8.0-33-generic #48-Ubuntu
Just noticed it only happens on newer kernels, everything is fine on
3.2.
--
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
Still happening on Precise for me. I have a laptop and there's no
numpad, but the process starts to use 100% of one core every time I plug
the charger and it'svery annoying.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I can confirm this error message occurs in Ubuntu 13.04 64-bit while
running VMware Workstation 10, each time that the mouse pointer crosses
onto, or off of, the VMware window.
(gnome-settings-daemon:5101): libappindicator-CRITICAL **:
app_indicator_set_label: assertion `IS_APP_INDICATOR (self)'
I have this problem after update from 13.04 to 13.10 with last updates.
What information may help to fix this issue?
--
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
I think you should go re-open or report a new bug on the gnome bugzilla,
because this issue is still happening.
--
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
Still happening on Precise for me as well. Should we file a new bug or
revert this status back to confirmed or new?
--
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
To me it happened once, after other bugs:
1. Used extensively (GPARTED=100%), crashed gnome-shell (wasn't answering, I
guess the kernel or something else killed it)
2. Attempted to log back in (had to do SYSRQ+K to logout), got forced in
gnome-classic (however having my icon theme)
3. Rebooted,
This is still happening to me as well, using 3.4.2-0ubuntu15. In fact, I
think 3.4.2-0ubuntu15 CAUSED the problem to recurr. I had experienced it
in the past and solved using the numlock workaround via dconf-editor.
Today I ran an update, and immediately afterward the problem came back.
I don't
still happening -- using Quantal, gsd 3.4.2-0ubuntu15
--
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
** Tags removed: verification-needed
--
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
This bug was fixed in the package gnome-settings-daemon -
3.4.2-0ubuntu15
---
gnome-settings-daemon (3.4.2-0ubuntu15) quantal-proposed; urgency=low
* debian/patches/git_no_numlock_eating_cpu_loop.patch:
- backport upstream fix for numlock keeps changing state and
@johrosina, I hadn't enabled proposed, thought fix released meant it was in
the regular updates already. With
proposed I went from 3.4.2-0ubuntu0.6 to 3.4.2-0ubuntu0.6.1, I'll see how it
goes.
--
You received this bug notification because you are a member of Desktop
Packages, which is
3.4.2-0ubuntu15 from quantal-proposed solves the problem for me.
** Tags added: verification-done-quantal
--
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:
sorry have not read all the details re:numlock but i can reproduce it
using remmina i connect to a vnc client
i issue a control_r i press the num lock button
i exit remmina
the client desktop is now locked into the num lock is off no matter what the
lights on the key board says
and no local
Erno, could you please verify you enabled proposed, as described on comment #135
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359/comments/135
And tell us which version of g-s-d you are using? Run dpkg -l | grep
gnome-settings-daemon
--
You received this bug
Still happens on Precise.
--
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)
I'm still experiencing the problem of gnome-settings-daemon consuming
100% of CPU. I have the deb from quantal-proposed installed.
[chbaker@reacher:~]$ dpkg -l | grep gnome-settings
Follow up observations patch applied on 11-30 (post #140)
This is for a remote PC I connect to via VNC over SSH. tightvnc. I don't see
it often. Today was first time in 3 weeks. User has trouble getting photos
from camera.
Initial cpu load around 30% - things look good.
PC uptime is 2 hours -
** Tags added: verification-done-precise
--
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
This bug was fixed in the package gnome-settings-daemon -
3.4.2-0ubuntu0.6
---
gnome-settings-daemon (3.4.2-0ubuntu0.6) precise-proposed; urgency=low
* debian/patches/git_no_numlock_eating_cpu_loop.patch:
- backport upstream fix for numlock keeps changing state and
Simon,
That fixed it.
$ ps -fe | grep gnome-settings-daemon
bdudek2088 2014 0 10:27 ?
00:00:00 /usr/lib/gnome-settings-daemon/gnome-settings-daemon
bdudek2404 2014 0 10:27 ?
00:00:00 /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
bdudek3939 3881 0 10:36 pts/1
I am still having this issue on 12.04 LTS
$ dpkg -l gnome-settings*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionDescription
@Bruce: what version are you using? you can use dpkg -l | grep gnome-
settings-daemon to avoid having the column truncated
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Ubuntu 12.04.1 LTS
$ dpkg -l | grep gnome-settings-daemon
ii gnome-settings-daemon 3.4.2-0ubuntu0.5
daemon handling the GNOME session settings
$ uname -a
Linux bruce 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
$ ps -fe |
@Bruce, see comment #135 on how to enable precise-proposed to install
version 3.4.2-0ubuntu0.6 (note the .6 at the end) that has the fix
included:
gnome-settings-daemon (3.4.2-0ubuntu0.6) precise-proposed; urgency=low
* debian/patches/git_no_numlock_eating_cpu_loop.patch:
- backport
the update is available for a week in precise-proposed and seems to work
fine, did anyone got the issue with it?
--
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
I just installed the i386 ...06 deb on a friend's PC with the problem.
Before the install cpu load was like 6.x or 7.x now it's like 0.3
Hope the bug stays dead.
Thanks for the package.
Will post back only if the bug returns.
--
You received this bug notification because you are a member of
I have also had this problem for the last couple of months so I applied
the proposed package as per comment #135 and so far all is working well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Hello James, or anyone else affected,
Accepted gnome-settings-daemon into quantal-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/gnome-
settings-daemon/3.4.2-0ubuntu15 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Branch linked: lp:ubuntu/quantal-proposed/gnome-settings-daemon
--
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
3.4.2-0ubuntu0.6 worked on precise
** Tags removed: verification-needed
** Tags added: verification-done
--
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:
I was subscribed to the duplicate bug 1004166, which is about a
different way to get Num Lock to blink. With the proposed package, that
method to get the bug is also fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello James, or anyone else affected,
Accepted gnome-settings-daemon into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/gnome-
settings-daemon/3.4.2-0ubuntu0.6 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Branch linked: lp:ubuntu/precise-proposed/gnome-settings-daemon
--
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
** Also affects: gnome-settings-daemon (Ubuntu Quantal)
Importance: Undecided
Status: New
--
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:
upstream think they fixed the issue with http://git.gnome.org/browse
/gnome-settings-
daemon/patch/?id=ff5b65349a9e377d17946ccb29b764f19c3bef7e
I've uploaded that fix to raring and backported to quantal, once the fix
is confirmed we will backport to the LTS as well
** Changed in:
** Branch linked: lp:ubuntu/raring-proposed/gnome-settings-daemon
--
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
This bug was fixed in the package gnome-settings-daemon -
3.4.2-0ubuntu16
---
gnome-settings-daemon (3.4.2-0ubuntu16) raring; urgency=low
* debian/patches/git_no_numlock_eating_cpu_loop.patch:
- backport upstream fix for numlock keeps changing state and
** Changed in: gnome-settings-daemon
Status: In Progress = Fix Released
--
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]:
** Changed in: gnome-settings-daemon
Status: Confirmed = In Progress
--
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]:
Upgraded to 12.10 with gnome-shell and the same problem appears. The
issue occurs randomly without being able to understand what triggers it.
The proposed fix in #120 didn' work for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I see this bug too. Workaroud #107 helps.
--
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
I have a patch for this upstream. If #120 / #107 didn't work for you,
try applying it when G-S-D isn't going crazy and your numlock isn't
flashing. It should definitely prevent numlock-flashing problem from
happening; if G-S-D is using 100% CPU and your numlock isn't flashing,
it may be a
I upgraded to 12.10 and started seeing this again. Will re-do the
keyboard.gnome-settings-plugin deletion and restart gnome-settings work-
around that worked before.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon
** Changed in: gnome-settings-daemon
Status: Incomplete = Confirmed
--
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]:
The proposed workround in #120 did not work for me. This bug is really
annoying - every time it happens it locks up the pc. I am running Ubuntu
desktop 12.04.1 x64.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in
Ran into this again after using RDP on this machine and then toggling
numlock - settings daemon went wild with CPU.
--
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
I too can confirm Comment #120 worked for me.
And I too had synergyc (client) running on Ubuntu12.10 (clean install)
--
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
I have reproduced this with Ubuntu 12.10 (with gnome-settings-daemon
3.4.2) as well. It displayed the usual symptom of 100% CPU usage, but
then it crashed. I have attached an Apport crash report.
I can reproduce this at will by turning Num Lock on, connecting to vino-
server with androidVNC,
i can confirm comment #120 fix worked for me
from command line
gsettings set org.gnome.settings-daemon.peripherals.keyboard
remember-numlock-state false
and in case you had to
gsettings set org.gnome.settings-daemon.peripherals.keyboard numlock-state 'off'
i added these commands to a custom new
happended to me when another user was logged in, and when switching to
tty8 (the other user's session) the blinking stopped, so i switched over
each tty and also in tty7 the blinking stopped. it crashed about 20
seconds afterward, though :/
--
You received this bug notification because you are a
post 107/120 hasnt fixed it for me, it still occurs, usually starts when
the system is doing something intensive.
--
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
Comment 107 worked for me. Bug occurs when using VNC client from
Windows PC to Vino on Ubuntu 12.04.
** Description changed:
- Check comment 33 for a possible workaround.
+ Check comments 33 and 107 for a possible workaround.
Original message:
-
I don't know how to
I had the same problem on an old laptop with Ubuntu 12.04.1 x86.
Thanks to Коренберг Марк, the problem was solved ! (#107)
$ sudo apt-get install dconf-tools
$ dconf-editor
$ Go to org.gnome.settings-daemon.peripherals.keyboard
$ uncheck remember-numlock-state checkbox
--
You received this bug
I'm fighting this bug too.
Tried the fix in #85 but bug came back again.
So I'm back here again.
Tried the fix of uncheck remember-numlock-state
cpu load dropped from 5.0 to under 1.0 and system seems fine now.
Could be a hardware issue. The user has a replacement keyboard. Don't know
what she
Updated from 10.04 tonight. After a few hours of use, noticed numlock
turning off and on as if my keyboard was shorting. Confirmed gnome-
settings-daemon consuming 150% cpu. I had been using Chrome,
Calculator, and Image Viewer. Killing gnome-settings-daemon returned
normal use of numlock, but
Hello. I had this issue too.
It was solved by running 'gsettings set org.gnome.settings-
daemon.peripherals.keyboard remember-numlock-state false' as Коренберг
Марк (socketpair) suggested.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi. Post #107 seems to have corrected it for me. All of my 8 ubuntu PCs
were exhibiting this issue and all have stopped after disabling the
numlock state. Two of those PCs were having the problem as I was fixing
the setting and the Numlock-State field in dconf-editor was changing
rapidly between
I wanted to comment (again) this bug is still happening, I have been
unable to catch when it starts, but will usually happen over night when
the system is under very heavy load, CPU or GPU. The load levels I am
talking about is a normally very responsive system will take 2-5 seconds
(if not more)
i saw numlock turning on/off by it self many times,
one way i can always reproduce this bug is:
1. enable remote desktop sharing (vino)
2. connect to this computer remotely with vnc
3. remotely enable/disable numlock multiple times
4. remotely type some number with numpad keys
5. remotely
** Changed in: gnome-settings-daemon
Status: Confirmed = Incomplete
--
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]:
** Changed in: gnome-settings-daemon
Status: New = Confirmed
--
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
I've had this issue repeatedly. Here are the apps I typically have open
when this occurs: Firefox 14, Gnome Terminal, GEdit. This is running in
VirtualBox. Looking at strace and .xsession-errors, I see that gnome-
settings-daemon appears to be getting into some sort of infinite loop.
Hopefully
I notice that after killing gnome-settings-, dconf-service is the
responsible for high IO usage (using iotop), after killing dconf-
service, the IO stop and the system becomes responsible again.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I notice a pattern. When I'm running the following aplications:
Thunderbird 15, Firefox 15, gnome-terminal, Netbeans 7.1.2, gedit,
Rhythmbox
on Unity 2D, and I try to open the following page on firefox:
http://www.thegeekstuff.com/2009/03/15-practical-unix-grep-command-
examples/
The issue
I don't want to speak too soon but, Коренберг Марк... I think I Love
You!!!
--
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]:
I changed my pc.
With this new one, intel sandy bridge generation and Ubuntu 12.04.1 x64
installed, against the old one with core duo generation and ubuntu 12.04
x86:
after a VNC session the cpu consumption is high for vino-server process
(100%) but I don't see the num lock led blinking on the
Comment #107 fixes the problem here :)
--
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
Workaround (!) was the disabling of 'remember numlock state' or whatever
it was called.
--
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]:
$ sudo apt-get install dconf-tools
$ dconf-editor
$ Go to org.gnome.settings-daemon.peripherals.keyboard
$ uncheck remember-numlock-state checkbox
And you are done!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon
This is happening to me with an USB keyboard on an IBM ThinkPad X41. g-s-d goes
to 100% CPU and the numlock led starts blinking in a crazy and irregular way.
The X41 BIOS has the option to keep the internal keyboard numlock separated
from the external keyboard one selected; so only the led on
I'm also seeing this problem. Removing the keyboard.gnome-settings-
plugin file makes it go away, but it also means I can no longer use my
Dvorak (default) keyboard layout, so I have to live with this bug.
It's mainly problematic for me not so much because of the CPU burning
but because of its
I was able to easily reproduce the bug by using Synergy as client in the
affected machine. After using the numeric keypad and/or toggling numlock
from the keyboard on the server machine (but with the focus on the
client machine), the problem appears.
Can this also be reproduced by remotely
I can reproduce this message when clicking caps lock on a computer with
a backlit keyboard (Dell E4310).
--
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:
at lest for me, the problem reappears even after removing /usr/lib
/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin and killing
gnome-settings-daemon. after a period of usage as described in #98 i'm
back to gnome-settings-daemon using 100% CPU.
--
You received this bug notification
I'm seeing this on 12.04 with 3.4.2-0ubuntu0.2.
It's not only eating most of the CPU, but also tons of memory - this morning I
unlocked the computer and g-s-d had 4.3GB VIRT, 3.2GB RES!
After killing, it only takes 450M VIRT and 8M RES.
--
You received this bug notification because you are a
After turning on Control pointer using they keypad in Universal access
I can trigger the bug 100% of the time by using the keypad to control
the mouse when browsing the web with Google Chrome. Editing /usr/lib
/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin as suggested
in #85 seems to
spoke to soon. editing the file as suggested in #85 does not fix the
issue for me. removing the file completely as suggested in #33 does seem
to fix it though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in
I think comment #85 has nailed this one. I removed the translated
strings from keyboard.gnome-settings-plugin and have have not seen this
issue since ( 1 week of operation). Best of all, I can keep my keboard
repeat rate fast and delay low (how anyone can stand slow or delayed
keyboard replace I
I think I triggered this just opening a localhost VNC connection by
accident using Gtk VNC Viewer, but maybe it was another thing, since I
was multitasking at that time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
hi guys,
May someone will be helpful.
I have same problem on desktop after upgrade from 11.10. At same time on my
netbook with clean installation 12.04 i didn't discover it.
I use 2 layouts EN and RU. And usually after i m back to office on morning, my
system is dieing under gnome-settings
** Visibility changed to: Public
--
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
That bug is neither private nor a security issue, please don't play with
those settings
--
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]:
1 - 100 of 139 matches
Mail list logo
