GNOME Bugzilla – Bug 467998
crash in Panel:
Last modified: 2007-09-02 13:22:56 UTC
Version: 2.18.0 What were you doing when the application crashed? 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 Wed Jul 11 16:13:27 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: 27439104 vsize: 27439104 resident: 14548992 share: 10788864 rss: 14548992 rss_rlim: 4294967295 CPU usage: start_time: 1187457647 rtime: 122 utime: 99 stime: 23 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226508608 (LWP 2002)] (no debugging symbols found) 0xb7f37410 in __kernel_vsyscall ()
+ Trace 156180
Thread 1 (Thread -1226508608 (LWP 2002))
----------- .xsession-errors (37 sec old) --------------------- /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "sanjay" /etc/gdm/Xsession: Beginning session setup... /etc/gdm/Xsession: ssh-agent not found! /etc/gdm/Xsession: Setup done, will execute: gnome-session SESSION_MANAGER=local/toshiba:/tmp/.ICE-unix/1980 ** (gnome-cups-icon:2011): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:2011): WARNING **: IPP request failed with status 1280 (gnome-panel:2002): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 Initializing gnome-mount extension Initializing nautilus-open-terminal extension ** (nautilus:2006): WARNING **: libxine.so.1: cannot open shared object file: No such file or directory --------------------------------------------------
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 452428 ***