GNOME Bugzilla – Bug 528532
crash in Panel: Just launched gnome-pane...
Last modified: 2008-04-17 09:24:22 UTC
Version: 2.22.1.2 What were you doing when the application crashed? Just launched gnome-panel automatically with gnome-session or from the command line. Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.22.1 2008-04-12 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.24-gentoo-r4 #1 SMP PREEMPT Tue Apr 1 20:59:24 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaVerdeOlivo Icon Theme: Mist Memory status: size: 279298048 vsize: 279298048 resident: 18284544 share: 13660160 rss: 18284544 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208423917 rtime: 13 utime: 11 stime: 2 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) 0x00002b5dacdc89f5 in waitpid () from /lib/libpthread.so.0
+ Trace 195439
----------- .xsession-errors (148 sec old) --------------------- /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/seahorse-agent --execute gnome-session SESSION_MANAGER=local/mangurrian:/tmp/.ICE-unix/3160 (gnome-panel:3222): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -236 and height 23 (gnome-panel:3222): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -236 and height 23 (gnome-panel:3222): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -236 and height 23 (gnome-panel:3222): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -254 and height 23 --------------------------------------------------
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 527441 ***