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 594590 - crash in Evolution Mail and Calendar: Mails angeschaut
crash in Evolution Mail and Calendar: Mails angeschaut
Status: RESOLVED DUPLICATE of bug 557613
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-09-09 05:05 UTC by information.geo
Modified: 2009-09-09 08:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description information.geo 2009-09-09 05:05:44 UTC 
What were you doing when the application crashed?
Mails angeschaut


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 263340032 vsize: 263340032 resident: 89341952 share: 15601664 rss: 89341952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1252471407 rtime: 58390 utime: 52088 stime: 6302 cutime:4 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb25ffb90 (LWP 8512)]
[New Thread 0xb4904b90 (LWP 8377)]
[New Thread 0xb08fcb90 (LWP 6927)]
[New Thread 0xb3f4fb90 (LWP 5382)]
[New Thread 0xb3902b90 (LWP 5381)]
[New Thread 0xaae92b90 (LWP 5216)]
[New Thread 0xac813b90 (LWP 5183)]
[New Thread 0xad014b90 (LWP 5182)]
[New Thread 0xaf5a4b90 (LWP 5174)]
[New Thread 0xb10fdb90 (LWP 5170)]
[New Thread 0xb5197b90 (LWP 5162)]
[New Thread 0xb5998b90 (LWP 5160)]
0xb8041424 in __kernel_vsyscall ()

+ Trace 217438

Thread 1 (Thread 0xb6416760 (LWP 5156))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 segv_redirect
    at main.c line 426
  • #6 <signal handler called>
  • #7 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #8 e_flag_set
    from /usr/lib/libedataserver-1.2.so.11
  • #9 try_open_e_book_cb
    at em-utils.c line 2006
  • #10 ??
    from /usr/lib/libebook-1.2.so.9
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 704 


----------- .xsession-errors (13 sec old) ---------------------
(evolution:5156): Gdk-WARNING **: GdkWindow is too large to allow the use of shape masks or shape regions.
(evolution:5156): Gdk-WARNING **: GdkWindow is too large to allow the use of shape masks or shape regions.
(evolution:5156): Gdk-WARNING **: GdkWindow is too large to allow the use of shape masks or shape regions.
** (gnome-panel:3619): WARNING **: Could not connect to session manager: Could not get owner of name 'org.gnome.SessionManager': no such name
warning: .dynamic section for "/usr/lib/libdirectfb-1.2.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libfusion-1.2.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libdirect-1.2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Akhil Laddha 2009-09-09 08:10:30 UTC 

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