After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610456 - notification extension should survive removal scenerio in the notification area
notification extension should survive removal scenerio in the notification area
Status: RESOLVED DUPLICATE of bug 529023
Product: banshee
Classification: Other
Component: User Interface
git master
Other Linux
: Normal minor
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-19 14:10 UTC by David Nielsen
Modified: 2010-02-19 16:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Nielsen 2010-02-19 14:10:34 UTC 
I've noticed that if I add a second notification area apple with banshee loaded, then delete the original notification area applet other notification objects survive but banshee is nowhere to be found. disabling then enabling the notification extension brings back the notification icon. 

Why would a user do such a silly thing one might ask. In the case where a bug caused a reduction in the screen resolution, due to a design or bug when restored can reshuffle the notification area applet and in case of Ubuntu Lucid the application indicator applet. 
This looks different and simply moving them back can lead to the notication area to be loaded at an offset that looks unappealing so rearranging the applets with a second and thus clean notification area applet then removing the original.

Fairly minor issue though
Comment 1 Michael Martin-Smucker 2010-02-19 16:48:54 UTC 
This seems similar enough to 529023 that I'm going to mark it as a duplicate.  If you disagree, or if I've misunderstood, feel free to reopen this.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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