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 558281 - crash in Evolution Mail and Calendar: Just opened evo
crash in Evolution Mail and Calendar: Just opened evo
Status: RESOLVED DUPLICATE of bug 557613
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-28 18:59 UTC by frankly3d
Modified: 2008-11-19 16:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description frankly3d 2008-10-28 18:59:52 UTC 
What were you doing when the application crashed?
Just opened evo


Distribution: Fedora release 9.92 (Rawhide)
Gnome Release: 2.24.1 2008-10-27 (Red Hat, Inc)
BugBuddy Version: 2.24.1

System: Linux 2.6.27.4-58.fc10.i686 #1 SMP Mon Oct 27 18:21:44 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 139710464 vsize: 139710464 resident: 31391744 share: 20500480 rss: 31391744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225220315 rtime: 208 utime: 190 stime: 18 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 0xb7ff0980 (LWP 4366)]
[New Thread 0xb2843b90 (LWP 4388)]
[New Thread 0xb3244b90 (LWP 4387)]
[New Thread 0xb4ad5b90 (LWP 4386)]
[New Thread 0xb54d6b90 (LWP 4380)]
[New Thread 0xb3e49b90 (LWP 4378)]
[New Thread 0xb70ffb90 (LWP 4372)]
0x00110416 in __kernel_vsyscall ()

+ Trace 208837

Thread 1 (Thread 0xb7ff0980 (LWP 4366))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 segv_redirect
    at main.c line 414
  • #8 <signal handler called>
  • #9 __pthread_mutex_lock
    at pthread_mutex_lock.c line 51
  • #10 e_flag_set
    at e-flag.c line 83
  • #11 try_open_e_book_cb
    at em-utils.c line 2048
  • #12 emit_async_open_response
    at e-book.c line 2762
  • #13 g_idle_dispatch
    at gmain.c line 4235
  • #14 g_main_dispatch
    at gmain.c line 2144
  • #15 IA__g_main_context_dispatch
    at gmain.c line 2697
  • #16 g_main_context_iterate
    at gmain.c line 2778
  • #17 IA__g_main_loop_run
    at gmain.c line 2986
  • #18 bonobo_main
    at bonobo-main.c line 311
  • #19 main
    at main.c line 689 


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/libnm-util.so.0.0.0.debug" does not match "/usr/lib/libnm-util.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libnm-util.so.0.0.0.debug" does not match "/usr/lib/libnm-util.so.0" (CRC mismatch).
Could not find the frame base for "start_thread".
Could not find the frame base for "camel_folder_sync".
Could not find the frame base for "start_thread".
Could not find the frame base for "_pr_poll_with_poll".
Could not find the frame base for "start_thread".
Could not find the frame base for "startup_mainloop".
Could not find the frame base for "start_thread".
Could not find the frame base for "link_io_thread_fn".
Could not find the frame base for "start_thread".
--------------------------------------------------
Comment 1 Milan Crha 2008-11-19 16:07:04 UTC 
We have similar downstream bug for this too.
https://bugzilla.redhat.com/show_bug.cgi?id=471956
Other circumstances, same issue, seems to me.
Comment 2 Milan Crha 2008-11-19 16:20:25 UTC 
This seems to be fixed in trunk and gnome-2-24 already, see bug #557613 comment #16. Please wait for the update of evolution package, where the fix will be included.

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