GNOME Bugzilla – Bug 330143
An unusable empty space grows up in the notification area
Last modified: 2006-02-12 11:31:38 UTC
Please describe the problem: Simply use the notification area on a transparent panel. You will see vertical lines. When I start my computer, I can see 2 or 3 of those lines. But sometimes, when I add or remove a software that uses the notification area, one line is added. Sometimes more. Steps to reproduce: 1. Use notification area on a transparent panel 2. Start and stop a few times applications like gajim, liferea, update notifier, amule... 3. enjoy Actual results: Expected results: Does this happen every time? Yes. This bug is a long standing bug for me. I think it was always there but I didn't care since I was lazy and I use rarely a transparent panel. Other information: Note that the "ugly" factor is not alone. There is also a waste of space that can be very annoying on a filled panel.
Created attachment 58815 [details] Screenshot of the problem See the screenshot. I'm running amule, gajim, liferea and update notifier.
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 100600 ***
Hello Seb, sorry for annoying you but I'm not entirely conviced that this bug is the same as #100600 As far as I understand, #100600 and all duplicates seems to speak mainly about having a transparent background for icons. But this one is not to speak about this. It's to speak about the unused space in the notification area that grows up each time you launch an application. This bug can be seen very well in the case of a transparent background because the wasted space is "some weird vertical lines". But I saw that this bug also apply to non-transparent panel. It's invisble but the wasted space still exist. From an user point of view, it's a very different thing than #100600. By reading my bug again, I understand that my title was very confusing. I will change it. I let you reopen the bug if you agree with me. Ignore if technically speaking, my issue is the same as #100600 Cheers ;-)
There's also a bug open about this, most probably in libegg.