Bug 156700 - On plasma crash, the 3.5.x icons on system tray cease to appear.
Summary: On plasma crash, the 3.5.x icons on system tray cease to appear.
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-systemtray (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 162764 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-26 12:05 UTC by manolis
Modified: 2008-06-01 09:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description manolis 2008-01-26 12:05:15 UTC
Version:            (using KDE 4.0.0)
Installed from:    Gentoo Packages
Compiler:          gcc 
OS:                Linux

If I kill plasma and restart it:

killall plasma; plasma

My icons in system tray reappear EXCEPT the 3.5.x ones (kontact, kmail, basket) that stop show off.
Comment 1 Pino Toscano 2008-01-26 12:52:27 UTC
There is no kicker and kdesktop in KDE 4, but plasma.
Comment 2 Chani 2008-01-26 13:37:49 UTC
the weirdest thing is, if you start kmail or kontact, or get new mail after having none (so that it creates the kmail systray icon) all your icons will suddenly reappear all at once.

last time I looked at the debug output, I remember being fairly sure that the systray wasn't getting any events from which to add the non-kde4 icons.

just to confuse things even more... after a clean rebuild with latest svn, I'm not seeing this problem. I nuked my kde and build folders, but not my settings.
Comment 3 Jason Stubbs 2008-06-01 05:55:48 UTC
Works fine here too. There's not really anything that can be done on the plasma side. When the system tray starts up, it sends out a notification of its existence and then waits for requests. The 3.5 icons don't appear (under some special circumstances?) because those requests aren't sent.
Comment 4 Jason Stubbs 2008-06-01 09:41:36 UTC
*** Bug 162764 has been marked as a duplicate of this bug. ***