Kopete icon disappears from notification area after gnome-panel reload

Bug #101996 reported by Wesley Stessens
12
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Low
Unassigned

Bug Description

When using Kopete in the GNOME desktop environment, the Kopete tray icon doesn't recover itself in the notification area when gnome-panel reloads itself (for example: when a gnome-panel crash occurs or when a user reloads gnome-panel manually)

This causes problems, because you will be unable to access Kopete if it is minimized to the tray, and you have to kill the process and start it again to get the tray icon back.

Changed in kdenetwork:
status: Unconfirmed → Rejected
Revision history for this message
Wesley Stessens (wesley) wrote :

Hobbsee, you rejected this bug, but you didn't tell why. What's wrong with the bugreport? Please tell me so I can make a better one, or so I can post the bug in the right place. Should I post a bugreport upstream to the KDE developers? Please reply.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

argh. my bugmail has gone strange.

I thought heno replied to this bug, for some reason, and rejected it (so i should have marked this one as a dupe of the other, but was lazy)

Changed in kdenetwork:
status: Rejected → Unconfirmed
Revision history for this message
billstei (billstei) wrote :

FWIW I wonder if there is a more general problem with KDE apps going into the Gnome system tray, as I have had issues for months now on Edgy/Gnome 2.16.1 with Konversation putting it's icon into the Gnome tray. Sometimes I get it, sometimes no icon with a blank spot, and sometimes as an icon in the upper left of the desktop (and my tray is at the bottom) It seems to depend on which *other* apps are maximized/minimized, or more likely the width of their task bar buttons/labels (i.e. not in the tray, but next to it on the left).

I have not tested Feisty/Gnome 2.18

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still an issue in Intrepid?

Changed in kdenetwork:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdenetwork:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.