GNOME Bugzilla – Bug 477030
crash in Show Desktop:
Last modified: 2007-09-14 21:47:31 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 36048896 vsize: 36048896 resident: 12627968 share: 9318400 rss: 12627968 rss_rlim: 4294967295 CPU usage: start_time: 1189793983 rtime: 462 utime: 421 stime: 41 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 -1208494368 (LWP 2900)] (no debugging symbols found) 0x00146402 in __kernel_vsyscall ()
+ Trace 162975
Thread 1 (Thread -1208494368 (LWP 2900))
----------- .xsession-errors (1796 sec old) --------------------- localuser:ivan being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2737 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Loading "installonlyn" plugin libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files compiz: pixmap 0x12058c0 can't be bound to texture compiz: pixmap 0x1205f3d can't be bound to texture Loading "installonlyn" plugin /usr/lib/python2.5/site-packages/pirut/Progress.py:162: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed self.pbar.set_fraction(fract) --------------------------------------------------
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 ***