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  gnome-settings-daemon                          3.8.5-0ubuntu11.2            
                 amd64        daemon handling the GNOME session settings
$ uname -a
Linux faui49y 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux


afaik, this didn't happen on 13.04.

-- 
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:
  Unknown

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     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to