GNOME Bugzilla – Bug 423858
crash in Keyboard: I was trying to configur...
Last modified: 2007-03-28 19:49:14 UTC
Version: 2.18.0 What were you doing when the application crashed? I was trying to configure the keyboard settings Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.18.0 2007-03-28 (JHBuild) BugBuddy Version: 2.18.0 System: Linux 2.6.17-11-powerpc #2 Thu Feb 1 17:56:02 UTC 2007 ppc X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 28061696 vsize: 28061696 resident: 13099008 share: 10862592 rss: 13099008 rss_rlim: 4294967295 CPU usage: start_time: 1175109718 rtime: 90 utime: 81 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome2/bin/gnome-keyboard-properties' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 805543168 (LWP 4139)] 0x0faa7334 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 123000
Thread 1 (Thread 805543168 (LWP 4139))
----------- .xsession-errors (9 sec old) --------------------- GTK Accessibility Module initialized Window manager warning: Failed to read saved session file /home/betatester/.metacity/sessions/default0.ms: Failed to open file '/home/betatester/.metacity/sessions/default0.ms': No such file or direct GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized (nautilus:4077): Liboobs-WARNING **: Failed to connect to socket /opt/gnome2/var/run/dbus/system_bus_socket: No such file or directory seahorse nautilus module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 370038 ***