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 400988 - evolution alarm notify crash
evolution alarm notify crash
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 358690 556486 561240 566130 576244 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-26 12:52 UTC by bugreports
Modified: 2009-11-22 17:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description bugreports 2007-01-26 12:52:47 UTC 
Steps to reproduce:
I was resuming the machine from s2ram then suddenly that applet crashed.

Stack trace:
Memory status: size: 71303168 vsize: 0 resident: 71303168 share: 0 rss: 8871936 rss_rlim: 0
CPU usage: start_time: 1169789040 rtime: 0 utime: 14 stime: 0 cutime:11 cstime: 0 timeout: 3 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 -1233233504 (LWP 32336)]
[New Thread -1262490704 (LWP 32363)]
[New Thread -1235670096 (LWP 32337)]
0xb7f6c410 in __kernel_vsyscall ()

+ Trace 105409

Thread 1 (Thread -1233233504 (LWP 32336))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 alarm_trigger_cb
    at alarm-queue.c line 1611
  • #5 alarm_ready_cb
    at alarm.c line 98
  • #6 g_timeout_dispatch
    at gmain.c line 3422
  • #7 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #8 g_main_context_iterate
    at gmain.c line 2677
  • #9 IA__g_main_loop_run
    at gmain.c line 2881
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main
    at notify-main.c line 162
  • #0 __kernel_vsyscall 

Other information:
Comment 1 Juan J. Martinez 2007-02-27 08:32:38 UTC 
Coming back from hibernation too. It happens randomly.

This is Ubuntu 6.10 with Gnome 2.16.1.

Memory status: size: 97148928 vsize: 0 resident: 97148928 share: 0 rss: 17006592 rss_rlim: 0
CPU usage: start_time: 1171618068 rtime: 0 utime: 107 stime: 0 cutime:94 cstime: 0 timeout: 13 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 -1233000784 (LWP 4690)]
[New Thread -1279272032 (LWP 4816)]
[New Thread -1235055712 (LWP 4718)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 114271

Thread 1 (Thread -1233000784 (LWP 4690))

  • #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 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 alarm_ready_cb
    at alarm.c line 75
  • #11 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at notify-main.c line 162
  • #0 __kernel_vsyscall 






Comment 2


Milan Crha





          2007-09-04 14:55:48 UTC
        



I think the stacktrace from comment 1 is fixed in actual trunk, by these changes:
http://svn.gnome.org/viewcvs/evolution/trunk/calendar/gui/alarm-notify/alarm.c?r1=31858&r2=33952
but the first stacktrace seems to crash somewhere else (a bit further).






Comment 3


Sebastien Bacher





          2008-03-26 23:05:36 UTC
        



there is a similar crash on https://bugs.launchpad.net/evolution/+bug/207286 using GNOME 2.22






Comment 4


Milan Crha





          2008-03-27 10:54:35 UTC
        



Hmm, copied relevant portion from launchpad bug:





+
Trace
    193439






Thread 1
          (process 6128)


    

  • 
#0
alarm_trigger_cb

    
                at alarm-queue.c
                  line
                  1666

    

    • 

  • 
#1
alarm_ready_cb

    
                at alarm.c
                  line
                  105

    

    • 

  • 
#2
g_timeout_dispatch

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  3437

    

    • 

  • 
#3
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2003

    

    • 

  • 
#4
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2636

    

    • 

  • 
#5
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2844

    

    • 

  • 
#6
bonobo_main

    
                at bonobo-main.c
                  line
                  311

    

    • 

  • 
#7
main

    
                at notify-main.c
                  line
                  164

    

    • 

  • 
#8
__libc_start_main

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#9
_start

    • 








My line 1666 is this:
if (url && *url && g_file_test (url, G_FILE_TEST_EXISTS)) {

so it doesn't make much sense to crash on this place.

Sebastien, can you ask for an event which causing this? I would like to see it/try to reproduce on my machine, but I want to be sure with the content. If it contains some private data, then let it be discarded, just the alarm setup is important here. Thanks in advance.






Comment 5


Milan Crha





          2008-04-23 14:18:26 UTC
        



Sebastien, ping






Comment 6


Sebastien Bacher





          2008-06-19 13:58:49 UTC
        



ups, forgot to subscribe to the bug, I've commented downstream now






Comment 7


Akhil Laddha





          2008-07-11 11:04:29 UTC
        



*** Bug 358690 has been marked as a duplicate of this bug. ***






Comment 8


Sebastien Bacher





          2008-08-20 13:31:51 UTC
        



the ubuntu submitter doesn't currently has an event to trigger the issue






Comment 9


Akhil Laddha





          2008-10-16 03:19:22 UTC
        



*** Bug 556486 has been marked as a duplicate of this bug. ***






Comment 10


Akhil Laddha





          2008-11-18 04:01:26 UTC
        



*** Bug 561240 has been marked as a duplicate of this bug. ***






Comment 11


André Klapper





          2008-12-31 19:25:22 UTC
        



*** Bug 566130 has been marked as a duplicate of this bug. ***






Comment 12


Fabio Durán Verdugo





          2009-03-22 01:20:59 UTC
        



*** Bug 576244 has been marked as a duplicate of this bug. ***






Comment 13


Tobias Mueller





          2009-11-22 17:31:31 UTC
        



If I remember correctly, this issue has been fixed long time ago. Please reopen if this still happens on a recent evolution.