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 628635 - Crash in alarm-queue.c:display_notification()
Crash in alarm-queue.c:display_notification()
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 600490 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-09-02 19:25 UTC by David Ronis
Modified: 2013-09-13 01:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2010-09-02 19:25:10 UTC
I'm not sure this is the right place to report this, but here goes.  I run the git/master of evolution and 2.31.91 of the rest of gnome (in particular of the clock applet).   When an alarm is triggered from my calendar, I get the reminder popup and then bug-buddy triggers, complaining about "Evolution Alarm Notify".  Unfortunately, when I tell it to send, something fails (invalid e-mail address or some such thing), although bug-buddy works fine for other applications.  The clock applet continues to run.

Here's the backtrace:


Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.31.90 2010-08-20 (GARNOME)
BugBuddy Version: 2.31.3

System: Linux 2.6.34-rc5-ge520683 #2 SMP PREEMPT Tue Jun 8 13:13:01 EDT 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Default
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomesegvhandler

Memory status: size: 133787648 vsize: 133787648 resident: 15310848 share: 12763136 rss: 15310848 rss_rlim: 18446744073709551615
CPU usage: start_time: 1283454987 rtime: 67 utime: 44 stime: 23 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.31.90/libexec/evolution/2.32/evolution-alarm-notify'

[Thread debugging using libthread_db enabled]
[New Thread 0xb5bf2b90 (LWP 10848)]
0xb5ffb171 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb5c5ea30 (LWP 10789))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    at gspawn.c line 385
  • #2 g_spawn_command_line_sync
    at gspawn.c line 699
  • #3 run_bug_buddy
    at gnome-segvhanlder.c line 240
  • #4 bugbuddy_segv_handle
    at gnome-segvhanlder.c line 191
  • #5 <signal handler called>
  • #6 display_notification
    at alarm-queue.c line 1539
  • #7 procedure_notification
    at alarm-queue.c line 1819
  • #8 alarm_trigger_cb
    at alarm-queue.c line 446
  • #9 alarm_ready_cb
    at alarm.c line 110
  • #10 g_timeout_dispatch
    at gmain.c line 3555
  • #11 g_main_dispatch
    at gmain.c line 2119
  • #12 g_main_context_dispatch
    at gmain.c line 2672
  • #13 g_main_context_iterate
    at gmain.c line 2750
  • #14 g_main_loop_run
    at gmain.c line 2958
  • #15 IA__gtk_main
    at gtkmain.c line 1237
  • #16 main
    at notify-main.c line 86

	Inferior 1 [process 10789] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Comment 1 Matthew Barnes 2010-09-02 20:12:52 UTC
Looks like a missing NULL pointer check.  This might help:

http://git.gnome.org/browse/evolution/commit/?id=8fc31dfe753b3fe5b5d5e0c1914ff64aec710086

Can you retest?
Comment 2 Milan Crha 2010-09-08 08:21:07 UTC
*** Bug 600490 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2010-10-22 04:02:50 UTC
David, did you get similar crash after the fix got committed as mentioned in comment#1 ?
Comment 4 Fabio Durán Verdugo 2010-11-14 03:41:41 UTC
any news?
Comment 5 Akhil Laddha 2010-12-23 05:38:23 UTC
Please feel free to reopen the bug if the problem still occurs with a newer
version of Evolution 2.32.1 or later, thanks.