Bug 240021 - Tray icon stays shown after crash
Summary: Tray icon stays shown after crash
Status: RESOLVED DUPLICATE of bug 232915
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.3.0.90
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-29 22:06 UTC by Vladislav Bogdanov
Modified: 2010-05-30 08:58 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vladislav Bogdanov 2010-05-29 22:06:09 UTC 
Version:           2.3.0.90 (using KDE 4.4.3) 
OS:                Linux

Tray icon is shown in system tray after occasional amarok crash.
Yes, I understand that crash should never happen, but...
Now I'm unable to take it away. If I run one more copy of amarok, new additional tray icon is shown.
Backtrace is unavailable, but it doesn't seem to be needed. Shouldn't you add icon disposal at sigsegv signal handler?

Reproducible: Didn't try
Comment 1 Myriam Schweingruber 2010-05-29 22:16:27 UTC 
Logging out of KDE and in again should solve that for now. Is the crash you had a known issue? If not, a backtrace could be informative.
Comment 2 Vladislav Bogdanov 2010-05-30 08:39:46 UTC 
Is there another way instead of logging off?

I do not know much about crash, I was several days ago, and I think it is acceptable at the beta stage.

But that lost tray icon is really annoying :)

Logging in is a quite long procedure in my case, cryptodisks, ssh keys, etc.
Comment 3 Mikko C. 2010-05-30 08:43:05 UTC 
You didn't use KDE 4.5 by any chance?
Does the icon disappear if you quit amarok normally? (No crash).
If it doesn't, then this is not an amarok bug, instead see bug 232915
Comment 4 Vladislav Bogdanov 2010-05-30 08:57:55 UTC 
> You didn't use KDE 4.5 by any chance?

Nope, 4.4.3
> Does the icon disappear if you quit amarok normally? (No crash).

Yes. But previous one (from the crashed session) remains there.

> If it doesn't, then this is not an amarok bug, instead see bug 232915

All other symptoms are the same with that bug.

I think we can mark this one as a duplicate of that.
After a bit of thinking I'm sure it is a bug of new trayicon framework and amarok has little to do with it.
Comment 5 Vladislav Bogdanov 2010-05-30 08:58:21 UTC 

*** This bug has been marked as a duplicate of bug 232915 ***