Public bug reported:
If the Num lock key is toggled rapidly, there's a chance that
mate-settings-daemon will go into runaway CPU usage (causing Xorg to also
appear to be in runaway CPU usage), and the Num lock LED will flash/blink
erratically (randomly--this is not the steady 2Hz blinking when a kernel panic
occurs). By killing mate-settings-daemon, the system can recover;
mate-settings-daemon respawns, Xorg goes back to normal CPU usage, and the Num
lock LED is stable.
This behavior is present on an up-to-date installation of Ubuntu MATE 14.10
(beta 1)as well as the LiveCD.
This seems to apply only to hardware Num lock toggling, as rapid toggling in
onboard does not seem to cause the issue. The same does not appear to happen to
the caps lock key. The state of num lock is indeed indeterminate when this
occurs (e.g. numeric 4 will vary between typing '4' and left-arrow).
This appears to be directly related to prior CPU availability, as it is more of
a problem on older hardware (e.g. with 2001 Pentium M) where it can be
triggered on an idle system, and more difficult to duplicate on later hardware
(e.g. with a dual-core processor) unless the CPUs are busy (e.g. other runaway
processes).
Only tested on 32-bit; will upload apport info.
** Affects: ubuntu-mate
Importance: Undecided
Status: New
** Affects: mate-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mate-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
If the Num lock key is toggled rapidly, there's a chance that
mate-settings-daemon will go into runaway CPU usage (causing Xorg to also
appear to be in runaway CPU usage), and the Num lock LED will flash/blink
erratically (randomly--this is not the steady 2Hz blinking when a kernel panic
occurs). By killing mate-settings-daemon, the system can recover;
mate-settings-daemon respawns, Xorg goes back to normal CPU usage, and the Num
lock LED is stable.
- This behavior is present on an up-to-date installation as well as the LiveCD.
- This seems to apply only to hardware Num lock toggling, as rapid toggling in
onboard does not seem to cause the issue. The same does not appear to happen to
the caps lock key. The state of num lock is indeed indeterminate when this
occurs (e.g. numeric 4 will vary between typing '4' and left-arrow).
+ This behavior is present on an up-to-date installation of Ubuntu MATE 14.10
(beta 1)as well as the LiveCD.
+ This seems to apply only to hardware Num lock toggling, as rapid toggling in
onboard does not seem to cause the issue. The same does not appear to happen to
the caps lock key. The state of num lock is indeed indeterminate when this
occurs (e.g. numeric 4 will vary between typing '4' and left-arrow).
This appears to be directly related to prior CPU availability, as it is more
of a problem on older hardware (e.g. with 2001 Pentium M) where it can be
triggered on an idle system, and more difficult to duplicate on later hardware
(e.g. with a dual-core processor) unless the CPUs are busy (e.g. other runaway
processes).
Only tested on 32-bit; will upload apport info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364111
Title:
Num lock toggling causing mate-settings-daemon, xorg cpu runaway, LED
astable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1364111/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
