GNOME Bugzilla – Bug 450965
crash in Panel: downloading a file
Last modified: 2007-06-26 09:44:27 UTC
Version: 2.18.1 What were you doing when the application crashed? downloading a file Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.1 2007-06-24 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-gentoo-r8 #2 SMP Tue Jun 19 10:12:11 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 123428864 vsize: 123428864 resident: 22638592 share: 18407424 rss: 22638592 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182795939 rtime: 52 utime: 47 stime: 5 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 47361894974448 (LWP 5445)] 0x00002b134b5c3ab5 in waitpid () from /lib/libpthread.so.0
+ Trace 143619
Thread 1 (Thread 47361894974448 (LWP 5445))
----------- .xsession-errors (394 sec old) --------------------- /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "root" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session SESSION_MANAGER=local/localhost:/tmp/.ICE-unix/5406 Initializing gnome-mount extension (gnome-panel:5445): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24 No running windows found --------------------------------------------------
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 422966 ***