GNOME Bugzilla – Bug 432449
crash in Panel: Changing the login photo...
Last modified: 2007-07-03 12:22:45 UTC
Version: 2.18.0 What were you doing when the application crashed? Changing the login photo for the face browser in GDM. I chose the guitar icon that comes in the pixmaps/faces directory (the default directory that opens when you choose to change the login photo). There was no photo selected previously. Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.0 2007-03-24 (Gentoo) BugBuddy Version: 2.18.0 System: Linux 2.6.19-gentoo-r2 #1 PREEMPT Sun Dec 31 02:01:46 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 141443072 vsize: 141443072 resident: 17776640 share: 13000704 rss: 17776640 rss_rlim: 18446744073709551615 CPU usage: start_time: 1177307966 rtime: 46 utime: 43 stime: 3 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 47100030288960 (LWP 9172)] 0x00002ad6530eaad5 in waitpid () from /lib/libpthread.so.0
+ Trace 129887
Thread 1 (Thread 47100030288960 (LWP 9172))
----------- .xsession-errors (28 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" "morgan" /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/9121 Initializing gnome-mount extension (gnome-panel:9172): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass changing all of these. Search for "dieguito-doing-incomplete-spam" to delete all this from your inbox.)
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 ***