Bug 202761 - System tray is empy after upgrade to 4.3
Summary: System tray is empy after upgrade to 4.3
Status: RESOLVED DUPLICATE of bug 192919
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemtray (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-06 09:46 UTC by Michal Svoboda
Modified: 2009-08-07 09:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
first screenshot (64.94 KB, image/png)
2009-08-06 11:39 UTC, Michal Svoboda 		Details
second screenshot (57.68 KB, image/png)
2009-08-06 11:39 UTC, Michal Svoboda 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Svoboda 2009-08-06 09:46:09 UTC 
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Unlisted Binary Package

As I upgraded to 4.3, all my systray icons disappeared. If I use a theme that has non black background i can see black squares where the icons used to be.
Comment 1 FiNeX 2009-08-06 10:16:23 UTC 
The old summary was really unuseful. A screenshot could be more interesting.
Comment 2 Michal Svoboda 2009-08-06 11:39:10 UTC 
Created attachment 35903 [details]
first screenshot
Comment 3 Michal Svoboda 2009-08-06 11:39:31 UTC 
Created attachment 35904 [details]
second screenshot
Comment 4 Michal Svoboda 2009-08-06 11:40:00 UTC 
There you go, it does not even display the black boxes after the applet is removed and added again.
Comment 5 Aaron J. Seigo 2009-08-06 13:37:10 UTC 
.. and every single time this problem gets reported it is one of:

* bad Qt version
* bad x driver
* bad x.org configuration

(usually the latter)
Comment 6 Michal Svoboda 2009-08-06 14:27:01 UTC 
What do you mean by bad x.org configuration?
Comment 7 Dario Andres 2009-08-06 15:01:19 UTC 
- Can you check that certain items like "KMix" will be shown properly? 
Also, try reading bug 192919, it has some tests and workarounds to apply.
Thanks
Comment 8 Michal Svoboda 2009-08-07 09:21:16 UTC 

*** This bug has been marked as a duplicate of bug 192919 ***