|
Bugzilla – Full Text Bug Listing |
| Summary: | [kyast] kcmshell crashed (SIGSEGV) upon launching Keyboard Layout app | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Dzmitry Prakapenka <4maillists> |
| Component: | YaST2 | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | ||
| Version: | unspecified | ||
| Target Milestone: | RC 1 | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Loading the keyboard module
SIGSEGV crash window Error message Ldd kcmshell output Strace kcmshell output |
||
|
Description
Dzmitry Prakapenka
2005-12-02 18:18:48 UTC
I was not able to reproduce this on my test machine, it works fine. Sorry but the backtrace is not very useful without the debug symbols, which can be found in the *-debuginfo packages which are available via FTP. Does this happen only with the keyboard module or with other modules, too? You might provide more information about your hardware (hwinfo --keyboard). This issue seems to occur only with this module on my machine.
Could you specify which specific debuginfo packages I would need to install to provide you with the debugging symbols? I cannot install all available due to space limitations...
Here's the output of hwinfo --keyboard:
hwinfo --keyboard
23: PS/2 00.0: 10800 Keyboard
[Created at input.137]
UDI: /org/freedesktop/Hal/devices/computer_i8042_Kbd_Port_logicaldev_input
Unique ID: EXC1.TBWTwSuMeW2
Hardware Class: keyboard
Model: "AT Translated Set 2 keyboard"
Vendor: int 0x0211
Device: int 0x0001 "AT Translated Set 2 keyboard"
Device File: /dev/input/event1
Device Number: char 13:65
Driver Info #0:
XkbRules: xfree86
XkbModel: pc104
Config Status: cfg=no, avail=yes, need=no, active=unknown
I reproduced the issue and this time an additional error message was displayed:
http://img496.imageshack.us/my.php?image=snapshot111zq.png
As per the error message, I'm including the additional info:
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc104", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "us", "", ""
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
overrideSettings = true
options = []
Please don't use links to refer to external sources. Always use the attachment-feature of bugzilla (see below). Could you please attach the used screenshots and all further ones here? This ensures the availibility of these sources. Thanks. As for the debug packages: You should install the kdelibs3-debuginfo package, this should do fine. Recreate the backtrace afterwards. Thanks. Created attachment 60143 [details]
Loading the keyboard module
Created attachment 60144 [details]
SIGSEGV crash window
Created attachment 60145 [details]
Error message
I re-attached the screenshots. I installed the kdelibs3-debuginfo package but the backtrace is without the debugging symbols again: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1096193088 (LWP 16362)] (no debugging symbols found) (no debugging symbols found) [KCrash handler] #7 0x40197d29 in KCModuleProxy::realModule () from /opt/kde3/lib/libkutils.so.1 #8 0x40031d2a in kdemain () from /opt/kde3/lib/libkdeinit_kcmshell.so #9 0x4004aea0 in __libc_start_main () from /lib/tls/libc.so.6 #10 0x08048451 in ?? () OK, this would require libthread_db-debuginfo, but before we spend ages here: Just use ltrace to create a backtrace and attach the output here. This should be sufficient, thanks. The output from ltrace: __libc_start_main(0x80484f0, 6, 0xbf9c0de4, 0x8048510, 0x8048580 <unfinished ...> kdemain(6, 0xbf9c0de4, 0xbf9c0e00, 1, 0x40150ff4kbuildsycoca running... <unfinished ...> --- SIGCHLD (Child exited) --- QObject::connect: Cannot connect (null)::changed( bool ) to KCModuleProxy::moduleChanged(bool) QObject::connect: Cannot connect (null)::destroyed() to KCModuleProxy::moduleDestroyed() QObject::connect: Cannot connect (null)::quickHelpChanged() to KCModuleProxy::quickHelpChanged() --- SIGSEGV (Segmentation fault) --- KCrash: Application 'kcmshell' crashing... KWrited - Listening on Device /dev/pts/0 --- SIGCHLD (Child exited) --- +++ exited (status 253) +++ OK, I'll reassign it now ;) We need help from the KDE maintainers, though. ltrace -f would have been more interesting.. strace and ldd are intersting as well. ltrace -f produced the following output: __libc_start_main(0x80484c0, 6, 0xbf8c54d4, 0x80484e0, 0x8048550 <unfinished ...> kdemain(6, 0xbf8c54d4, 0xbf8c54f0, 1, 0x40150ff4QObject::connect: Cannot connect (null)::changed( bool ) to KCModuleProxy::moduleChanged(bool) QObject::connect: Cannot connect (null)::destroyed() to KCModuleProxy::moduleDestroyed() QObject::connect: Cannot connect (null)::quickHelpChanged() to KCModuleProxy::quickHelpChanged() <unfinished ...> --- SIGSEGV (Segmentation fault) --- KCrash: Application 'kcmshell' crashing... Segmentation fault The ldd output and strace outputs are saved as attachments. Created attachment 60788 [details]
Ldd kcmshell output
Created attachment 60789 [details]
Strace kcmshell output
we do no longer support yast modules in kcontrol *** This bug has been marked as a duplicate of 139343 *** |
