Bug 368517 – 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 368517 - 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:

Duplicates:	370035 370040 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-31 20:13 UTC by avt-2048
Modified:	2006-11-03 17:59 UTC

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

Description avt-2048 2006-10-31 20:13:18 UTC

Version: 2.16.0

What were you doing when the application crashed?
Запуск "Индикатор раскладок клавиатуры 2.16.0.1. "


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 257957888 vsize: 257957888 resident: 13443072 share: 9469952 rss: 13443072 rss_rlim: -1
CPU usage: start_time: 1162325434 rtime: 17 utime: 13 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-keyboard-properties'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912508929600 (LWP 4335)]
(no debugging symbols found)
0x0000003fac60d935 in waitpid () from /lib64/libpthread.so.0

+ Trace 81143

Thread 1 (Thread 46912508929600 (LWP 4335))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 xkl_config_rec_dump
from /usr/lib64/libxklavier.so.11
#4 xkl_config_rec_dump
from /usr/lib64/libxklavier.so.11
#5 gconf_property_editor_marshal_VOID__STRING_POINTER
#6 gconf_property_editor_marshal_VOID__STRING_POINTER
#7 g_ascii_strcasecmp
#8 g_ascii_strcasecmp
#9 g_ascii_strcasecmp
#10 __libc_start_main
from /lib64/libc.so.6
#11 g_ascii_strcasecmp
#12 ??
#13 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Sergey V. Udaltsov 2006-10-31 20:57:19 UTC

Ghm... This stacktrace is not really useful. Would you be able to build libxklavier (3.1) with debug info?

Comment 2 André Klapper 2006-11-01 09:42:47 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 3 Karsten Bräckelmann 2006-11-03 15:26:09 UTC

*** Bug 370040 has been marked as a duplicate of this bug. ***

Comment 4 Karsten Bräckelmann 2006-11-03 15:26:16 UTC

*** Bug 370035 has been marked as a duplicate of this bug. ***

Comment 5 Karsten Bräckelmann 2006-11-03 17:59:35 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 ***