GNOME Bugzilla – Bug 370040
crash in Keyboard: try reconfigure keyboard
Last modified: 2006-11-03 15:26:09 UTC
Version: 2.16.0 What were you doing when the application crashed? try reconfigure keyboard Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- SESSION_MANAGER=local/vadim.internal.parkcode.com.ua:/tmp/.ICE-unix/2583 libGL warning: 3D driver claims to not support visual 0x4b ** (eggcups:2688): WARNING **: IPP request failed with status 1030 ** (eggcups:2688): WARNING **: IPP request failed with status 1030 compiz: water: GL_ARB_fragment_program is missing You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. compiz: pixmap 0xa01054 can't be bound to texture ** (bug-buddy:2829): WARNING **: Не удаётся загрузить значок для Открыть папку -------------------------------------------------- Memory status: size: 257916928 vsize: 257916928 resident: 11649024 share: 7909376 rss: 11649024 rss_rlim: -1 CPU usage: start_time: 1162565481 rtime: 8 utime: 6 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496353216 (LWP 2827)] (no debugging symbols found) 0x0000003080e0d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 82375
Thread 1 (Thread 46912496353216 (LWP 2827))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 368517 ***