Version: 1.9.3 (using KDE KDE 3.5.3) Installed from: Ubuntu Packages OS: Linux I run KMail from Gnome I have the Notification Area applet in my Gnome panel to support Systray Icons (this is a Freedesktop specification, supposed to work indifferently from KDE or Gnome). When I use KMail, at first the icon is where it should be, showing what it should be. Then when time passes and that KMail check for new mail, the icon disappear from the notification area, and then is floating somewhere on the screen. Sometime it even turns into its own window. I don't know if it is a bug in Kmail or in Gnome notification area, but at one point it has worked properly. I use KMail from the 3.5.3-0ubuntu0.1 ubuntu package provided by jriddel. For Gnome it is Gnome 2.14 from Ubuntu Dapper 6.06
Did you try other kde applications that have a tray icon? Did you try using something else that manages/swallows tray icons (kicker, fluxbox slit, ....)? At what point of time did the trayicon work properly? Usually software doesn't stop working without a reason. I suggest to rethink about recently updated software. It could of course be a bug in the kde trayicon class (that's what kmail uses), that would be a kdelibs bug then.
I didn't upgrade anythoing a the time it stopped working properly. I have upgraded to 3.5.3 since for other reasons. Strangely Amarok 1.3 works fine with the Systray.
I think the problem disappeared since I restarted the whole thing. It was probably gnome-panel the guilty Gnome in my computer. Closing WFM. I'll reopen if it ever happens again. (maybe I should switch ti kicker, hint, hint)
I consistantly reproduce this bug. Akregator behaves correctly, but KMail never goes to the system tray, but bounces around the screen in a little 16x16 window when you close to the system tray.
Oh this is with 3.5.6
*** Bug 146441 has been marked as a duplicate of this bug. ***
I have also seen this problem when switching window managers, for example when trying out Beryl out KWin in KDE4.
Is this still a problem with recent software?
No response. Closing because of that. Please report if you still see this issue.