GNOME Bugzilla – Bug 483273
crash in Window Selector:
Last modified: 2007-10-11 17:44:40 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: LowContrast Memory status: size: 284876800 vsize: 284876800 resident: 11833344 share: 8499200 rss: 11833344 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191486954 rtime: 121 utime: 105 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496446720 (LWP 31788)] (no debugging symbols found) 0x0000003ad6e0d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 167638
Thread 1 (Thread 46912496446720 (LWP 31788))
----------- .xsession-errors (10 sec old) --------------------- ** WARNING **: dock_set_uposition: current screen size 1280x1024 smaller than window position specified in config file, resetting to x=640 y=512 ** WARNING **: dock_set_uposition: current screen size 1280x1024 smaller than window position specified in config file, resetting to x=640 y=512 ** WARNING **: dock_set_uposition: current screen size 1280x1024 smaller than window position specified in config file, resetting to x=640 y=512 ** WARNING **: dock_set_uposition: current screen size 1280x1024 smaller than window position specified in config file, resetting to x=640 y=512 ** WARNING **: dock_set_uposition: current screen size 1280x1024 smaller than window position specified in config file, resetting to x=640 y=512 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 420713 ***