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 568238 - crash in Evolution Mail and Calendar: Open up a new appointmen...
crash in Evolution Mail and Calendar: Open up a new appointmen...
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: 2009-01-18 23:06 UTC by Paul Menzel
Modified: 2009-01-19 05:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Paul Menzel 2009-01-18 23:06:15 UTC 
What were you doing when the application crashed?
Open up a new appointment and hit Ctrl + T in the calendar to get to today/current date.


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 Sat Jan 10 19:55:48 UTC 2009 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: 241676288 vsize: 241676288 resident: 169598976 share: 25235456 rss: 169598976 rss_rlim: 18446744073709551615
CPU usage: start_time: 1232299641 rtime: 27056 utime: 24955 stime: 2101 cutime:20 cstime: 41 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xf656c6d0 (LWP 4094)]
[New Thread 0xefed9b90 (LWP 4837)]
[New Thread 0xf55a3b90 (LWP 4714)]
[New Thread 0xef6d8b90 (LWP 4164)]
0xf7ee4425 in __kernel_vsyscall ()

+ Trace 211652

Thread 1 (Thread 0xf656c6d0 (LWP 4094))

  • #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 e_calendar_view_get_tooltips
    at e-calendar-view.c line 2166
  • #9 g_timeout_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 3446
  • #10 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #11 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #12 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #13 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #14 main
    at main.c line 793
  • #0 __kernel_vsyscall 


----------- .xsession-errors (20294 sec old) ---------------------
** (gnome-settings-daemon:3870): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
** (gnome-settings-daemon:3870): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
** (gnome-settings-daemon:3870): 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:3900): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3900): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3900): WARNING **: Can not get _NET_WORKAREA
** (nautilus:3900): WARNING **: Can not determine workarea, guessing at layout
--------------------------------------------------
Comment 1 Akhil Laddha 2009-01-19 05:25:23 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 333224 ***