GNOME Bugzilla – Bug 441620
crash in Panel: selecting edit menu
Last modified: 2007-05-27 17:29:09 UTC
Version: 2.18.0 What were you doing when the application crashed? selecting edit menu 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: 33411072 vsize: 33411072 resident: 17108992 share: 12271616 rss: 17108992 rss_rlim: 4294967295 CPU usage: start_time: 1180285755 rtime: 713 utime: 618 stime: 95 cutime:0 cstime: 1 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 -1226615104 (LWP 2031)] (no debugging symbols found) 0xb7f1d410 in __kernel_vsyscall ()
+ Trace 136297
Thread 1 (Thread -1226615104 (LWP 2031))
----------- .xsession-errors (8 sec old) --------------------- SESSION_MANAGER=local/toshiba:/tmp/.ICE-unix/1993 ** (gnome-cups-icon:2040): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:2040): WARNING **: IPP request failed with status 1280 Initializing gnome-mount extension Initializing nautilus-open-terminal extension (gnome-panel:2031): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 ** (gnome-cups-icon:2040): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2200003 specified for 0x2200075 (acroread). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2200003 specified for 0x22001e0 (Adobe Read). warning: .dynamic section for "/usr/X11R6/lib/libfreetype.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***