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 404709 - crash in Evolution: Trying to add an appoint...
crash in Evolution: Trying to add an appoint...
Status: RESOLVED DUPLICATE of bug 342634
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-02-05 19:04 UTC by craigs
Modified: 2007-02-18 12:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description craigs 2007-02-05 19:04:04 UTC 
What were you doing when the application crashed?
Trying to add an appointment without a specific time


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 313098240 vsize: 313098240 resident: 36139008 share: 20766720 rss: 36139008 rss_rlim: -1
CPU usage: start_time: 1170701846 rtime: 752 utime: 706 stime: 46 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46914399776112 (LWP 5910)]
[New Thread 1132489040 (LWP 6005)]
[New Thread 1141147984 (LWP 5947)]
[New Thread 1115703632 (LWP 5928)]
[New Thread 1107310928 (LWP 5927)]
[New Thread 1098918224 (LWP 5922)]
[New Thread 1090525520 (LWP 5921)]
[New Thread 1082132816 (LWP 5917)]
(no debugging symbols found)
0x00002aab17d635cf in waitpid () from /lib/libc.so.6

+ Trace 108250

Thread 8 (Thread 1082132816 (LWP 5917))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 7 (Thread 1090525520 (LWP 5921))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 6 (Thread 1098918224 (LWP 5922))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 5 (Thread 1107310928 (LWP 5927))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 4 (Thread 1115703632 (LWP 5928))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ?? 






Comment 1


palfrey





          2007-02-06 17:40:47 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


craigs





          2007-02-16 00:47:56 UTC
        



Finally got this to crash again.  Again I was adding an appointment.  I entered the info into the bar space on the calendar, hit return and then immediately tried to edit the same appointment.  Here are the additional stac traces (I hope); if you need more I'll try to help.

Craig

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 370180096 vsize: 370180096 resident: 53760000 share: 24584192 rss: 53760000 rss_rlim: -1
CPU usage: start_time: 1171582249 rtime: 2035 utime: 1907 stime: 128 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47589714681200 (LWP 10412)]
[New Thread 1107310928 (LWP 10901)]
[New Thread 1141147984 (LWP 10485)]
[New Thread 1132489040 (LWP 10483)]
[New Thread 1115703632 (LWP 10481)]
[New Thread 1098918224 (LWP 10425)]
[New Thread 1090525520 (LWP 10424)]
[New Thread 1082132816 (LWP 10420)]
0x00002b4853bde5cf in waitpid () from /lib/libc.so.6




+
Trace
    111140






Thread 8
          (Thread 1082132816 (LWP 10420))


    

  • 
#0
select

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
e_msgport_wait

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#2
e_msgport_reply

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#3
start_thread

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
??

    • 



Thread 7
          (Thread 1090525520 (LWP 10424))


    

  • 
#0
select

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
e_msgport_wait

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#2
e_msgport_reply

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#3
start_thread

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
??

    • 



Thread 6
          (Thread 1098918224 (LWP 10425))


    

  • 
#0
select

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
e_msgport_wait

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#2
e_msgport_reply

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#3
start_thread

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
??

    • 



Thread 5
          (Thread 1115703632 (LWP 10481))


    

  • 
#0
select

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
e_msgport_wait

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#2
e_msgport_reply

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#3
start_thread

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
??

    • 



Thread 4
          (Thread 1132489040 (LWP 10483))


    

  • 
#0
select

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
e_msgport_wait

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#2
e_msgport_reply

    
                from
                /usr/lib64/libedataserver-1.2.so.7

    

    • 

  • 
#3
start_thread

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
??

    • 













Comment 3


palfrey





          2007-02-16 01:07:40 UTC
        



Unfortunately, that's a bit better, but still not vastly useful. If you see a stacktrace from Bug Buddy with no "<signal handler called>" and lots of "killpg"'s followed by "??" items, then it means that Bug Buddy has got a bit confused...

One way around this if you've got a repeatable way to trigger the bug is to get a trace from gdb directly. There's a guide at http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running that says how to do this. Should help us resolve this one properly. Thanks!






Comment 4


craigs





          2007-02-18 07:59:57 UTC
        



Ok.  I can repeatedly crash the program by entering something in the appointment space and then, before hitting return, right click on it.  Here is the gdb stack trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47928729247088 (LWP 5536)]
e_cal_popup_target_new_select (eabp=<value optimized out>, model=0x10cdb30, events=0x12b31b0) at e-cal-popup.c:572
572     e-cal-popup.c: No such file or directory.
        in e-cal-popup.c
(gdb) thread apply all bt





+
Trace
    111698






Thread 1
          (Thread 47928729247088 (LWP 5536))


    

  • 
#0
e_cal_popup_target_new_select

    
                at e-cal-popup.c
                  line
                  572

    

    • 

  • 
#1
e_calendar_view_create_popup_menu

    
                at e-calendar-view.c
                  line
                  1771

    

    • 

  • 
#2
e_day_view_show_popup_menu

    
                at e-day-view.c
                  line
                  4081

    

    • 

  • 
#3
e_day_view_on_main_canvas_button_press

    
                at e-day-view.c
                  line
                  3678

    

    • 

  • 
#4
_gtk_marshal_BOOLEAN__BOXED

    
                from
                /usr/lib64/libgtk-x11-2.0.so.0

    

    • 

  • 
#5
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#6
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2440

    

    • 

  • 
#7
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2209

    

    • 

  • 
#8
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#9
gtk_widget_get_default_style

    
                from
                /usr/lib64/libgtk-x11-2.0.so.0

    

    • 

  • 
#10
gtk_propagate_event

    
                from
                /usr/lib64/libgtk-x11-2.0.so.0

    

    • 

  • 
#11
gtk_main_do_event

    
                from
                /usr/lib64/libgtk-x11-2.0.so.0

    

    • 

  • 
#12
_gdk_events_init

    
                from
                /usr/lib64/libgdk-x11-2.0.so.0

    

    • 

  • 
#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/lib64/libbonobo-2.so.0

    

    • 

  • 
#17
??

    • 













Comment 5


palfrey





          2007-02-18 12:04:37 UTC
        



Ok, looks like it's a duplicate of Bug 342634 which has been resolved. Thanks for your help!

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