Bug 301497 - Audacious icon not visible in the tray
Summary: Audacious icon not visible in the tray
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemtray (show other bugs)
Version: 4.8.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: http://redmine.audacious-media-player...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-09 08:49 UTC by mkkot
Modified: 2012-06-19 18:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Audacious no systray icon (23.14 KB, image/png)
2012-06-09 08:51 UTC, mkkot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mkkot 2012-06-09 08:49:09 UTC
This has already been reported to audacious' developers but the answer was "We just use GtkStatusIcon, so there's not really much we can do. Sorry."

After KDE 4.8.2 > 4.8.3 update there is no audacious tray icon wisible in KDE, although you can use it as well as it was there. So right-click menu works, mouse wheel scroll over works, it takes place between other icons, but the very graphics is not visible.

I removed ~/.config/audacious and checked version 3.2.2 and 3.2.3.

On the provided screen Audacious' icon should be placed between white kmail's icon and yellow psi icon.

Reproducible: Always

Steps to Reproduce:
1. Install audacious
2. Enable tray icon in plugins
Actual Results:  
 Icon takes place in the tray but it's invisible

Expected Results:  
The icon graphics should be visible

It worked in 4.8.2
http://redmine.audacious-media-player.org/issues/121
Comment 1 mkkot 2012-06-09 08:51:30 UTC
Created attachment 71679 [details]
Audacious no systray icon
Comment 2 mkkot 2012-06-14 18:28:11 UTC
Funny enough, I was using nouveau. Now switched back to nvidia binary driver and icon is there.
Comment 3 Jekyll Wu 2012-06-14 19:25:00 UTC
It works for me when using either nouveau or the binary blob. I'm using KDE SC 4.9 beta2 at the moment.
Comment 4 Myriam Schweingruber 2012-06-19 18:59:02 UTC
Looks like not something we can do much about if it is a driver related issue