GNOME Bugzilla – Bug 370123
crash in Keyboard: loggin in
Last modified: 2006-11-03 17:58:13 UTC
Version: 2.16.0 What were you doing when the application crashed? loggin in 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:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/5195 libGL warning: 3D driver claims to not support visual 0x4b compiz: water: GL_ARB_fragment_program is missing ** (eggcups:5305): WARNING **: IPP request failed with status 1030 ** (eggcups:5305): WARNING **: IPP request failed with status 1030 Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Unable to connect to yum-updatesd... compiz: pixmap 0xc00438 can't be bound to texture compiz: pixmap 0xc006d2 can't be bound to texture Warning: Lisp directory `/usr/share/emacs/21.3.50/leim' does not exist. Xlib: unexpected async reply (sequence 0xc)! ** (bug-buddy:5529): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 25661440 vsize: 0 resident: 25661440 share: 0 rss: 11022336 rss_rlim: 0 CPU usage: start_time: 1162576204 rtime: 0 utime: 18 stime: 0 cutime:14 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (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 -1208439984 (LWP 5527)] (no debugging symbols found) 0x00d56402 in __kernel_vsyscall ()
+ Trace 82439
Thread 1 (Thread -1208439984 (LWP 5527))
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 368055 ***