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 645074 - evolution-alarm-notify keeps running after session logout
evolution-alarm-notify keeps running after session logout
Status: RESOLVED DUPLICATE of bug 646117
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-03-17 21:24 UTC by Pacho Ramos
Modified: 2011-05-12 08:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pacho Ramos 2011-03-17 21:24:52 UTC 
I am seeing this since updating to evolution-2.32 (I am now running evo-2.32.2): evolution-alarm-notify process is not killer at session logout and, then, if I login/logout multiple times, I see a lot of evolution-alarm-notify processes kept around.

Thanks for solving this
Comment 1 Matthias Clasen 2011-03-18 11:42:51 UTC 
A very low-tech, one-line fix to this kind of problem is to just connect to the session bus.
Comment 2 Milan Crha 2011-04-29 09:45:41 UTC 
I tried to reproduce this under Fedora 15 beta and it works fine, the alarm notification daemon is closed as soon as I logout from X. Maybe it's related also to bug #646117.

Are you able to apply fix from there and test in your environment, please? Of course, if you are fine that actual stable has this fixed, then I'm even happier.
Comment 3 Akhil Laddha 2011-05-10 06:35:28 UTC 
Shall we keep the bug open or close it ?
Comment 4 Pacho Ramos 2011-05-10 08:17:35 UTC 
The patch looks to fix the problem, can it be committed to 2.32 branch also?
Comment 5 Pacho Ramos 2011-05-10 08:17:49 UTC 
The patch looks to fix the problem, can it be committed to 2.32 branch also?
Comment 6 Milan Crha 2011-05-12 08:07:51 UTC 
I wrote your request to yours bug #649854. I'm closing this as a duplicate. Thanks for testing.

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