Version: (using KDE 4.1.0) Installed from: Compiled From Sources Compiler: GCC 4.3.1 OS: Linux Hi there, since i updated to Qt 4.4.1 the systray icons are not drawn on startup of KDE 4.1... The icons take their space in the tray, they just dont show and the tray is empty... To solve this i have to remove and then add the systray applet again... Downgrading to Qt 4.4.0 solves this problem... If you need any more info, i am glad to help Greetings Jan
Confirmed.
Confirmed. It's annoying.
Confirmed. Readding System tray seems to make it reappear (when "panel settings" bar is closed). But on the next login, it is empty (or simply hidden somewhere) again.
*** Bug 168087 has been marked as a duplicate of this bug. ***
The same thing on my computer. Confirmed
The bug is already confirmed enough. Please stop the "me too!", thanks.
Confirmed
I can confirm with this with Qt 4.4.1 installed, sometimes I can make the icon show in systray by re-adding this widgets, but most time I can not see the icons.
confirmed
Before adding another "confirmed", please read comment #6.
Hi, Jason Stubbs could you give a link to the "comfirmed bug" regard
*** Bug 168325 has been marked as a duplicate of this bug. ***
No bug is confirmed enough until the status actually changes to 'confirmed'. Confirmed on archlinux.
Nick, as you can see the status of the bug is NEW. Which means it has been confirmed. Otherwise it would be at UNCONFIRMED. Please read http://bugs.kde.org/bug_status.html .
Ah, of course. Always pleased to make myself look like an idiot.
*** Bug 168386 has been marked as a duplicate of this bug. ***
I can work around this bug by moving the panel to the right edgke of the desktop and back to the bottom. After I lock the widgets the icons appear in the systray. Might be a bit easier than re-adding the systray.
Workaround works for me too.
Even with this "workaround" the systray disappears when clinking the plasma icon on the panel; and reappears when cosing the config panel.
SVN commit 842541 by jstubbs: Make sure that the widget is on top after being created. raise() isn't working for some reason, so this is a hack on top of a hack. ;) Note, the system tray still isn't visible during panel configuration. Thanks to Matthias Kretz for digging through subversion changes. CCBUG: 168007 CC: plasma-devel@kde.org More details to come in a reply to this on panel-devel@ M +11 -0 systemtraywidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=842541
report: this bug is resolved after i update my sytem. anyone else? 2008/8/5 Ivo Anjo <knuckles@gmail.com> [bugs.kde.org quoted mail] <div dir="ltr">report:<br>this bug is resolved after i update my sytem. anyone else?<br><br><br><div class="gmail_quote">2008/8/5 Ivo Anjo <span dir="ltr"><<a href="mailto:knuckles@gmail.com">knuckles@gmail.com</a>></span><br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br> You are on the CC list for the bug, or are watching someone who is.<br> <br> <a href="http://bugs.kde.org/show_bug.cgi?id=168007" target="_blank">http://bugs.kde.org/show_bug.cgi?id=168007</a><br> </div>knuckles gmail com changed:<br> <br> What |Removed |Added<br> ----------------------------------------------------------------------------<br> CC| |knuckles gmail com<br> </blockquote></div><br><br clear="all"><br>-- <br>世界没有尽头 所以会茫然<br> </div>
See my message in comment #20. If it works in panel configuration mode and/or you updated before comment #20 was posted, then please add more information - distro and whatnot. Otherwise, the only useful comments on this bug are those explaining the _why_.
Created attachment 26652 [details] sytray fix for Qt4.4.1 please, find attached a fix for Qt4.4.1 from Matthias Kretz.
That would be a regression as far as Qt is concerned. My mail on plasma-devel@ has the details: http://mail.kde.org/pipermail/plasma-devel/2008-August/000258.html
*** Bug 168503 has been marked as a duplicate of this bug. ***
SVN commit 843617 by jstubbs: Removing the raise() hack as going with Qt::AA_DontCreateNativeWidgetSiblings is the better option for the time being. I extended the raise() hack to include watching parentWidget()'s events and calling raise() whenever on all ChildAdded events (which works) but the huge white flashes with native widgets aren't really acceptable. CCBUG: 168007 M +0 -11 systemtraywidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=843617
SVN commit 843619 by jstubbs: Revert to Qt-4.4.0 behaviour so that the SystemTrayWidget is always on top. This needs to be backported to the 4.1 branch. BUG: 168007 CCMAIL: plasma-devel@kde.org M +14 -0 systemtray.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=843619
I hope that this will be backported BEFORE the distributions pack the 4.1 it's extremely annoying to not being able to access kmail and klipper sitting in the systray
Don't worry, I think distributions follow this bug report closely. Mandriva will include this patch in the future Mandriva 2009.0 (it's already in the development version, cooker, and works pretty well).
I'll get it into the 4.1 branch on the weekend if nobody else takes care of it first.
SVN commit 843908 by fabo: backport Qt4.4.1/systemtray fix to 4.1 branch. CCBUG: 168007 CCMAIL: jasonbstubbs@gmail.com M +20 -0 systemtray.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=843908
I've recompiled kdebase-workspace with this patch for myself, systray was obviously fixed, but however there're some artifacts when icons are added to it on startup and on some icons the image is like the proper icon overlays the one to the left of its position (screenshot will follow). But though, thank you for this fix, because without systray it's completely insane working.
Created attachment 26753 [details] Screenshot of the artifact in systray
That looks to be bug #158094
Thanks for the link, it really must be those bug and I've read it has a long story.. Sorry for filing it here.
*** Bug 169069 has been marked as a duplicate of this bug. ***
Reporting this bug too