GNOME Bugzilla – Bug 466808
crash in Evolution: searching the calendar
Last modified: 2007-08-19 16:27:26 UTC
What were you doing when the application crashed? searching the calendar Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.2 2007-08-13 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r2 #1 SMP Tue Aug 14 13:16:09 CDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 229830656 vsize: 229830656 resident: 9236480 share: 6651904 rss: 9236480 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187136548 rtime: 20 utime: 15 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-data-server-1.10' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47500340512160 (LWP 2552)] [New Thread 1090791744 (LWP 2582)] [New Thread 1074006336 (LWP 2553)] 0x00002b3388ab4f9f in waitpid () from /lib/libc.so.6
+ Trace 155274
Thread 1 (Thread 47500340512160 (LWP 2552))
----------- .xsession-errors --------------------- ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 calendar-gui-Message: Check if default client matches (1184886304.16327.9@modeler 1184886304.16327.9@modeler) ** (gnome-cups-icon:824): WARNING **: IPP request failed with status 1030 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 453029 ***