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 598150 - crash in Evolution Mail: exited evolution
crash in Evolution Mail: exited evolution
Status: RESOLVED DUPLICATE of bug 593704
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-12 11:19 UTC by Johannes Rohr
Modified: 2009-10-13 03:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Johannes Rohr 2009-10-12 11:19:45 UTC
What were you doing when the application crashed?
exited evolution


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 294371328 vsize: 294371328 resident: 54296576 share: 16162816 rss: 54296576 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255343626 rtime: 9894 utime: 8878 stime: 1016 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xa5efdb90 (LWP 23608)]
[New Thread 0xaabc7b90 (LWP 20429)]
[New Thread 0xa99ffb90 (LWP 16102)]
[New Thread 0xb36feb90 (LWP 16101)]
[New Thread 0xabcb5b90 (LWP 15933)]
[New Thread 0xac4b6b90 (LWP 15930)]
[New Thread 0xaeafdb90 (LWP 15923)]
[New Thread 0xaf2feb90 (LWP 15922)]
[New Thread 0xafaffb90 (LWP 15921)]
[New Thread 0xb04fdb90 (LWP 15920)]
[New Thread 0xb0cfeb90 (LWP 15919)]
[New Thread 0xb14ffb90 (LWP 15918)]
[New Thread 0xb1efbb90 (LWP 15917)]
[New Thread 0xb2efdb90 (LWP 15915)]
[New Thread 0xb50b7b90 (LWP 15911)]
[New Thread 0xb58b8b90 (LWP 15909)]
0xb7ff3424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb62b1760 (LWP 15891))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 700
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 IA__g_logv
  • #10 IA__g_log
  • #11 g_mutex_free_posix_impl
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gthread/gthread-posix.c line 171
  • #12 e_flag_free
    at e-flag.c line 169
  • #13 e_book_op_free
    at e-book.c line 234
  • #14 e_book_clear_op
    at e-book.c line 259
  • #15 do_cancel
    at e-book.c line 2563
  • #16 e_book_cancel
    at e-book.c line 2608
  • #17 emu_addr_cancel_book
    at em-utils.c line 1981
  • #18 IA__g_hook_list_invoke
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/ghook.c line 299
  • #19 mail_cancel_all
    at mail-mt.c line 457
  • #20 impl_quit
    at mail-component.c line 899
  • #21 _ORBIT_skel_small_GNOME_Evolution_Component_quit
    at Evolution-common.c line 68
  • #22 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #23 GNOME_Evolution_Component_quit
    at Evolution-stubs.c line 111
  • #24 es_run_quit
    at e-shell.c line 1297
  • #25 g_timeout_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 3396
  • #26 g_main_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 1960
  • #27 IA__g_main_context_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2513
  • #28 g_main_context_iterate
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2591
  • #29 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2799
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
    at main.c line 704


---- Critical and fatal warnings logged during execution ----

** GLib-GIO **: g_inet_address_to_string: assertion `G_IS_INET_ADDRESS (address)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** GThread **: file /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Das Gerät oder die Ressource ist belegt' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' 


----------- .xsession-errors (3659 sec old) ---------------------
>> GET CHAT #kathriniwgia/$johannesrohr;205bab01621efad0 RECENTCHATMESSAGES
<< CHAT #kathriniwgia/$johannesrohr;205bab01621efad0 RECENTCHATMESSAGES 1372, 1371, 1370, 1369, 1368, 1367, 1366, 1365, 1364, 1363
>> GET CHATMESSAGE 1372 TIMESTAMP
<< CHATMESSAGE 1372 TIMESTAMP 1254133558
>> GET CHAT #kathriniwgia/$johannesrohr;205bab01621efad0 FRIENDLYNAME
<< CHAT #kathriniwgia/$johannesrohr;205bab01621efad0 FRIENDLYNAME RITC Concept note Climate Change
>> SEARCH GROUPS ALL
<< GROUPS 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55
>> GET GROUP 65 TYPE
<< GROUP 65 TYPE ALL_USERS
>> GET GROUP 64 TYPE
<< GROUP 64 TYPE ALL_FRIENDS
>> GET GROUP 64 USERS 
<< GROUP 64 USERS heikedrillisch, echo123, roxanekauz, raipon.director1, tongtongpiplinks, fhainskin, anjapohlmann, kathriniwgia, ritc.koordinator1, kamchadal2000, rodion_ritc, annagosh, alejandropare
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-10-13 03:31:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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