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 564788 - crash in Evolution Mail and Calendar: Working in the calender.
crash in Evolution Mail and Calendar: Working in the calender.
Status: RESOLVED DUPLICATE of bug 333224
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: 2008-12-16 22:05 UTC by Paul Menzel
Modified: 2009-02-19 18:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Paul Menzel 2008-12-16 22:05:47 UTC 
What were you doing when the application crashed?
Working in the calender.


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

System: Linux 2.6.26-1-amd64 #1 SMP Wed Nov 26 20:45:21 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 261947392 vsize: 261947392 resident: 189526016 share: 23957504 rss: 189526016 rss_rlim: 18446744073709551615
CPU usage: start_time: 1229442430 rtime: 27260 utime: 25168 stime: 2092 cutime:78 cstime: 131 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xf66586d0 (LWP 3956)]
[New Thread 0xf46feb90 (LWP 5252)]
[New Thread 0xeacfeb90 (LWP 4144)]
[New Thread 0xef6f4b90 (LWP 4028)]
0xf7fcf425 in __kernel_vsyscall ()

+ Trace 210865

Thread 1 (Thread 0xf66586d0 (LWP 3956))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/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 <signal handler called>
  • #8 pvl_head
    at pvl.c line 541
  • #9 icalcomponent_get_summary
    at icalcomponent.c line 1758
  • #10 e_calendar_view_get_icalcomponent_summary
    at e-calendar-view.c line 2338
  • #11 e_calendar_view_get_tooltips
    at e-calendar-view.c line 2174
  • #12 g_timeout_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 3446
  • #13 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #14 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #15 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
    at main.c line 793
  • #0 __kernel_vsyscall 


----------- .xsession-errors (22693 sec old) ---------------------
** (gnome-settings-daemon:3800): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
** (gnome-settings-daemon:3800): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
** (gnome-settings-daemon:3800): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
seahorse nautilus module initialized
Initializing gnome-mount extension
** (nautilus:3830): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3830): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3830): WARNING **: Can not get _NET_WORKAREA
** (nautilus:3830): WARNING **: Can not determine workarea, guessing at layout
--------------------------------------------------
Comment 1 Akhil Laddha 2009-01-19 05:28:40 UTC 
may be fixed with bug 333224
Comment 2 Milan Crha 2009-02-19 18:06:13 UTC 
Yup, I believe it is, especially when this one is for 2.22 too.

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