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 513121 - crash in Evolution: evo running in backgroun...
crash in Evolution: evo running in backgroun...
Status: RESOLVED DUPLICATE of bug 437835
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-30 13:22 UTC by Reid Thompson
Modified: 2008-01-31 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Reid Thompson 2008-01-30 13:22:21 UTC 
What were you doing when the application crashed?
evo running in background


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.3 2008-01-17 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-gentoo-r6 #2 SMP PREEMPT Tue Jan 29 07:46:57 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: marble-look
Icon Theme: gnome

Memory status: size: 85454848 vsize: 85454848 resident: 28966912 share: 9564160 rss: 28966912 rss_rlim: 4294967295
CPU usage: start_time: 1201697163 rtime: 412 utime: 368 stime: 44 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb63496c0 (LWP 31378)]
[New Thread 0xb60a0b90 (LWP 31383)]
0xb7fb6410 in __kernel_vsyscall ()

+ Trace 187387

Thread 1 (Thread 0xb63496c0 (LWP 31378))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 soup_connection_disconnect
    at soup-connection.c line 618
  • #10 socket_disconnected
    at soup-connection.c line 348
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 490
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #15 IA__g_signal_emit
    at gsignal.c line 2243
  • #16 soup_socket_disconnect
    at soup-socket.c line 919
  • #17 socket_read_watch
    at soup-socket.c line 1013
  • #18 g_io_unix_dispatch
    at giounix.c line 162
  • #19 g_main_dispatch
    at gmain.c line 2064
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2616
  • #21 g_main_context_iterate
    at gmain.c line 2697
  • #22 IA__g_main_loop_run
    at gmain.c line 2905
  • #23 bonobo_main
    at bonobo-main.c line 311
  • #24 main
    at main.c line 238
  • #0 __kernel_vsyscall 


----------- .xsession-errors (56114 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(gnome-terminal:25056): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:25056): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:25056): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:25056): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Comment 1 André Klapper 2008-01-31 22:45:51 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 437835 ***