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 359025 - crash in Evolution: updating the end time of...
crash in Evolution: updating the end time of...
Status: RESOLVED DUPLICATE of bug 329356
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-02 15:27 UTC by mve
Modified: 2006-10-11 07:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mve 2006-10-02 15:27:18 UTC 
What were you doing when the application crashed?
updating the end time of a meeting sent from Lotus Notes


Distribution: Debian testing/unstable
Gnome Release: 2.15.91 2006-08-13 (Debian)
BugBuddy Version: 2.16.0

Memory status: size: 233717760 vsize: 0 resident: 233717760 share: 0 rss: 88629248 rss_rlim: 0
CPU usage: start_time: 1159507830 rtime: 0 utime: 39125 stime: 0 cutime:36619 cstime: 0 timeout: 2506 it_real_value: 0 frequency: 518

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233102624 (LWP 6451)]
[New Thread -1409107024 (LWP 29430)]
[New Thread -1324733520 (LWP 22200)]
[New Thread -1335886928 (LWP 20588)]
[New Thread -1324471376 (LWP 6896)]
[New Thread -1287504976 (LWP 6526)]
[New Thread -1314128976 (LWP 6480)]
[New Thread -1270727760 (LWP 6478)]
[New Thread -1262302288 (LWP 6473)]
[New Thread -1253913680 (LWP 6472)]
[New Thread -1245398096 (LWP 6465)]
[New Thread -1237009488 (LWP 6464)]
(no debugging symbols found)
0xb772a201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 74088

Thread 1 (Thread -1233102624 (LWP 6451))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/tls/libc.so.6
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 gtk_text_view_new_with_buffer
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_text_unknown_char_utf8
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
  • #12 gtk_text_unknown_char_utf8
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_text_unknown_char_utf8
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 






Comment 1


Karsten Bräckelmann





          2006-10-02 17:44:05 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Can you reproduce this issue?







Comment 2


mve





          2006-10-02 18:04:35 UTC
        



it's completely reproducible.

I installed the debug packages of evolution (as well as a bunch of dependencies
like the ones for e-d-s, gtk+ and glib). Does the new trace help ?

Distribution: Debian testing/unstable
Gnome Release: 2.15.91 2006-08-13 (Debian)
BugBuddy Version: 2.16.0

Memory status: size: 180252672 vsize: 0 resident: 180252672 share: 0 rss: 49623040 rss_rlim: 0
CPU usage: start_time: 1159804327 rtime: 0 utime: 2431 stime: 0 cutime:2300 cstime: 0 timeout: 131 it_real_value: 0 frequency: 39

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233590048 (LWP 32027)]
[New Thread -1357513808 (LWP 32236)]
[New Thread -1279603792 (LWP 32136)]
[New Thread -1315570768 (LWP 32128)]
[New Thread -1365902416 (LWP 32068)]
[New Thread -1298531408 (LWP 32045)]
[New Thread -1287992400 (LWP 32044)]
[New Thread -1262789712 (LWP 32034)]
[New Thread -1254401104 (LWP 32033)]
[New Thread -1245885520 (LWP 32032)]
[New Thread -1237496912 (LWP 32031)]
0xb76b0201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0




+
Trace
    74112






Thread 1
          (Thread -1233590048 (LWP 32027))


    

  • 
#0
__waitpid_nocancel

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#1
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  870

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
raise

    
                from
                /lib/tls/libc.so.6

    

    • 

  • 
#4
abort

    
                from
                /lib/tls/libc.so.6

    

    • 

  • 
#5
IA__g_logv

    • 

  • 
#6
IA__g_log

    • 

  • 
#7
IA__g_assert_warning

    
                at gmessages.c
                  line
                  552

    

    • 

  • 
#8
gtk_text_view_start_selection_drag

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtktextview.c
                  line
                  5665

    

    • 

  • 
#9
gtk_text_view_button_press_event

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtktextview.c
                  line
                  3987

    

    • 

  • 
#10
_gtk_marshal_BOOLEAN__BOXED

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtkmarshalers.c
                  line
                  84

    

    • 

  • 
#11
g_type_class_meta_marshal

    
                at gclosure.c
                  line
                  567

    

    • 

  • 
#12
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#13
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2476

    

    • 

  • 
#14
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2207

    

    • 

  • 
#15
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2241

    

    • 

  • 
#16
gtk_widget_event_internal

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtkwidget.c
                  line
                  3911

    

    • 

  • 
#17
IA__gtk_propagate_event

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtkmain.c
                  line
                  2188

    

    • 

  • 
#18
IA__gtk_main_do_event

    
                at /tmp/buildd/gtk+2.0-2.10.4/gtk/gtkmain.c
                  line
                  1422

    

    • 

  • 
#19
gdk_event_dispatch

    
                at /tmp/buildd/gtk+2.0-2.10.4/gdk/x11/gdkevents-x11.c
                  line
                  2320

    

    • 

  • 
#20
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#21
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#22
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#23
bonobo_main

    
                from
                /usr/lib/libbonobo-2.so.0

    

    • 

  • 
#24
main

    
                at main.c
                  line
                  615

    

    • 

  • 
#0
__waitpid_nocancel

    
                from
                /lib/tls/libpthread.so.0

    

    • 













Comment 3


Karsten Bräckelmann





          2006-10-10 20:42:57 UTC
        



Thanks for the good stacktrace. :)

Actually this one looks like a duplicate of bug 329356, which is supposed to be fixed already. GAR.


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






Comment 4


Karsten Bräckelmann





          2006-10-10 20:48:44 UTC
        



Added you to the Cc list of the other bug, so you'll be kept in the loop.







Comment 5


mve





          2006-10-10 21:24:18 UTC
        



good idea indeed. The new emails triggered me to try to crash evolution again, and the new version in Debian (2.8.1-1) doesn't crash anymore.
Whether this is related to an upstream fix or a debian-only patch is left as an exercise for you guys (the patch is at http://ftp.debian.org/debian/pool/main/e/evolution/evolution_2.8.1-1.diff.gz but doesn't seem to contain any calendar-related fixes, so kudos to upstream hackers !)






Comment 6


Karsten Bräckelmann





          2006-10-11 00:59:07 UTC
        



M, please note that the patch that is supposed to fix this actually is against e-d-s, not evolution. Can you tell us, which exact versions of Evolution as well as evolution-data-server are installed now -- and before that recent update?







Comment 7


mve





          2006-10-11 07:39:32 UTC
        



from aptitude.log:
[UPGRADE] evolution 2.8.0-2 -> 2.8.1-1
[UPGRADE] evolution-data-server 1.8.0-3 -> 1.8.1-1

(as you know, Debian splits the resulting binaries in multiple packages,
so this is a summary. I also updated all the 'subpackages')