Bug 397849 – crash in Keyboard:

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 397849 - crash in Keyboard:


Summary:	crash in Keyboard:


Status:	RESOLVED DUPLICATE of bug 368055

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-01-18 01:34 UTC by Steve
Modified:	2007-01-18 02:30 UTC

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

Description Steve 2007-01-18 01:34:58 UTC

Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 21651456 vsize: 0 resident: 21651456 share: 0 rss: 11530240 rss_rlim: 0
CPU usage: start_time: 1169084086 rtime: 0 utime: 16 stime: 0 cutime:14 cstime: 0 timeout: 2 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 -1225124176 (LWP 15873)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103135

Thread 1 (Thread -1225124176 (LWP 15873))

#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 Bruno Boaventura 2007-01-18 02:30:13 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 368055 ***