GNOME Bugzilla – Bug 455171
crash in Window Selector: I was dragging a mozilla...
Last modified: 2007-07-10 13:52:36 UTC
Version: 2.18.2 What were you doing when the application crashed? I was dragging a mozilla window from one workspace to the next. The desktop effects were enabled. I was dragging the window from a panel to the workspace window left. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Clearlooks Memory status: size: 49471488 vsize: 49471488 resident: 24690688 share: 21917696 rss: 24690688 rss_rlim: 4294967295 CPU usage: start_time: 1183989972 rtime: 144 utime: 131 stime: 13 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 -1209030944 (LWP 3708)] (no debugging symbols found) 0x00a02402 in __kernel_vsyscall ()
+ Trace 146737
Thread 1 (Thread -1209030944 (LWP 3708))
----------- .xsession-errors (418 sec old) --------------------- (gnome-background-properties:3739): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (gnome-background-properties:3739): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (gnome-background-properties:3739): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (gnome-background-properties:3739): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed --- Hash table keys for warning below: --> file:///home/Joe_Coleman (nautilus:3744): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) compiz: pixmap 0x10016be can't be bound to texture compiz: pixmap 0x100289f can't be bound to texture --------------------------------------------------
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 ***