GNOME Bugzilla – Bug 560437
crash in Keyboard Indicator: Plugged in an external k...
Last modified: 2008-11-12 15:25:22 UTC
Version: 2.22.3 What were you doing when the application crashed? Plugged in an external keyboard. Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.22.3 2008-10-09 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.25-gentoo-r3 #6 SMP Thu Jun 5 12:32:29 PDT 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 243769344 vsize: 243769344 resident: 8462336 share: 6500352 rss: 8462336 rss_rlim: 18446744073709551615 CPU usage: start_time: 1226293519 rtime: 290 utime: 197 stime: 93 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/gnome-keyboard-applet' [Thread debugging using libthread_db enabled] [New Thread 0x7f82ff5c4770 (LWP 2574)] 0x00007f82fa214e65 in __libc_waitpid (pid=1261, stat_loc=0x7fff07616ee0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32 32 return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 209677
Thread 1 (Thread 0x7f82ff5c4770 (LWP 2574))
----------- .xsession-errors (41023 sec old) --------------------- ** (nm-applet:2524): CRITICAL **: nm_gconf_wso_set_key: assertion `key != NULL' failed ** (nm-applet:2524): WARNING **: <WARN> real_write_secrets_cb(): Error saving secret for wireless network 'BoxerWireless' in keyring: 5 ** (nm-applet:2524): CRITICAL **: nm_gconf_wso_set_key: assertion `key != NULL' failed ** (nm-applet:2524): WARNING **: <WARN> real_write_secrets_cb(): Error saving secret for wireless network 'BoxerWireless' in keyring: 5 ** (nm-applet:2524): CRITICAL **: nm_gconf_wso_set_key: assertion `key != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
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 553915 ***