Bug 170981 - Akregator displays two icons in the system tray
Summary: Akregator displays two icons in the system tray
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-13 14:02 UTC by Emmanuel Surleau
Modified: 2008-12-01 14:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Emmanuel Surleau 2008-09-13 14:02:19 UTC 
Version:           1.3.1 (using 4.1.1 (KDE 4.1.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-5.slh.3-sidux-686

Akregator displays two icons in the system tray at startup (when restored from previous session). Both are functional. Using 'Quit' closes the application and removes the two icons. Restarting the application displays only a single icon in the system tray.
Comment 1 George Kiagiadakis 2008-09-13 14:20:06 UTC 
This is a known bug in 4.1.1. It happens because the buggy kjs debugger opens a new hidden KMainWindow with every khtmlpart (see bug 167826 and bug 169881) and that window is saved in akregator's session file, which causes the session restore code to malfunction. I have talked with Frank Osterfeld about that, a fix should be on the way.
Comment 2 FiNeX 2008-11-30 21:25:47 UTC 
Has it been fixed? I cannot reproduce using current trunk.
Comment 3 Emmanuel Surleau 2008-12-01 00:28:46 UTC 
Think so. I'm currently on 4.1.3 and haven't seen it happen for a long while. I'd say it can be marked as resolved and go to the big bugtracker in the sky.
Comment 4 FiNeX 2008-12-01 14:27:12 UTC 
Ok. Thanks for the feedback!
Comment 5 George Kiagiadakis 2008-12-01 14:44:04 UTC 
This is not reproducable because bug 169881 is fixed, but it's not really fixed from akregator's side afaik, so it will reappear if we ever get a bug similar to 169881. But In the meantime, I think this bug can stay closed ;)