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 322624 - crash in alarm_trigger_cb at alarm-queue.c:417
crash in alarm_trigger_cb at alarm-queue.c:417
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other other
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 381184 387862 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-11-28 09:04 UTC by Joachim Reichelt
Modified: 2007-08-02 11:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
proposed evo patch (2.78 KB, patch)
2007-07-30 10:15 UTC, Milan Crha
committed Details | Review

Description Joachim Reichelt 2005-11-28 09:04:43 UTC
Distribution: SuSE Linux 9.3 (i586)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: SUSE
Synopsis: Alarm notify crashes on start
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from
'/opt/gnome/libexec/evolution-alarm-notify'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1094644352 (LWP 8459)]
[New Thread 1118870448 (LWP 8463)]
[Thread debugging using libthread_db enabled]
[New Thread 1094644352 (LWP 8459)]
[New Thread 1118870448 (LWP 8463)]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1094644352 (LWP 8459)]
[New Thread 1118870448 (LWP 8463)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in ?? ()

Thread 1 (Thread 1094644352 (LWP 8459))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 gnome_init_with_popt_table
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 raise
    from /lib/tls/libc.so.6
  • #12 abort
    from /lib/tls/libc.so.6
  • #13 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #14 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #15 g_assert_warning
    from /opt/gnome/lib/libglib-2.0.so.0
  • #16 alarm_queue_init
  • #17 alarm_add
  • #18 g_source_get_current_time
    from /opt/gnome/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #20 g_main_context_acquire
    from /opt/gnome/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #22 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #23 main
  • #0 ??




------- Bug moved to this database by unknown@gnome.bugs 2005-11-28 09:04 UTC -------

Comment 1 Poornima 2005-11-28 11:34:07 UTC
This bug is fixed in evolution 2.4.x.
Comment 2 André Klapper 2006-12-01 16:19:31 UTC
what a crappy last comment.
Comment 3 ebbywiselyn 2006-12-08 06:09:24 UTC
*** Bug 381184 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-01-07 16:39:54 UTC
*** Bug 387862 has been marked as a duplicate of this bug. ***
Comment 5 Sebastien Bacher 2007-02-22 21:03:08 UTC
There is duplicate with evolution 2.8.x, reopening
Comment 6 Sebastien Bacher 2007-02-28 21:02:44 UTC
Debug backtrace on the Ubuntu bug:
http://librarian.launchpad.net/6568373/evolution-alarm-notify-bugreport.txt

"Memory status: size: 91840512 vsize: 0 resident: 91840512 share: 0 rss: 16543744 rss_rlim: 0
CPU usage: start_time: 1172597199 rtime: 0 utime: 36 stime: 0 cutime:34 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232836944 (LWP 4963)]
[New Thread -1244267616 (LWP 5025)]
[New Thread -1235608672 (LWP 4977)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232836944 (LWP 4963))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
    at gmessages.c line 552
  • #10 alarm_trigger_cb
    at alarm-queue.c line 417
  • #11 alarm_ready_cb
    at alarm.c line 98
  • #12 g_timeout_dispatch
    at gmain.c line 3422
  • #13 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #14 g_main_context_iterate
    at gmain.c line 2677
  • #15 IA__g_main_loop_run
    at gmain.c line 2881
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
    at notify-main.c line 162
  • #0 __kernel_vsy"

Comment 7 Milan Crha 2007-07-30 10:15:14 UTC
Created attachment 92689 [details] [review]
proposed evo patch

for evolution;

just test before adding an alarm if we know the notification method, and if not, print a debug message and skip this alarm, instead of crashing when it comes on time. Maybe some imported alarms could have unknown notification types for Evolution.
Comment 8 Srinivasa Ragavan 2007-08-02 10:07:51 UTC
Commit to head
Comment 9 Milan Crha 2007-08-02 11:15:22 UTC
Committed to trunk. Committed revision 33927.