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 605512 - git/master SIGSEVS after upgrade of gnome to 2.29.4
git/master SIGSEVS after upgrade of gnome to 2.29.4
Status: RESOLVED NOTGNOME
Product: evolution
Classification: Applications
Component: general
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-12-26 23:43 UTC by David Ronis
Modified: 2013-09-13 01:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2009-12-26 23:43:30 UTC
I upgraded many components of gnome in the last week, including 	

* platform/gtk+: bump version to 2.19.2

With the exception of a docbook configure issue in gtk-doc, everything went smoothly.  I also uninstalled all of evo and friends and rebuilt the git/master.

evolution dies on startup (with lots of libc errors on the console and no UI mapped).   Running in a debugger gives the following backtrace (note that dbus was not upgraded):

Thread 1 (Thread 0xb5770700 (LWP 12921))

  • #0 mempcpy
    from //lib/libc.so.6
  • #1 _IO_default_xsputn_internal
    from //lib/libc.so.6
  • #2 vfprintf
    from //lib/libc.so.6
  • #3 vsprintf
    from //lib/libc.so.6
  • #4 vsnprintf
    at vsnprintf.c line 135
  • #5 _dbus_printf_string_upper_bound
    at dbus-sysdeps-unix.c line 3228
  • #6 _dbus_string_append_printf_valist
    at dbus-string.c line 1255
  • #7 dbus_set_error
    at dbus-errors.c line 384
  • #8 dbus_set_error_from_message
    at dbus-message.c line 3616
  • #9 gkr_operation_handle_errors
    at gkr-operation.c line 379
  • #10 callback_with_message
    at gkr-operation.c line 281
  • #11 on_pending_call_notify
    at gkr-operation.c line 301
  • #12 _dbus_pending_call_complete
    at dbus-pending-call.c line 196
  • #13 complete_pending_call_and_unlock
    at dbus-connection.c line 2233
  • #14 check_for_reply_and_update_dispatch_unlocked
    at dbus-connection.c line 2252
  • #15 _dbus_connection_block_pending_call
    at dbus-connection.c line 2362
  • #16 dbus_pending_call_block
    at dbus-pending-call.c line 705
  • #17 gkr_operation_block
    at gkr-operation.c line 341
  • #18 gnome_keyring_is_available
    at gnome-keyring.c line 492
  • #19 e_passwords_init
    at e-passwords.c line 1273
  • #20 main
    at main.c line 552
  • #0 mempcpy
    from //lib/libc.so.6
  • #1 _IO_default_xsputn_internal
    from //lib/libc.so.6
  • #2 vfprintf
    from //lib/libc.so.6
  • #3 vsprintf
    from //lib/libc.so.6
  • #4 vsnprintf
    at vsnprintf.c line 135
  • #5 _dbus_printf_string_upper_bound
    at dbus-sysdeps-unix.c line 3228
  • #6 _dbus_string_append_printf_valist
    at dbus-string.c line 1255
  • #7 dbus_set_error
    at dbus-errors.c line 384
  • #8 dbus_set_error_from_message
    at dbus-message.c line 3616
  • #9 gkr_operation_handle_errors
    at gkr-operation.c line 379
  • #10 callback_with_message
    at gkr-operation.c line 281
  • #11 on_pending_call_notify
    at gkr-operation.c line 301
  • #12 _dbus_pending_call_complete
    at dbus-pending-call.c line 196
  • #13 complete_pending_call_and_unlock
    at dbus-connection.c line 2233
  • #14 check_for_reply_and_update_dispatch_unlocked
    at dbus-connection.c line 2252
  • #15 _dbus_connection_block_pending_call
    at dbus-connection.c line 2362
  • #16 dbus_pending_call_block
    at dbus-pending-call.c line 705
  • #17 gkr_operation_block
    at gkr-operation.c line 341
  • #18 gnome_keyring_is_available
    at gnome-keyring.c line 492
  • #19 e_passwords_init
    at e-passwords.c line 1273
  • #20 main
    at main.c line 552
  • #0 mempcpy
    from //lib/libc.so.6

Comment 1 David Ronis 2009-12-27 17:50:40 UTC
I reverted both glib and gtk+ to the last version (2.23.0 and 2.19.1).  The problem doesn't go away.
Comment 2 David Ronis 2009-12-28 04:33:24 UTC
After playing around with reverting the many gnome modules I'd upgraded, it turns out that the culprit seems to be gnome-keyring.  I'd upgraded from version 2.28.2 to 2.29.4.  Reverting the package allows evolution to run again.  

Frankly, I find the keyring a nuisance on my laptop, and would appreciate a configure flag to turn it off.
Comment 3 Matthew Barnes 2009-12-28 13:53:51 UTC
evolution-data-server$ ./configure --disable-gnome-keyring
Comment 4 David Ronis 2009-12-28 17:39:55 UTC
Thanks Matthew.   I'll give it a try.
Comment 5 David Ronis 2010-02-16 17:11:09 UTC
The problem is a broken libical the supplies it's own (broken) vsnprintf.   See bug 605811