Bug 408166 – crash in Keyboard: starting it

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 408166 - crash in Keyboard: starting it


Summary:	crash in Keyboard: starting it


Status:	RESOLVED DUPLICATE of bug 370038

Product:	gnome-control-center
Classification:	Core
Component:	Keyboard
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-15 09:05 UTC by remco.slotboom
Modified:	2007-02-15 17:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description remco.slotboom 2007-02-15 09:05:05 UTC

Version: 2.16.1

What were you doing when the application crashed?
starting it


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 20525056 vsize: 0 resident: 20525056 share: 0 rss: 11173888 rss_rlim: 0
CPU usage: start_time: 1171530287 rtime: 0 utime: 22 stime: 0 cutime:19 cstime: 0 timeout: 3 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225587024 (LWP 5651)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110919

Thread 1 (Thread -1225587024 (LWP 5651))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 xkl_config_rec_dump
from /usr/lib/libxklavier.so.11
#5 xkl_config_rec_dump
from /usr/lib/libxklavier.so.11
#6 gconf_property_editor_marshal_VOID__STRING_POINTER
#7 gconf_property_editor_marshal_VOID__STRING_POINTER
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2007-02-15 17:01:40 UTC

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 370038 ***