GNOME Bugzilla – Bug 481180
crash in Panel: I was launching update n...
Last modified: 2007-10-02 21:32:18 UTC
Version: 2.20.0.1 What were you doing when the application crashed? I was launching update notifier Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 39608320 vsize: 39608320 resident: 24518656 share: 13443072 rss: 24518656 rss_rlim: 4294967295 CPU usage: start_time: 1190961762 rtime: 215 utime: 189 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ffb6b0 (LWP 3748)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 166097
Thread 1 (Thread 0xb6ffb6b0 (LWP 3748))
----------- .xsession-errors --------------------- amarok: WARNING: Pixmap not found for mimetype application/ogg amarok: WARNING: Pixmap not found for mimetype application/ogg amarok: WARNING: Pixmap not found for mimetype application/ogg amarok: WARNING: Pixmap not found for mimetype application/ogg amarok: WARNING: Pixmap not found for mimetype application/ogg ** (gnome-cups-icon:3871): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3871): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3871): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3871): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3871): WARNING **: IPP request failed with status 1280 --------------------------------------------------
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 480982 ***