GNOME Bugzilla – Bug 529023
Icon does not reappear after Notification Area applet has been removed and re-added
Last modified: 2020-03-17 08:20:35 UTC
Steps to reproduce:
1. Start Banshee with a Notification Area
2. Start Playing and Minimize Banshee into the Notification Area
3. Remove the Notification Area
4. When the Song Changes it should Start using more and more ram and start
to lag everything
How do you remove the notification area if Banshee is minimized to it? Do you have to click it to show Banshee again, go to its Edit menu etc? Have you seen the same issue on Banshee 1.0 or higher?
I've tested it with banshee-1 now, it does not crash but when you add the notification area back to the panel its icon doesnt reappear so you must kill it.
Weird coincidence: I was just browsing through critical Banshee bugs to see if I could reproduce any, and I stumbled on this one. When I started to test this one, I noticed that Banshee's icon wasn't in my panel notification area to begin with. I would assume that the reason is this: An hour ago my panel was acting strange, so I ran "killall gnome-panel". When the panel restarted, Banshee's icon wasn't there and now I have to kill Banshee. I think I accidentally confirmed this.
Could we change the version to 1.4.1, status to new, and severity to something a little lower, since this isn't exactly a crasher anymore and it's not something that users will run into during normal everyday use?
I can confirm this in svn trunk version. I started Banshee, minimised it to the notification area, removed the notification area from the panel, and added it back. After this, the Banshee icon in no longer in the notification area, I had to kill the process to close it.
Bug 575232 is a duplicate of this one, but the title of this bug should be changed. Right now it's a bit misleading.
*** Bug 582052 has been marked as a duplicate of this bug. ***
From bug #582052 :
This also happens with gnome-shell, as it replaces the entire panel, including the notification area.
Steps to reproduce:
1. Start banshee
2. Start gnome-shell and you'll see that the banshee tray icon will not be
added like the other ones.
3. If you kill the gnome-shell and it falls back to the normal gnome-desktop
also there the banshee tray icon is missing.
If you start gnome-shell first and then start banshee the tray icon appears
as expected *but* if you exit gnome-shell and it falls back to normal
gnome-desktop the banshee icon is missing.
Of note, since GTK+ 2.16, GtkStatusIcon should be able to support all of the features needed by Banshee:
* Primary click
* Secondary click
* Rich tooltips (as well as a tooltip event that should let you continue using the existing tooltip-type-thing banshee uses)
* Scroll events
Of course, you may need some stuff form gtk-sharp-beans (or have to write some bindings yourself) since there is no gtk-sharp-2.16, but that should not be too much work.
There are implications here for SLED11 support, but for users who frequently upgrade their distro, support for GtkStatusIcon would be a nice little win. There could be a build-time decision about which type of tray icon is used.
*** Bug 602730 has been marked as a duplicate of this bug. ***
Should this not be relatively simple to fix, even if by just looking at how other notification area icons seem to be able to survive the NA being restarted?
*** Bug 607031 has been marked as a duplicate of this bug. ***
Sure would be nice if this were fixed... my gnome-panel is crashing pretty regularly on me these days (that's another bug) and every time I have to kill/restart banshee.
(In reply to comment #12)
> Sure would be nice if this were fixed... my gnome-panel is crashing pretty
> regularly on me these days (that's another bug) and every time I have to
> kill/restart banshee.
You don't really need to kill/restart Banshee. You can just disable/enable the notification area icon extension. This is more clicks but probably less time. :-)
(In reply to comment #13)
> You don't really need to kill/restart Banshee. You can just disable/enable the
> notification area icon extension. This is more clicks but probably less time.
I don't actually use banshee any more (went back to rhythmbox) so I can't try to repro this, but IIRC, once I had made the banshee window disappear by clicking on the notification area icon the only way to get it back was to click on the notification area icon. But of course, once the panel is restarted and the icon gone, there is no way to bring back banshee's main window so that you can disable/enable the icon. Kinda catch-22.
*** Bug 610456 has been marked as a duplicate of this bug. ***
This should definitely be higher importance. If the window's hidden and the icon's disappeared, a restart is the only option.
Worse than that: if you have Banshee as a startup program and it happens to load before gnome-panel, you have to kill it anyway. Surely this wouldn't be hard to fix? Why has it been around for two years??
(In reply to comment #16)
> This should definitely be higher importance. If the window's hidden and the
> icon's disappeared, a restart is the only option.
Not true. Just do whatever one normally does to start Banshee, and the window will reappear. Run `banshee-1` from a terminal, or click it in the Application menu, or select it from gnome-do...all of those will bring the window back.
If I were a user whose notification area icon disappeared, and I thought Banshee was gone, that is the first thing I would try.
> Worse than that: if you have Banshee as a startup program and it happens to
> load before gnome-panel, you have to kill it anyway.
What do you "have to kill", and why? And does this actually happen to you? I'd be surprised if banshee started before the panel, but if it happens to you then I would agree that is more likely to cause a user problems/confusion than the panel crashing.
> Surely this wouldn't be hard to fix?
Statements like this aren't helpful. If you don't think it's hard, then please submit a patch.
> Why has it been around for two years??
Because it is labeled as a minor bug, there are plenty of higher-priority bugs keeping folks busy, the developers have limited time, and nobody else has volunteered a patch. Welcome to open source software.
(In reply to comment #17)
> Statements like this aren't helpful. If you don't think it's hard, then please
> submit a patch.
I wouldn't be able to provide a patch myself (although I'd love to contribute when I have the skills), so apologies if it's less simple than I think.
> What do you "have to kill", and why? And does this actually happen to you?
I was referring to banshee, although I was unaware banshee-1 would invoke the window. In any case, this does happen to me on about 1 out of 3 logins and gnome-panel starting before banshee seems the most likely cause.
*** Bug 650146 has been marked as a duplicate of this bug. ***
*** Bug 685296 has been marked as a duplicate of this bug. ***
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.
Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.