GNOME Bugzilla – Bug 441617
crash in Panel: closed firefox
Last modified: 2007-05-27 16:51:59 UTC
Version: 2.18.0 What were you doing when the application crashed? closed firefox Distribution: Frugalware 0.6 (Terminus) Gnome Release: 2.18.0 2007-03-13 (Frugalware) BugBuddy Version: 2.18.0 System: Linux 2.6.20-fw4 #1 SMP PREEMPT Thu May 10 13:05:29 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Candido-Graphite2 Icon Theme: Mist Memory status: size: 33193984 vsize: 33193984 resident: 16838656 share: 12103680 rss: 16838656 rss_rlim: 4294967295 CPU usage: start_time: 1180280021 rtime: 788 utime: 664 stime: 124 cutime:0 cstime: 3 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226561856 (LWP 1977)] (no debugging symbols found) 0xb7f29410 in __kernel_vsyscall ()
+ Trace 136296
Thread 1 (Thread -1226561856 (LWP 1977))
----------- .xsession-errors (234 sec old) --------------------- ** (gnome-cups-icon:1987): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:1987): WARNING **: IPP request failed with status 1280 Initializing gnome-mount extension Initializing nautilus-open-terminal extension (gnome-panel:1977): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 ** (gnome-cups-icon:1987): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. (gnome-terminal:2063): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ADDED URL: harry_potter_phoenix-tlr1_h320.mov code: 51 speed -1 --------------------------------------------------
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 422966 ***