Volume notification pops up and never go off using 100% cpu

[Federico Foschini]

When I change the Volume with my external laptop wheel the notification windows pops up and hangs there using 100% cpu untill I manually restart X server.

[Chris Coulson (chrisccoulson)]

Which process is using 100% cpu when this happens?

[Ara Pulido (ara)]

We would also need more information about your configuration:

Could you please run this command:

$ apport-collect 376840

That will attach some useful information to the bug report.

Thanks

[Motin (motin)]

Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.11-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse sambashare video www-data

[Motin (motin)]

I am experiencing the same behavior right now. Very annoying. It's notify-osd and X that takes up around 43% each of the cpu. The rest is used by other apps, mostly firefox. Just ran that command as you can see.

[Motin (motin)]

I tried inactivating the keyboard shortcuts for changing the volume without luck. Also ran xev to see if my hotkeys were spamming key presses to X. They are not. Gotta log out now...

[AvA (inetava)]

Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.11-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Federico Foschini (undicizeri)]

Architecture: i386
DistroRelease: Ubuntu 9.04
Package: notify-osd 0.9.11-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Chris Coulson (chrisccoulson)]

Do any other notifications work after this happens? Is this repeatable with a new user on your system (or using the guest account)? Could you run "dbus-monitor --session 2>&1 | tee ~/session-bus.log", press a volume button and see if the session bus is being flooded with notifications.

Thanks

[AvA (inetava)]

>>Do any other notifications work after this happens?
Yes
>>Is this repeatable with a new user on your system (or using the guest account)?
Yes
>>Could you run "dbus-monitor --session 2>&1 | tee ~/session-bus.log", press a volume button and see if the session bus is being flooded with notifications.
see attach file

[ChrisMoraes (moraes-christopher)]

This does not seem to be a duplicate of the bug it is linked to.

I have observed this bug on Ubuntu 9.04 and Linux Mint 7, both running in VirtualBox on a Win XP host.

This behaviour seems to be trigged randomly. Suddenly the volume notification (from notify-OSD) pops up and takes 100% CPU. Teh keyboard becomes unresponsive and nothing can be typed in. The mouse responds and the UI can be clicked. The only solution that works is to log out and log in again.

[Mirco Müller (macslow)]

Chris, have you tried notify-osd 0.9.24 yet?

[Motin (motin)]

I realized that one trigger to this was my hardware! I run a Dell XPS M1330
and the media buttons seems to be activated by the heat or pressure of the
LCD when the lid is closed! That means that if I close the lid for a couple
of minutes, the lid will spam X with these events. I guess it has always
been so (when having media shortcuts active - which has not been too often
because of frequent breakages of these assignments between updates), but
only with the notify-osd has it become a CPU intensive issue which queues up
and imposes this annoying issue.
On Fri, Oct 23, 2009 at 11:48 PM, Mirco Müller
<email address hidden>wrote:

> *** This bug is a duplicate of bug 367049 ***
> https://bugs.launchpad.net/bugs/367049
>
> Chris, have you tried notify-osd 0.9.24 yet?
>
> --
> Volume notification pops up and never go off using 100% cpu
> https://bugs.launchpad.net/bugs/376840
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Mirco Müller (macslow)]

Am Montag, den 26.10.2009, 17:27 +0000 schrieb Motin:

> *** This bug is a duplicate of bug 367049 ***
> https://bugs.launchpad.net/bugs/367049
>
> I realized that one trigger to this was my hardware! I run a Dell XPS M1330
> and the media buttons seems to be activated by the heat or pressure of the
> LCD when the lid is closed! That means that if I close the lid for a couple
> of minutes, the lid will spam X with these events. I guess it has always
> been so (when having media shortcuts active - which has not been too often
> because of frequent breakages of these assignments between updates), but
> only with the notify-osd has it become a CPU intensive issue which queues up
> and imposes this annoying issue.

 There's already a branch available, addressing a part of the issue.
It's the first part of the solution to the described issue. Have a look
here...

        https://code.edge.launchpad.net/~macslow/notify-osd/conditional-bubble-refresh/+merge/13545

... if you are curious and want to try it yourself. Unfortunately this
didn't make it in for Karmic final, but will likely be made available as
a SRU.

Best regards ...

Mirco