Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.
** Changed in: evolution (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1278429 Title: evolution-alarm-notify hangs on snooze Status in “evolution” package in Ubuntu: New Bug description: The alarm notification window becomes unresponsive on clicking "snooze". This usually happens, after I get updates in an ics file that is monitored by evolution and the due alarms are popping up. The window is modal (in foreground) and does not respond, the only way to get rid of it is a kill command: $ killall evolution-alarm-notify I started with debugging option on: $ killall evolution-addressbook-factory $ killall evolution-source-registry $ killall evolution-calendar-factory $ LANG=C ALARMS_DEBUG=1 evolution 2>&1 | tee /tmp/evolution.debug.log and got a crash on a notification, so apport should have sent another crash report at around Mo 10. Feb 13:20:00 CET 2014 The first log following here is the log for a non-crash, snooze did work this one time, but here is corrupt double linked list error in the end (took some time to appear, ca. 2 minutes). This was unfortunately not logged in the logfile (evolution.debug.log), only appeared on console. The snooze reminder did not show up. The second log is a log with a frozen notification window (see below and in evolution.debug2.log). I will add both logfiles with small comments (#) in it. To me it looks like the function "tray_list_remove_data_async" is causing these issues. BTW, why is acroread starting?!? (<- non-issue here) Thanks for looking into this. --- First log excerpt (non-crash) alarm_ready_cb (alarm.c:90): Alarm callback! alarm_ready_cb (alarm.c:100): Process alarm with trigger 1392035400 alarm_trigger_cb (alarm-queue.c:462): Setting Last notification time to Mon Feb 10 13:30:00 201 popup_notification (alarm-queue.c:1778): ... display_notification (alarm-queue.c:1642): ... open_alarm_dialog (alarm-queue.c:1452): ... alarm_trigger_cb (alarm-queue.c:504): Notification sent: 2 setup_timeout (alarm.c:157): Setting timeout for 30. 0 (from now) 1392037200 1392035400 setup_timeout (alarm.c:158): Mon Feb 10 14:00:00 2014 setup_timeout (alarm.c:159): Mon Feb 10 13:30:00 2014 notify_dialog_cb (alarm-queue.c:1342): Received from dialog notify_dialog_cb (alarm-queue.c:1350): Creating a snooze setup_timeout (alarm.c:157): Setting timeout for 5. 0 (from now) 1392035703 1392035403 setup_timeout (alarm.c:158): Mon Feb 10 13:35:03 2014 setup_timeout (alarm.c:159): Mon Feb 10 13:30:03 2014 create_snooze (alarm-queue.c:1007): Adding a alarm at Mon Feb 10 13:35:03 201 tray_list_remove_data_async (alarm-queue.c:1314): Removing 0x7f3074c38200 from tray list *** Error in `/usr/lib/evolution/3.8/evolution-alarm-notify': corrupted double-linked list: 0x00007f3074c38280 *** ---- Another try, now with the notificaton window did not responding alarm_ready_cb (alarm.c:90): Alarm callback! alarm_ready_cb (alarm.c:100): Process alarm with trigger 1392036300 alarm_trigger_cb (alarm-queue.c:462): Setting Last notification time to Mon Feb 10 13:45:00 201 popup_notification (alarm-queue.c:1778): ... display_notification (alarm-queue.c:1642): ... open_alarm_dialog (alarm-queue.c:1452): ... alarm_trigger_cb (alarm-queue.c:504): Notification sent: 2 setup_timeout (alarm.c:157): Setting timeout for 15. 0 (from now) 1392037200 1392036300 setup_timeout (alarm.c:158): Mon Feb 10 14:00:00 2014 setup_timeout (alarm.c:159): Mon Feb 10 13:45:00 2014 notify_dialog_cb (alarm-queue.c:1342): Received from dialog notify_dialog_cb (alarm-queue.c:1350): Creating a snooze setup_timeout (alarm.c:157): Setting timeout for 5. 0 (from now) 1392036602 1392036302 setup_timeout (alarm.c:158): Mon Feb 10 13:50:02 2014 setup_timeout (alarm.c:159): Mon Feb 10 13:45:02 2014 create_snooze (alarm-queue.c:1007): Adding a alarm at Mon Feb 10 13:50:02 201 tray_list_remove_data_async (alarm-queue.c:1314): Removing 0x7fc067702fe0 from tray list *** Error in `/usr/lib/evolution/3.8/evolution-alarm-notify': corrupted double-linked list: 0x00007fc067703060 *** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libevolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 10 13:06:52 2014 InstallationDate: Installed on 2013-11-25 (76 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1278429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
