GNOME Bugzilla – Bug 344463
Alarm icon doesn't disappear on Notification Area applet .
Last modified: 2013-09-13 00:49:40 UTC
Please describe the problem: Alarm icon doesn't disappear on Notification Area applet . Steps to reproduce: 1. alarm setup 2. popup alarm and appointment dialog 3. closed alarm and appointment dialog Actual results: Expected results: Does this happen every time? yes, always. Other information: os : fedora development evolution-2.7.2.1
I'm seeing this as well. On 2.7.4.
Still seems to be present in 2.7.91
Still present in 2.7.92. This is a RATHER frustrating bug, since if I have a lot of meetings in one day, this can fill up my panel pretty damn quick. Plus, if you snooze a meeting, you get a second one. Can we PLEASE get this fixed for the 2.8 release??
Ryan, you should enable /apps/evolution/calendar/notify/notify_with_tray . It should be part of configuration too. The tray impl is buggy if 2 events are waiting. Ill fix them asap.
No it is just a local change. It works well. Just that it is not yet part of configuration, should be the bug IMO
Hmm, Im wrong. If you have latest Gtk, the tray feature is broken. Ill attach the patch. It has to be committed to head. The icon wont getaway from tray.
Created attachment 71897 [details] [review] Proposed patch This should fix the issue. Chen can you review it?
Committed the patch to make the tray to work well in HEAD. Please enable the key to have your alarm come in tray applet. Thanks for the bug, it really helped me fix a hidden issue. You may file a seperate bug to have a conf for it.
Srini, is this going to be in Evolution 2.6.4 as well?
Mathew, Im dont know the behaviour in 2.6.x Is the same issue happening there too. This happens only with gtk version > 2.9.x.
there won't be a 2.6.4 *release*, 2.6.3 was the latest for the gnome 2.14.x series. matthew, does fedora ship gtk 2.10 on gnome 2.14?
Fedora Core 5 ships GTK+ 2.8 and GNOME 2.14. I was led to believe there would be a 2.6.4 by this comment: http://bugzilla.gnome.org/show_bug.cgi?id=349413#c17
*** Bug 354935 has been marked as a duplicate of this bug. ***