Bug 327049 - Crash of Systemsettings when in setup-keyboard clicked on "show example"
Summary: Crash of Systemsettings when in setup-keyboard clicked on "show example"
Status: RESOLVED NOT A BUG
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard_layout (show other bugs)
Version: 4.11.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-11-02 19:44 UTC by Ad Verburg
Modified: 2014-03-10 08:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
/usr/share/X11/xkb/rules/evdev.xml (187.65 KB, text/xml)
2013-11-03 08:35 UTC, Ad Verburg
Details
my kxkbrc-file (255 bytes, application/octet-stream)
2013-11-06 07:54 UTC, Ad Verburg
Details
root kxkbrc-file (255 bytes, application/octet-stream)
2013-11-06 07:56 UTC, Ad Verburg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ad Verburg 2013-11-02 19:44:48 UTC
Application: systemsettings (4.11.2)
KDE Platform Version: 4.11.2
Qt Version: 4.8.5
Operating System: Linux 3.11.6-33.gf7498bf-desktop x86_64
Distribution: "openSUSE 12.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: 
Mouse click on the button "Voorbeeld" (show layout) to show the keyboard layout.

-- Backtrace:
Application: Systeeminstellingen (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  QList (l=..., this=0x7fff295dd410) at /usr/include/QtCore/qlist.h:122
#7  QForeachContainer (t=..., this=0x7fff295dd410) at /usr/include/QtCore/qglobal.h:2368
#8  KCMKeyboardWidget::previewLayout (this=<optimized out>) at /usr/src/debug/kde-workspace-4.11.2/kcontrol/keyboard/kcm_keyboard_widget.cpp:380
#9  0x00007fba5c80844f in QMetaObject::activate (sender=sender@entry=0x306e690, m=m@entry=0x7fba5df3ce20 <QAbstractButton::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff295dd5f0) at kernel/qobject.cpp:3556
#10 0x00007fba5dadf582 in QAbstractButton::clicked (this=this@entry=0x306e690, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
#11 0x00007fba5d833b2e in QAbstractButtonPrivate::emitClicked (this=this@entry=0x29fd110) at widgets/qabstractbutton.cpp:548
#12 0x00007fba5d834360 in QAbstractButtonPrivate::click (this=this@entry=0x29fd110) at widgets/qabstractbutton.cpp:541
#13 0x00007fba5d8345cc in QAbstractButton::mouseReleaseEvent (this=0x306e690, e=0x7fff295dde90) at widgets/qabstractbutton.cpp:1123
#14 0x00007fba5d4c93f9 in QWidget::event (this=0x306e690, event=0x7fff295dde90) at kernel/qwidget.cpp:8376
#15 0x00007fba5d47992c in QApplicationPrivate::notify_helper (this=this@entry=0x256ef50, receiver=receiver@entry=0x306e690, e=e@entry=0x7fff295dde90) at kernel/qapplication.cpp:4562
#16 0x00007fba5d47e60b in QApplication::notify (this=this@entry=0x7fff295deaf0, receiver=receiver@entry=0x306e690, e=e@entry=0x7fff295dde90) at kernel/qapplication.cpp:4105
#17 0x00007fba5e18c016 in KApplication::notify (this=0x7fff295deaf0, receiver=0x306e690, event=0x7fff295dde90) at /usr/src/debug/kdelibs-4.11.2/kdeui/kernel/kapplication.cpp:311
#18 0x00007fba5c7f2f3e in QCoreApplication::notifyInternal (this=0x7fff295deaf0, receiver=receiver@entry=0x306e690, event=event@entry=0x7fff295dde90) at kernel/qcoreapplication.cpp:949
#19 0x00007fba5d47a76b in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231
#20 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x306e690, event=event@entry=0x7fff295dde90, alienWidget=alienWidget@entry=0x306e690, nativeWidget=nativeWidget@entry=0x2681600, buttonDown=buttonDown@entry=0x7fba5df4f288 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173
#21 0x00007fba5d4f5074 in QETWidget::translateMouseEvent (this=this@entry=0x2681600, event=event@entry=0x7fff295de600) at kernel/qapplication_x11.cpp:4528
#22 0x00007fba5d4f3e01 in QApplication::x11ProcessEvent (this=0x7fff295deaf0, event=event@entry=0x7fff295de600) at kernel/qapplication_x11.cpp:3651
#23 0x00007fba5d51a192 in x11EventSourceDispatch (s=0x2564e00, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#24 0x00007fba551117d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fba55111b08 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007fba55111bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007fba5c8215b6 in QEventDispatcherGlib::processEvents (this=0x2525a70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#28 0x00007fba5d519e0e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007fba5c7f1bef in QEventLoop::processEvents (this=this@entry=0x7fff295de9d0, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007fba5c7f1e78 in QEventLoop::exec (this=this@entry=0x7fff295de9d0, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007fba5c7f6bb8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#32 0x00007fba5d477bdc in QApplication::exec () at kernel/qapplication.cpp:3823
#33 0x000000000040b49e in main (argc=5, argv=0x7fff295dec38) at /usr/src/debug/kde-workspace-4.11.2/systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Andriy Rysin 2013-11-03 02:29:14 UTC
Could you please attach your kxkbrc file and /usr/share/X11/xkb/evdev.xml ?
Also which layout/variant was selected when you pressed "Show layout"?
Comment 2 Ad Verburg 2013-11-03 08:35:15 UTC
Created attachment 83309 [details]
/usr/share/X11/xkb/rules/evdev.xml
Comment 3 Ad Verburg 2013-11-03 08:41:22 UTC
kxkbrc not found on this system.
The layout was us_intl.
Comment 4 Ad Verburg 2013-11-03 09:17:05 UTC
Info added.
*Ad Verburg*
op 03-11-13 03:29, Andriy Rysin schreef:
> https://bugs.kde.org/show_bug.cgi?id=327049
>
> --- Comment #1 from Andriy Rysin <arysin@gmail.com> ---
> Could you please attach your kxkbrc file and /usr/share/X11/xkb/evdev.xml ?
> Also which layout/variant was selected when you pressed "Show layout"?
>
Comment 5 Andriy Rysin 2013-11-03 13:27:28 UTC
So there's no $HOME/.kde*/share/config/kxkbrc ?

There's no us_intl layout in your evdev.xml, did you mean us(intl) which is English (US) - international with dead keys?

Did you upgrade your system recently? If yes and you had some (old) layouts before, please remove all of them in the configuration and readd again.
Comment 6 Ad Verburg 2013-11-03 16:02:35 UTC
Yes, there is no kxkbdrc.
The only files in that folder are:
-rw------- 1 ad users 1717 23 okt 17:46 amarokrc
-rw------- 1 ad users  368 26 okt 12:06 cdbakeovenrc
-rw------- 1 ad users 1967 23 okt 17:51 kaffeinerc
-rw------- 1 ad users  844 26 okt 12:04 kconf_updaterc
-rw------- 1 ad users   76 23 okt 17:38 kcookiejarrc
-rw------- 1 ad users   39 23 okt 17:38 kdedrc
-rw------- 1 ad users   39 29 okt 18:39 kdeglobals
-rw------- 1 ad users   81 23 okt 17:38 kdeprintrc
-rw------- 1 ad users   69 23 okt 17:38 kio_httprc
-rw------- 1 ad users   92 23 okt 17:38 kioslaverc
-rw------- 1 ad users   35 23 okt 17:38 knfsshare
-rw------- 1 ad users 1084 26 okt 12:04 konversationrc
-rw------- 1 ad users   46 29 okt 18:39 kpowersaverc

Yes, I recently changed many KDE files from version 4.xx to 4.11.2.
In the past I worked with the composekey for "special" chars. 
Now the composekey is not working anaymore. That is the reason why I was fiddling with system settings.

Hereafter I gonna clean up the settings.
Thanks for your advise, I'll inform you later.
Comment 7 Ad Verburg 2013-11-03 22:02:18 UTC
The keyboard setting was: map US, layout English (US), variant none (Default).
That was the only one visible.

I removed that, and added: map US, layout English (US), variant English (US, with euro on 5)
Then clicking "preview" showed the layout as intended, without crash.
The compose key still does not do anything, and the keys for `,~,^,",' are dead keys.

The same procedure I had to do when I was logged in as root to prevent a crash.
Here the compose key works as intended, and the keys for `,~,^,",' are "normal" keys.

So the crash has been resolved.
Only the keyboard behavior I would like to see the same as for root.
Thanks.
Comment 8 Andriy Rysin 2013-11-05 02:51:56 UTC
So you're using exactly the same layout/variant between root and non-root user and the results are different? I would really like to see your kxkbrc file for both users. Also check if you don't have .xmodmap in your home directory
Comment 9 Ad Verburg 2013-11-05 14:16:21 UTC
Yes, the same layout/variant is chosen for root me and a new created guest.
Root and the guest keyboards act the same (correct) way, but for me different.

kxkbrc could not be found on the system using Dolphin in superuser mode.

.xmodmap (starting with a dot) is also not found. Without dot in /usr/bin/xmodmap, and /etc/X11/Xmodmap
Comment 10 Andriy Rysin 2013-11-06 03:05:39 UTC
I am not sure I understand this sentence "Root and the guest keyboards act the same (correct) way, but for me different".

Also kxkbrc the keyboard module won't work, so it should be present somewhere in the home directory.
Comment 11 Ad Verburg 2013-11-06 07:54:19 UTC
Created attachment 83364 [details]
my kxkbrc-file
Comment 12 Ad Verburg 2013-11-06 07:56:08 UTC
Created attachment 83365 [details]
root kxkbrc-file
Comment 13 Ad Verburg 2013-11-06 08:18:47 UTC
What I meant is: When logged in as root or as common user "gast" then the keyboard behaves correct, but when logged in as "ad" (that is me) then the keyboard behavior is different. (no compose and dead keys).

You are right, the kxkbrc-files exist in the root and users directories.
Trouble was (and is) that dolphin (4.11.2-5.5 ) did not find those files, and I concluded based on that that it does not exist. However I found those at last.
There is a difference in the sequence the options are written down.
Later I will try with copy / paste (from root to me) to see what the effect is.
Comment 14 Ad Verburg 2013-11-06 09:10:53 UTC
The copy/paste action had no effect on the behavior, but now the settings are identical.

In the the KDE Service Manager I did see that the Keyboard daemon was not ticked and was not running.
Switching the daemon to running, and marking the tick solved the problem.
Thanks for your thinking along.
Comment 15 Andriy Rysin 2013-11-06 15:01:07 UTC
Cool, I am glad you found the solution