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 615335 - crash in Evolution: killed gnome-panel as th...
crash in Evolution: killed gnome-panel as th...
Status: RESOLVED DUPLICATE of bug 544110
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.28.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-04-09 22:53 UTC by Johannes Rohr
Modified: 2010-05-03 03:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Johannes Rohr 2010-04-09 22:53:29 UTC
What were you doing when the application crashed?
killed gnome-panel as the clock applet made it hang. 


Distribution: Debian squeeze/sid
Gnome Release: 2.28.2 2009-12-18 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-3-686 #1 SMP Thu Feb 25 06:14:20 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10706000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 73244672 vsize: 73244672 resident: 13639680 share: 11276288 rss: 13639680 rss_rlim: 18446744073709551615
CPU usage: start_time: 1270853529 rtime: 23 utime: 16 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution/2.28/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb4386b70 (LWP 1667)]
[New Thread 0xb4d87b70 (LWP 1666)]
[New Thread 0xb55c9b70 (LWP 1602)]
0xb7817424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb595f760 (LWP 1593))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gspawn.c line 700
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #8 *__GI_abort
    at abort.c line 88
  • #9 IA__g_logv
  • #10 IA__g_log
  • #11 g_mutex_free_posix_impl
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/gthread/gthread-posix.c line 171
  • #12 e_cal_backend_sync_dispose
    at e-cal-backend-sync.c line 1042
  • #13 ??
  • #14 ??
  • #15 IA__g_object_unref
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/gobject/gobject.c line 2453
  • #16 IA__g_value_unset
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/gobject/gvalue.c line 276
  • #17 IA__g_signal_emit_valist
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/gobject/gsignal.c line 3011
  • #18 IA__g_signal_emit
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/gobject/gsignal.c line 3038
  • #19 last_client_gone
    at e-cal-backend.c line 406
  • #20 e_cal_backend_remove_client
    at e-cal-backend.c line 471
  • #21 listener_died_cb
    at e-cal-backend.c line 400
  • #22 ??
    from /usr/lib/libORBit-2.so.0
  • #23 ??
    from /usr/lib/libORBit-2.so.0
  • #24 g_idle_dispatch
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 4065
  • #25 g_main_dispatch
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 1960
  • #26 IA__g_main_context_dispatch
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2513
  • #27 g_main_context_iterate
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2591
  • #28 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2799
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 ??
  • #31 __libc_start_main
    at libc-start.c line 222
  • #32 ??
A debugging session is active.

	Inferior 1 [process 1593] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


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

** GThread **: file /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/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 (1235 sec old) ---------------------
   onNowPlayingReturn: [id: 0 ] "OK" 
"100409 22:31:15" - "-1380979856" - void CPlayerConnection::onScrobbleTimeout() ( 207 ) - L4
   "yaxya" 
"100409 22:31:15" - "-1239763200" - void ScrobbleCache::write() ( 349 ) - L4
   Wrote 1 tracks to "/home/jr/.local/share/Last.fm/yaxya_submissions.xml" 
Exiting thread 
"100409 22:32:36" - "-1252000912" - virtual void ProxyOutput::stopPlayback() ( 57 ) - L4
   Playback stopped 
"100409 22:32:36" - "-1239763200" - void ScrobblerManager::scrobble(TrackInfo) ( 105 ) - L4
   "Keimzeit – Mit dem Regen" 
"100409 22:32:36" - "-1239763200" - void ScrobbleCache::write() ( 349 ) - L4
   Wrote 1 tracks to "/home/jr/.local/share/Last.fm/yaxya_submissions.xml" 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-04-10 01:13:46 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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Johannes Rohr 2010-04-10 06:21:57 UTC
Hi, could you be more specific on what debugging symbols are missing? I have Debian's gnome-dbg package with all its dependencies installed plus libc6-dev and a couple of others. What is missing?
Comment 3 Akhil Laddha 2010-05-03 03:54:40 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 544110 ***