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 543912 - crash in Evolution Mail and Calendar: Looking at the calendar ...
crash in Evolution Mail and Calendar: Looking at the calendar ...
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-07-20 21:23 UTC by flameeyes
Modified: 2008-07-21 05:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description flameeyes 2008-07-20 21:23:55 UTC 
What were you doing when the application crashed?
Looking at the calendar with a Google Calendar enabled.


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.3 2008-07-19 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-gentoo #5 PREEMPT Sat Jul 19 20:19:32 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 482332672 vsize: 482332672 resident: 39231488 share: 20426752 rss: 39231488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1216588897 rtime: 224 utime: 201 stime: 23 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

0x00007f6d306ffc6f in waitpid () from /lib/libpthread.so.0

+ Trace 203358

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #3 check_if_gdb
    at gnome-breakpad.cc line 213
  • #4 bugbuddy_segv_handle
    at gnome-breakpad.cc line 87
  • #5 <signal handler called>
  • #6 e_calendar_view_get_tooltips
    at e-calendar-view.c line 2256
  • #7 g_timeout_dispatch
    at gmain.c line 3446
  • #8 IA__g_main_context_dispatch
    at gmain.c line 2012
  • #9 g_main_context_iterate
    at gmain.c line 2645
  • #10 IA__g_main_loop_run
    at gmain.c line 2853
  • #11 bonobo_main
    at bonobo-main.c line 311
  • #12 main
    at main.c line 793 


----------- .xsession-errors (256 sec old) ---------------------
/home/flame/.config/qtcurve.gtk-icons:616: Unable to locate image file in pixmap_path: "32x32/actions/redo.png"
/home/flame/.config/qtcurve.gtk-icons:617: Unable to locate image file in pixmap_path: "16x16/actions/redo.png"
/home/flame/.config/qtcurve.gtk-icons:620: Unable to locate image file in pixmap_path: "16x16/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:621: Unable to locate image file in pixmap_path: "22x22/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:622: Unable to locate image file in pixmap_path: "32x32/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:623: Unable to locate image file in pixmap_path: "16x16/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:624: Unable to locate image file in pixmap_path: "16x16/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:625: Unable to locate image file in pixmap_path: "32x32/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:626: Unable to locate image file in pixmap_path: "16x16/actions/reload.png"
/home/flame/.config/qtcurve.gtk-icons:629: Unable to locate image file in pixmap_path: "16x16/actions/remove.png"
/home/flame/.config/qtcurve.gtk-icons:630: Unable to locate image file in pixmap_path: "22x22/actions/remove.png"
/home/flame/.config/qtcurve.gtk-icons:631: Unable to locate image file in pixmap_path: "32x32/actions/remove.png"
/home/flame/.config/qtcurve.gtk-icons:632: Unable to locate image file in pixmap_path: "16x16/actions/remove.png"
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-07-21 05:04:03 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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