GNOME Bugzilla – Bug 393725
crash in Keyboard Shortcuts: closing after making som...
Last modified: 2007-01-07 20:25:16 UTC
Version: 2.17.3 What were you doing when the application crashed? closing after making some changes to keyboard shortcuts Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc) BugBuddy Version: 2.17.3 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Enabled Memory status: size: 47595520 vsize: 0 resident: 47595520 share: 0 rss: 12677120 rss_rlim: 0 CPU usage: start_time: 1168127527 rtime: 0 utime: 649 stime: 0 cutime:583 cstime: 0 timeout: 66 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keybinding-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 -1209001216 (LWP 27310)] (no debugging symbols found) 0x00bac402 in __kernel_vsyscall ()
+ Trace 100037
Thread 1 (Thread -1209001216 (LWP 27310))
----------- .xsession-errors (23 sec old) --------------------- connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:2094): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory Link points to "/tmp/ksocket-ggw" Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0x4000012 (Run as roo). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0x4000012 (Run as roo). GTK Accessibility Module initialized Bonobo accessibility support initialized (gnome-keybinding-properties:27315): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 364839 ***