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 573883 - Evolution crashes on startup
Evolution crashes on startup
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.26.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks:
 
 
Reported: 2009-03-03 09:13 UTC by Mikel Olasagasti
Modified: 2013-09-14 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Mikel Olasagasti 2009-03-03 09:13:31 UTC 
I'm using Ubuntu-9.04 with latest packages and I get evolution crashes on startup.

Don't know if is glib or evolution problem...

GThread-ERROR **: file /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.

+ Trace 213100

Thread 3032480656 (LWP 15531)

  • #0 IA__g_logv
  • #1 IA__g_log
  • #2 g_mutex_free_posix_impl
    at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c line 171
  • #3 ??
    from /usr/lib/libsoup-2.4.so.1
  • #4 IA__g_object_unref
    at /build/buildd/glib2.0-2.19.10/gobject/gobject.c line 2421
  • #5 e_gw_connection_dispose
    at e-gw-connection.c line 310
  • #6 IA__g_object_unref
    at /build/buildd/glib2.0-2.19.10/gobject/gobject.c line 2393
  • #7 e_gw_connection_new_with_error_handler
    at e-gw-connection.c line 558
  • #8 groupwise_connect
    at camel-groupwise-store.c line 212
  • #9 camel_service_connect
    at camel-service.c line 369
  • #10 camel_groupwise_store_connected
    at camel-groupwise-store.c line 1466
  • #11 groupwise_get_folder_info
    at camel-groupwise-store.c line 1173
  • #12 camel_store_get_folder_info
    at camel-store.c line 894
  • #13 get_folderinfo_exec
    at mail-ops.c line 1069
  • #14 mail_msg_proxy
    at mail-mt.c line 520
  • #15 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c line 265
  • #16 g_thread_create_proxy
    at /build/buildd/glib2.0-2.19.10/glib/gthread.c line 635
  • #17 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #18 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


Matthew Barnes





          2009-03-04 00:53:38 UTC
        



Looks GroupWise-related.






Comment 2


Milan Crha





          2009-04-16 10:42:33 UTC
        



Could you add a "t a a bt" result here, please? It'll show whole context of the crash. Based on the error message, the lock left locked while someone wants to free it. It means some code flow on evo side, most likely.






Comment 3


Mikel Olasagasti





          2009-04-16 10:56:48 UTC
        



Sure! Now I'm using latest pkgs at Ubuntu-9.04

(gdb) t a a bt





+
Trace
    214503






Thread 1
          (Thread 0xb61fe770 (LWP 17204))


    

  • 
#0
??

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

    

    • 

  • 
#1
free

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

    

    • 

  • 
#2
cairo_pattern_destroy

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#3
??

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#4
??

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#5
cairo_fill_preserve

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#6
cairo_fill

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#7
gtk_cell_renderer_pixbuf_render

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkcellrendererpixbuf.c
                  line
                  689

    

    • 

  • 
#8
IA__gtk_cell_renderer_render

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkcellrenderer.c
                  line
                  578

    

    • 

  • 
#9
gtk_tree_view_column_cell_process_action

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtktreeviewcolumn.c
                  line
                  2802

    

    • 

  • 
#10
_gtk_tree_view_column_cell_render

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtktreeviewcolumn.c
                  line
                  3135

    

    • 

  • 
#11
gtk_tree_view_bin_expose

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtktreeview.c
                  line
                  4684

    

    • 

  • 
#12
gtk_tree_view_expose

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtktreeview.c
                  line
                  4959

    

    • 

  • 
#13
_gtk_marshal_BOOLEAN__BOXED

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkmarshalers.c
                  line
                  84

    

    • 

  • 
#14
g_type_class_meta_marshal

    
                at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c
                  line
                  878

    

    • 

  • 
#15
IA__g_closure_invoke

    
                at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c
                  line
                  767

    

    • 

  • 
#16
signal_emit_unlocked_R

    
                at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c
                  line
                  3285

    

    • 

  • 
#17
IA__g_signal_emit_valist

    
                at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c
                  line
                  2990

    

    • 

  • 
#18
IA__g_signal_emit

    
                at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c
                  line
                  3037

    

    • 

  • 
#19
gtk_widget_event_internal

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkwidget.c
                  line
                  4761

    

    • 

  • 
#20
IA__gtk_main_do_event

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkmain.c
                  line
                  1558

    

    • 

  • 
#21
gdk_window_process_updates_internal

    
                at /build/buildd/gtk+2.0-2.16.0/gdk/gdkwindow.c
                  line
                  2611

    

    • 

  • 
#22
IA__gdk_window_process_all_updates

    
                at /build/buildd/gtk+2.0-2.16.0/gdk/gdkwindow.c
                  line
                  2677

    

    • 

  • 
#23
gtk_container_idle_sizer

    
                at /build/buildd/gtk+2.0-2.16.0/gtk/gtkcontainer.c
                  line
                  1353

    

    • 

  • 
#24
gdk_threads_dispatch

    
                at /build/buildd/gtk+2.0-2.16.0/gdk/gdk.c
                  line
                  498

    

    • 

  • 
#25
g_idle_dispatch

    
                at /build/buildd/glib2.0-2.20.1/glib/gmain.c
                  line
                  3922

    

    • 

  • 
#26
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.20.1/glib/gmain.c
                  line
                  1814

    

    • 

  • 
#27
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.20.1/glib/gmain.c
                  line
                  2448

    

    • 

  • 
#28
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.20.1/glib/gmain.c
                  line
                  2656

    

    • 

  • 
#29
bonobo_main

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

    

    • 

  • 
#30
main

    
                at main.c
                  line
                  704

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 4


Milan Crha





          2009-04-16 11:27:28 UTC
        



Mike, do you use proxies? Based on source code line numbers, it seems like very similar to bug #574957. Could you try to get the libsoup package with that fix included and test with it please?






Comment 5


Mikel Olasagasti





          2009-04-16 11:41:18 UTC
        



Yes, we do have proxy for the Internet connection, but GW is on the LAN. Anyway, any idea of where I can get fixed libsoup for ubuntu to test?






Comment 6


Milan Crha





          2009-04-16 13:04:59 UTC
        



I asked Sebastien from ubuntu and he said the package is not available yet, but he'll backport the patch soon. I gave him reference to this and one other bug, so hopefully he'll update both when the package will be ready.






Comment 7


Mikel Olasagasti





          2009-05-12 08:23:23 UTC
        



I installed libsoup-2.26.0-0ubuntu3 and evo doesn't crash on startup. Now the problem is that evolution reports "camel-groupwise-provider-WARNING **: Could not connect..failure connecting" and I can get my new mail. Could this one be related? If no, please close and thanks for all!






Comment 8


Mikel Olasagasti





          2009-05-12 08:26:17 UTC
        



s/I can get/I can't get/






Comment 9


Milan Crha





          2009-05-12 08:46:38 UTC
        



It's just that instead of crashing it reports the error "properly". I would suggest you to check you proxy settings, probably those in your system, but check in evolution itself too, though those are not propagated to camel yet.






Comment 10


Mikel Olasagasti





          2009-06-10 13:27:22 UTC
        



I can read mails with latest Ubuntu stable. Closing bug. Thanks all :)