GNOME Bugzilla – Bug 537878
crash in Panel: machine left idle overni...
Last modified: 2008-06-12 06:35:35 UTC
Version: 2.20.3 What were you doing when the application crashed? machine left idle overnight Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.20.3 2008-02-20 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo-r4 #2 PREEMPT Sat Apr 12 13:27:19 BST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Smooth-Tangerine-Dream Icon Theme: nuvola Memory status: size: 115671040 vsize: 115671040 resident: 21225472 share: 13922304 rss: 21225472 rss_rlim: 4294967295 CPU usage: start_time: 1212416460 rtime: 16255 utime: 15635 stime: 620 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal] Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6cd16c0 (LWP 7300)] [New Thread 0xb2839b90 (LWP 11759)] _______________________________________________________________________________ eax:FFFFFE00 ebx:000058C5 ecx:080DF57C edx:00000000 eflags:00200293 esi:080DF57C edi:00000000 esp:080DF494 ebp:080DF598 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t S z A p C [007B:080DF494]---------------------------------------------------------[stack] 080DF4C4 : 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 080DF4B4 : 7C F5 0D 08 00 00 00 00 - 00 00 00 00 00 00 00 00 |............... 080DF4A4 : F4 2F 0D B7 00 00 00 00 - 25 5E 07 B7 C5 58 00 00 ./......%^...X.. 080DF494 : 98 F5 0D 08 00 00 00 00 - 7C F5 0D 08 AB AF 19 B7 ........|....... [007B:080DF57C]---------------------------------------------------------[ data] 080DF57C : 40 B3 01 B7 C5 58 00 00 - FF FF FF FF FF FF FF FF @....X.......... 080DF58C : F4 2F 0D B7 00 00 00 00 - 18 F6 0D 08 E8 F5 0D 08 ./.............. [0073:FFFFE410]---------------------------------------------------------[ code] 0xffffe410 <__kernel_vsyscall+16>: pop %ebp 0xffffe411 <__kernel_vsyscall+17>: pop %edx 0xffffe412 <__kernel_vsyscall+18>: pop %ecx 0xffffe413 <__kernel_vsyscall+19>: ret 0xffffe414: nop 0xffffe415: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 200190
----------- .xsession-errors (49 sec old) --------------------- (evolution:7432): Gtk-CRITICAL **: gtk_icon_info_free: assertion `icon_info != NULL' failed ** (gnome-panel:7300): WARNING **: The calendar backend for file:///home/shevek/.evolution/tasks/local/system has crashed. ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/usa__en@holiday.calendar.google.com/public/basic.ics has crashed. ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/uk__en@holiday.calendar.google.com/public/basic.ics has crashed. ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/jewish__en@holiday.calendar.google.com/public/basic.ics has crashed. ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/u07vp0ai1ordsual9jjhm43vno@group.calendar.google.com/private-aee8639db8dfe773ae22ecd95a5f7d04/basic.ic ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/u336o8fgjqemvsab4vor6o1e68@group.calendar.google.com/private-a02ab0a877d3927de5192034b2473f52/basic.ic ** (gnome-panel:7300): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/google@anarres.org/private-e73486368347b8b4f0c5824e645695db/basic.ics has crashed. --------------------------------------------------
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 378854 ***