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 513532 - crash in Evolution: evo running in backgroun...
crash in Evolution: evo running in backgroun...
Status: RESOLVED DUPLICATE of bug 489501
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-31 21:10 UTC by Reid Thompson
Modified: 2008-01-31 22:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Reid Thompson 2008-01-31 21:10:31 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: 79900672 vsize: 79900672 resident: 23080960 share: 9539584 rss: 23080960 rss_rlim: 4294967295
CPU usage: start_time: 1201812350 rtime: 354 utime: 307 stime: 47 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 0xb62f56c0 (LWP 31696)]
[New Thread 0xb604cb90 (LWP 31700)]
0xb7f62410 in __kernel_vsyscall ()

+ Trace 187650

Thread 1 (Thread 0xb62f56c0 (LWP 31696))

  • #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 strchr
    from /lib/libc.so.6
  • #10 soup_uri_new_with_base
    at soup-uri.c line 142
  • #11 soup_uri_new
    at soup-uri.c line 378
  • #12 soup_message_new
    at soup-message.c line 492
  • #13 e2k_soup_message_new
    at e2k-context.c line 755
  • #14 e2k_soup_message_new_full
    at e2k-context.c line 786
  • #15 patch_msg
    at e2k-context.c line 1367
  • #16 e2k_context_proppatch
    at e2k-context.c line 1407
  • #17 set_replied_flags
    at mail-stub-exchange.c line 1730
  • #18 process_flags
    at mail-stub-exchange.c line 1854
  • #19 g_timeout_dispatch
    at gmain.c line 3498
  • #20 g_main_dispatch
    at gmain.c line 2064
  • #21 IA__g_main_context_dispatch
    at gmain.c line 2616
  • #22 g_main_context_iterate
    at gmain.c line 2697
  • #23 IA__g_main_loop_run
    at gmain.c line 2905
  • #24 bonobo_main
    at bonobo-main.c line 311
  • #25 main
    at main.c line 238
  • #0 __kernel_vsyscall 


----------- .xsession-errors (135 sec old) ---------------------
	192.168.1.0/255.255.255.0
env is null
	161.170.0.0/255.255.0.0
env is null
	161.173.0.0/255.255.0.0
env is null
NetExtender IP Address: 192.168.1.23
env is null
NetExtender connected successfully. Type "Ctrl-c" to disconnect...
env is null
Saving profiles...
Opening /home/rthompso/.netextender
closing
Done.
/opt/vmware/server/console/lib/bin/vmware-server-console: /opt/vmware/server/console/lib/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
--------------------------------------------------
Comment 1 André Klapper 2008-01-31 22:54:01 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 489501 ***