GNOME Bugzilla – Bug 444970
crash in Show Desktop: moving a window from one...
Last modified: 2007-06-07 05:21:28 UTC
Version: 2.18.0 What were you doing when the application crashed? moving a window from one workspace to another 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Bluecurve Memory status: size: 50016256 vsize: 50016256 resident: 11632640 share: 8478720 rss: 11632640 rss_rlim: 4294967295 CPU usage: start_time: 1181173184 rtime: 750 utime: 681 stime: 69 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 -1208498464 (LWP 2913)] (no debugging symbols found) 0x00597402 in __kernel_vsyscall ()
+ Trace 138941
Thread 1 (Thread -1208498464 (LWP 2913))
----------- .xsession-errors (152 sec old) --------------------- libdvdnav: DVD disk reports itself with Region mask 0x00fe0000. Regions: 1 The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 102 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) No bind found for key 'F11'. Exiting... (Quit) compiz: pixmap 0xe1ef61 can't be bound to texture compiz: pixmap 0xe1f45b can't be bound to texture --------------------------------------------------
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 ***