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 581471 - crash in Evolution Mail and Calendar:
crash in Evolution Mail and Calendar:
Status: RESOLVED DUPLICATE of bug 523463
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-05 13:36 UTC by 123456
Modified: 2009-05-06 03:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description 123456 2009-05-05 13:36:04 UTC 
What were you doing when the application crashed?



Distribution: Debian 5.0.1
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26 #2 SMP PREEMPT Sun Apr 12 13:00:48 CEST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Murrina-Deviant
Icon Theme: gnome

Memory status: size: 141463552 vsize: 141463552 resident: 42102784 share: 22880256 rss: 42102784 rss_rlim: 4294967295
CPU usage: start_time: 1241530522 rtime: 208 utime: 192 stime: 16 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb65fc6d0 (LWP 3842)]
[New Thread 0xae6feb90 (LWP 3966)]
[New Thread 0xad6fcb90 (LWP 3965)]
[New Thread 0xb1cfdb90 (LWP 3875)]
[New Thread 0xb3e51b90 (LWP 3866)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 215146

Thread 1 (Thread 0xb65fc6d0 (LWP 3842))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 segv_redirect
    at main.c line 519
  • #7 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #8 <signal handler called>
  • #9 IA__g_main_context_check
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2491
  • #10 g_main_context_iterate
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2642
  • #11 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
    at main.c line 793
  • #0 __kernel_vsyscall 


----------- .xsession-errors (25 sec old) ---------------------
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
** (gnome-settings-daemon:3673): WARNING **: Failed to acquire org.gnome.SettingsDaemon
** (gnome-settings-daemon:3673): WARNING **: Could not acquire name
seahorse nautilus module initialized
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
** Message: failed to load session from /home/gui/.nautilus/saved-session-YTNDDU
Impossible d'ouvrir le fichier de bureau /home/gui/Desktop/zend-zendstudioeclipse.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
** Message: Failed to load /home/gui/.local/share/icons/hicolor/32x32/mimetypes/application-vnd.oasis.opendocument.text.png into memory: Failed to open file '/home/gui/.local/share/icons/hicolor/32x32
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
36
--------------------------------------------------
Comment 1 Akhil Laddha 2009-05-06 03:17:46 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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