GNOME Bugzilla – Bug 449240
crash in Window Selector: I was switching between ...
Last modified: 2007-06-19 21:36:53 UTC
Version: 2.18.2 What were you doing when the application crashed? I was switching between windows. A little white rectangle with black border appeared above applications bar (this is the second time it happend, first time it showed up in center of the screen). It was "sticky" and "above" Distribution: Unknown Gnome Release: 2.18.2 2007-05-31 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.21-ARCH #1 SMP PREEMPT Mon Jun 11 23:47:51 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Mist Memory status: size: 27996160 vsize: 27996160 resident: 13975552 share: 10682368 rss: 13975552 rss_rlim: 4294967295 CPU usage: start_time: 1182272708 rtime: 768 utime: 708 stime: 60 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225046336 (LWP 6005)] (no debugging symbols found) 0xb7f25410 in __kernel_vsyscall ()
+ Trace 142230
Thread 1 (Thread -1225046336 (LWP 6005))
----------- .xsession-errors (512 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 /opt/mozilla/lib/firefox-2.0.0.4/run-mozilla.sh: line 131: 6871 Unicestwiony "$prog" ${1+"$@"} ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 420713 ***