Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40966 - [volumeicon] 100% cpu if soundcard is disconnected (+patch)
Attached to Project:
Community Packages
Opened by Steven Honeyman (stevenhoneyman) - Tuesday, 24 June 2014, 20:38 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 03 July 2014, 23:39 GMT
Opened by Steven Honeyman (stevenhoneyman) - Tuesday, 24 June 2014, 20:38 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 03 July 2014, 23:39 GMT
|
DetailsDescription:
If you unplug your soundcard, volumeicon goes into an infinite loop when ALSA can't see the card. This causes CPU usage to go to 100% (bug is also in 'official release 0.5.0' - the code responsible for this hasn't changed at all even in Git release) Steps to reproduce: 1. Start volumeicon (any version) 2. Unplug soundcard 3. Watch CPU go to 100% Fix: As upstream seems dead (no reply to my github pull request, or email(s) even from months ago), I've attached an incredibly simple patch which fixes this problem. The author just forgot to pass G_IO_ERR status to his handle_events function, so without this patch, it never sees the error! I know Arch policy isn't to patch code... but unfortunately, upstream is gone :( |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Thursday, 03 July 2014, 23:39 GMT
Reason for closing: Fixed
Thursday, 03 July 2014, 23:39 GMT
Reason for closing: Fixed
volumeicon-fix_100_cpu_bug.pa...
It's only Gtk2 supported, but some recent commits on Git. I've raised a few tickets for obvious bugs, so will see if they get a reply or not
It is a real shame. Everything else is either meant for a bloated DE, a dead project, or is just a messy Python script etc.
I've replied to your other comment in the related bugreport too (patches applied to my github fork)
Thanks,
Steven.