GNOME Bugzilla – Bug 369309
crash in Keyboard: Opening keybord settings
Last modified: 2006-11-02 12:58:58 UTC
Version: 2.16.0 What were you doing when the application crashed? Opening keybord settings 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 --------------------- the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. Loading "installonlyn" plugin Loading "installonlyn" plugin CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... Loading "installonlyn" plugin warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 1ac70ce6 Importing GPG key 0x1AC70CE6 "Fedora Project <fedora-extras@fedoraproject.org>" libGL warning: 3D driver claims to not support visual 0x4b ** (bug-buddy:22350): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 25559040 vsize: 0 resident: 25559040 share: 0 rss: 9814016 rss_rlim: 0 CPU usage: start_time: 1162458305 rtime: 0 utime: 32 stime: 0 cutime:27 cstime: 0 timeout: 5 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 -1208768288 (LWP 22348)] (no debugging symbols found) 0x00dde402 in __kernel_vsyscall ()
+ Trace 81802
Thread 1 (Thread -1208768288 (LWP 22348))
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 ***