GNOME Bugzilla – Bug 459786
crash in Workspace Switcher: i am jocking with the ea...
Last modified: 2007-07-25 17:53:01 UTC
Version: 2.18.0 What were you doing when the application crashed? i am jocking with the easy configuration and i haveclicked to easy on the eyes... great beryl!!! 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: 37920768 vsize: 37920768 resident: 13369344 share: 9838592 rss: 13369344 rss_rlim: 4294967295 CPU usage: start_time: 1185239980 rtime: 93 utime: 83 stime: 10 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 -1208330528 (LWP 3106)] (no debugging symbols found) 0x00e5c402 in __kernel_vsyscall ()
+ Trace 150134
Thread 1 (Thread -1208330528 (LWP 3106))
----------- .xsession-errors --------------------- ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg No framebuffer_object support! (only simple Blur aviable). --------------------------------------------------
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 403377 ***