| Summary: | Dead kmix icon in systray | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Clemens Eisserer <linuxhippy> |
| Component: | widget-systemtray | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | asraniel, codenamed004, evorster, henryusp, johnvarouhakis, luca.tagliaferri, notmart, tampakrap, thev00d00 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
How the systray looked before I closed kmix
systray after closing&starting kmix Screenshot |
||
|
Description
Clemens Eisserer
2009-06-11 11:18:04 UTC
Created attachment 34426 [details]
How the systray looked before I closed kmix
Created attachment 34427 [details]
systray after closing&starting kmix
Update: After restarting KDE everything looks fine again Update2: Just happend again, this time both kmix icons respond to clicks. this could be caused either by some junk graphics behind an existing systray icon (a problem that seems still present with some drivers) or more likely a bug in the dbus systray thinghie. i suppose the culript is that kmix for a while has two systray icons for an instant when destroys the old one and creates the new one this mean in some circumstances the systray doesn't notice the dbus service gone away or it notices but doesn't clean up stuff correctly. it looks pretty hard to trigger and so to fix sigh ... *** Bug 196194 has been marked as a duplicate of this bug. *** Side note: when I see two kmix-icons, both are updated when I press the mute key. So they are not actually dead, but in some duplicated state. I'm also getting this behavior. It happens for kmix and knetworkmanager. Initially, all icons respond to clicks, until I close one, in which case the duplicates become dead. If the application(e.g. kmix) is restarted the duplicate icons that were left from before, continue to be dead and only the new one is responsive. I suppose that any duplicates created after this will be responsive, thus having some icons that can control the application and some that won't perform any function. As to the conditions that cause this to happen, I'm not really sure but I think it hapens during resolution changes(e.g. like when launching fullscreen games) and/or when watching videos in fullscreen. My setup: Debian testing/unstable Qt: 4.5.2 KDE: 4.3.1 (KDE 4.3.1) KNetworkManager: v0.8 KMix: 3.5 D-Bus Message Bus Daemon 1.2.16 Created attachment 36703 [details]
Screenshot
I am having the same problem and not only with kmix icons; this time appeared with the KOrganizer daemon. In my opinion the problem occurs when som icons changes for any reason. I also found out that removing the systray and adding again to the panel tepmorarly solves the problem. OS: Mandriva 2010 KDE: 4.3.2 KMix: 3.5 D-Bus: Message Bus Daemon 1.2.16 I am not 100% sure, but I think I had this problem with KDE 4.3 and iirc it was a Qt bug. Please try with KDE 4.4 RC and Qt 4.6 and report back setting as needsinfo, see last comment *** Bug 236936 has been marked as a duplicate of this bug. *** Confirmed here with: Qt: 4.6.2 KDE Development Platform: 4.4.75 (KDE 4.4.75 (KDE 4.5 >= 20100505)) KMix: 3.7 Removing the systray removes the icons but leaves a blank space where the icon was. I can confirm this behaviour. I saw it first on KDE 4.5.0 All compiled from source, qt-everywhere-opensource is at version 4.6.2, which did not have this bug with the previous version of KDE on top of it. Also, the Amarok icon would show a menu upon a right click before, and does not do so now. The only real change here is the KDE major version from 4.4.x to 4.5.x -Evert Vorster- Aaand, it does not happen anymore with qt-everywhere-opensource 4.6.3. I just HAD to go check to see if there was an upgrade available for Qt, and if this could maybe have been the cause, as the developers of KDE usually run the latest libraries. Looks like just upgrading Qt fixes this problem. -Evert Vorster- Closing based on comment #7 |