Bug 353825 - Login by x2go in Plasma 5 crashes KCMInit
Summary: Login by x2go in Plasma 5 crashes KCMInit
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 5.4.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
: 355940 356701 358873 359010 360018 363065 366015 366687 383178 394985 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-12 11:26 UTC by Thomas Schmid
Modified: 2018-06-03 11:41 UTC (History)
24 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
systemd journal (273.44 KB, text/plain)
2015-11-25 08:12 UTC, Fabian Köster
Details
Patch for libXi preventing segfault (382 bytes, patch)
2015-11-25 08:42 UTC, Fabian Köster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Schmid 2015-10-12 11:26:24 UTC
Application: kdeinit5 ()

Qt Version: 5.4.2
Operating System: Linux 4.1.6-10-desktop x86_64
Distribution: "openSUSE Leap 42.1 Beta 1 (Malachite) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I am running openSuSE Leap 42.1 Beta1, with Plasma 5 as the default desktop environment. 
I installed x2go 4.0.5 including the Perl-Basedir-Module. When I try to login from another system using x2go client (4.0.5), KCMInit always chrashes during the login and session startup process. Running Plasma5 directly (without x2go) works OK. 

- Custom settings of the application:
Access is by x2go client: Configured is "KDE" as window manager to start.

- Additional info:
Accessing this box via x2go and using IceWM or MATE as windows manager / desktop
works OK.
While KCMinit crashes, the login and session start seems to complete. This assistant was able to start Firefox to let me create a login at KDE bug reporting.

-- Backtrace:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4e5d415780 (LWP 773))]

Thread 2 (Thread 0x7f4e48153700 (LWP 775)):
#0  0x00007f4e5b7cec1d in poll () from /lib64/libc.so.6
#1  0x00007f4e5acd2422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f4e5acd400f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f4e4a6a5ee9 in ?? () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007f4e5bb408cf in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007f4e591f10a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f4e5b7d704d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f4e5d415780 (LWP 773)):
[KCrash Handler]
#6  0x00007f4e4a46c2ac in XIFreeDeviceInfo () from /usr/lib64/libXi.so.6
#7  0x00007f4e45f3397f in ?? () from /usr/lib64/qt5/plugins/kcm_input.so
#8  0x00007f4e45f37461 in kcminit_mouse () from /usr/lib64/qt5/plugins/kcm_input.so
#9  0x00007f4e4a933d18 in KCMInit::runModule (this=this@entry=0x7fff019e56c0, libName=..., service=...) at /usr/src/debug/plasma-workspace-5.4.0/startkde/kcminit/main.cpp:86
#10 0x00007f4e4a93460c in KCMInit::runModules (this=this@entry=0x7fff019e56c0, phase=phase@entry=0) at /usr/src/debug/plasma-workspace-5.4.0/startkde/kcminit/main.cpp:128
#11 0x00007f4e4a934c13 in KCMInit::KCMInit (this=0x7fff019e56c0, args=...) at /usr/src/debug/plasma-workspace-5.4.0/startkde/kcminit/main.cpp:204
#12 0x00007f4e4a935d8b in kdemain (argc=1, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.4.0/startkde/kcminit/main.cpp:268
#13 0x0000000000408c03 in ?? ()
#14 0x000000000040564f in main ()

Reported using DrKonqi
Comment 1 Fabian Köster 2015-11-20 18:15:09 UTC
Backtrace with full debug symbols:

Application: kdeinit5 ()

Qt Version: 5.4.2
Operating System: Linux 4.2.6-gentoo x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:

The crash can be reproduced every time.

-- Backtrace:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd2933bc780 (LWP 7154))]

Thread 2 (Thread 0x7fd27fc6c700 (LWP 7156)):
#0  0x00007fd291ca42dd in poll () from /lib64/libc.so.6
#1  0x00007fd291415ac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fd29141772f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007fd281373939 in ?? () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007fd291ffca42 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007fd28fb3b334 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fd291cad1bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fd2933bc780 (LWP 7154)):
[KCrash Handler]
#6  XIFreeDeviceInfo (info=0x0) at /hdd/tmp/portage/x11-libs/libXi-1.7.5/work/libXi-1.7.5/src/XIQueryDevice.c:118
#7  0x00007fd27e52db9f in MouseSettings::apply (this=this@entry=0x7ffe69021060, force=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.3/work/plasma-desktop-5.4.3/kcms/input/mouse.cpp:723
#8  0x00007fd27e530ff5 in MouseSettings::apply (this=this@entry=0x7ffe69021060, force=force@entry=true) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.3/work/plasma-desktop-5.4.3/kcms/input/mouse.cpp:727
#9  0x00007fd27e533fe4 in kcminit_mouse () at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.3/work/plasma-desktop-5.4.3/kcms/input/main.cpp:56
#10 0x00007fd2814059d3 in KCMInit::runModule (this=this@entry=0x7ffe69021470, libName=..., service=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.3/work/plasma-workspace-5.4.3/startkde/kcminit/main.cpp:86
#11 0x00007fd281406296 in KCMInit::runModules (this=this@entry=0x7ffe69021470, phase=phase@entry=0) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.3/work/plasma-workspace-5.4.3/startkde/kcminit/main.cpp:128
#12 0x00007fd281406957 in KCMInit::KCMInit (this=this@entry=0x7ffe69021470, args=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.3/work/plasma-workspace-5.4.3/startkde/kcminit/main.cpp:204
#13 0x00007fd281407acb in kdemain (argc=1, argv=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.3/work/plasma-workspace-5.4.3/startkde/kcminit/main.cpp:268
#14 0x0000000000408540 in ?? ()
#15 0x0000000000404fb0 in main ()
Comment 2 Fabian Köster 2015-11-25 08:12:46 UTC
Created attachment 95717 [details]
systemd journal

The output of journalctl -b. Search for "x2go" to find start of plasma session via x2go.
Comment 3 Fabian Köster 2015-11-25 08:13:16 UTC
I am currently testing this on Plasma 5.5 Beta (aka 5.4.95).

While I do not get the segfault mentioned above anymore, I see other segfaults in dmesg and still the Plasma session is not fully started, e.g. there is no control bar (no application menu, window switcher etc.).

The segfaults are:

[  200.165902] kscreen_backend[2882]: segfault at 8 ip 00007fd588354e83 sp 00007fff49b56760 error 4 in KSC_XRandR.so[7fd58833d000+22000]
[  200.554712] kscreen_backend[2911]: segfault at 8 ip 00007fd781056e83 sp 00007ffcf9f1bb70 error 4 in KSC_XRandR.so[7fd78103f000+22000]
[  200.677220] kscreen_backend[2917]: segfault at 8 ip 00007fdc23be9e83 sp 00007ffc971b67c0 error 4 in KSC_XRandR.so[7fdc23bd2000+22000]
[  201.400974] kscreen_backend[2966]: segfault at 8 ip 00007f7ad32b0e83 sp 00007ffe6e6f8d30 error 4 in KSC_XRandR.so[7f7ad3299000+22000]
[  392.774658] kactivitymanage[2887]: segfault at 7ff03c017c50 ip 00007ff04b892071 sp 00007ffc10d92d98 error 4 in libQt5Sql.so.5.5.1[7ff04b87e000+3f000]

I already attached the output of journalctl in the previous comment.

Unfortunately those crashes only appear in dmesg but drkonqi is not launched. How can I get a full backtrace for those segfaults?

I will do anything needed to help fixing this bug (or set of bugs).
Comment 4 Fabian Köster 2015-11-25 08:14:40 UTC
Forgot to mention: I can launch krunner as usual using Alt-F2 and start KDE programs like console. I can terminate the session by pressing Strg+Alt+Entf and choosing to logout.
Comment 5 Fabian Köster 2015-11-25 08:42:52 UTC
Created attachment 95718 [details]
Patch for libXi preventing segfault

Sorry, please ignore my previous comments, I forgot that I applied a patch to libXi some days ago to help workaround this problem.

Without this patch this bug still occurs. The backtrace for Plasma 5.5 Beta (aka 5.4.95) is below.

I will open separate bugs for the other segfaults. Sorry for the chaos.

Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f973d582780 (LWP 2700))]

Thread 2 (Thread 0x7f9729f26700 (LWP 2702)):
#0  0x00007f973be3c2dd in poll () from /lib64/libc.so.6
#1  0x00007f973b5a6ac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f973b5a872f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f972b434c89 in QXcbEventReader::run (this=0x676a90) at qxcbconnection.cpp:1229
#4  0x00007f973c198492 in QThreadPrivate::start (arg=0x676a90) at thread/qthread_unix.cpp:331
#5  0x00007f9739cbb334 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f973be451bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f973d582780 (LWP 2700)):
[KCrash Handler]
#6  0x00007f972b1efc79 in XIFreeDeviceInfo (info=0x0) at /hdd/tmp/portage/x11-libs/libXi-1.7.5/work/libXi-1.7.5/src/XIQueryDevice.c:118
#7  0x00007f9723df0b8f in MouseSettings::apply (this=this@entry=0x7ffc10f07f70, force=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.95/work/plasma-desktop-5.4.95/kcms/input/mouse.cpp:723
#8  0x00007f9723df3fe5 in MouseSettings::apply (this=this@entry=0x7ffc10f07f70, force=force@entry=true) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.95/work/plasma-desktop-5.4.95/kcms/input/mouse.cpp:727
#9  0x00007f9723df6fd4 in kcminit_mouse () at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.4.95/work/plasma-desktop-5.4.95/kcms/input/main.cpp:56
#10 0x00007f972b4e59cb in KCMInit::runModule (this=this@entry=0x7ffc10f08370, libName=..., service=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.95/work/plasma-workspace-5.4.95/startkde/kcminit/main.cpp:86
#11 0x00007f972b4e6266 in KCMInit::runModules (this=this@entry=0x7ffc10f08370, phase=phase@entry=0) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.95/work/plasma-workspace-5.4.95/startkde/kcminit/main.cpp:128
#12 0x00007f972b4e6927 in KCMInit::KCMInit (this=this@entry=0x7ffc10f08370, args=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.95/work/plasma-workspace-5.4.95/startkde/kcminit/main.cpp:204
#13 0x00007f972b4e7a8b in kdemain (argc=1, argv=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.4.95/work/plasma-workspace-5.4.95/startkde/kcminit/main.cpp:268
#14 0x0000000000408560 in launch (argc=argc@entry=1, _name=0x60fd71 "kcminit_startup", args=<optimized out>, args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b17d "0") at /hdd/tmp/portage/kde-frameworks/kinit-5.16.0-r1/work/kinit-5.16.0/src/kdeinit/kinit.cpp:745
#15 0x0000000000405020 in main (argc=5, argv=<optimized out>) at /hdd/tmp/portage/kde-frameworks/kinit-5.16.0-r1/work/kinit-5.16.0/src/kdeinit/kinit.cpp:1825
Comment 6 Fabian Köster 2015-11-25 09:19:45 UTC
I created the separate bugs:

Bug #355877 - Segfault in kscreen_backend
Bug #355878 - Segfault in kactivitymanagerd
Comment 7 Christoph Feck 2015-12-03 13:34:30 UTC
*** Bug 355940 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2015-12-15 00:19:25 UTC
*** Bug 356701 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Feck 2016-02-02 03:38:23 UTC
*** Bug 358873 has been marked as a duplicate of this bug. ***
Comment 10 Amrit 2016-02-22 06:53:13 UTC
I am using: 
KDE Plasma Version: 5.5.4
Qt Version: 5.5.1
Kernel Version: 4.4.1-2-ARCH
OS TYPE: 64-bit

Whenever I lock the screen and try to log back in after couple minutes, It lets me in but I get the following bug notification and when I click on close, I get logged out and I have to log back in: 

Application: ksmserver (ksmserver), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fc9b533d07e in QXcbScreen::mapToNative(QRect const&) const () from /usr/lib/libQt5XcbQpa.so.5
#6  0x00007fc9b53422a3 in QXcbWindow::mapToNative(QRect const&, QXcbScreen const*) const () from /usr/lib/libQt5XcbQpa.so.5
#7  0x00007fc9b5343a9b in QXcbWindow::propagateSizeHints() () from /usr/lib/libQt5XcbQpa.so.5
#8  0x00007fc9b5348c2c in QXcbWindow::setGeometry(QRect const&) () from /usr/lib/libQt5XcbQpa.so.5
#9  0x00007fc9c982b26a in ?? () from /usr/lib/libKScreenLocker.so.5
#10 0x00007fc9c546c1a7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#11 0x00007fc9c5d89ff1 in QDesktopWidget::screenCountChanged(int) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007fc9c5d8b36d in ?? () from /usr/lib/libQt5Widgets.so.5
#13 0x00007fc9c546d1e1 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#14 0x00007fc9c5d7371b in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#15 0x00007fc9c5d309ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#16 0x00007fc9c5d35e86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#17 0x00007fc9c543dbab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#18 0x00007fc9c543ffa6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#19 0x00007fc9c5494143 in ?? () from /usr/lib/libQt5Core.so.5
#20 0x00007fc9bf22adc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007fc9bf22b020 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007fc9bf22b0cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007fc9c549454f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#24 0x00007fc9c543b57a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#25 0x00007fc9c544353c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#26 0x00007fc9c9df50e6 in kdemain () from /usr/lib/libkdeinit5_ksmserver.so
#27 0x00007fc9c9a60610 in __libc_start_main () from /usr/lib/libc.so.6
#28 0x00000000004007b9 in _start ()
Comment 11 kentaur 2016-02-22 21:02:45 UTC
Application: kdeinit5 ()

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Using FreeNX to login, using opennx client, causes KCMinit to crash.
.xsession-errors is available at http://tartu.uusmaa.ee/~kentaur/xsession-errors

Journalctl shows:
kernel: kscreen_backend[8600]: segfault at 8 ip 00007f43c19b1de3 sp 00007fff4a249cd0 error 4 in KSC_XRandR.so[7f43c199c000+2
kernel: kscreen_backend[8609]: segfault at 8 ip 00007fed8995cde3 sp 00007fff1879a450 error 4 in KSC_XRandR.so[7fed89947000+2
 org.kde.kglobalaccel[8534]: failed to get the current screen resources
org.kde.kglobalaccel[8534]: QXcbConnection: XCB error: 173 (Unknown), sequence: 163, resource id: 87, major code: 150 (Unkno
org.kde.kglobalaccel[8534]: failed to get the primary output of the screen
org.kde.kglobalaccel[8534]: QXcbConnection: XCB error: 1 (BadRequest), sequence: 385, resource id: 87, major code: 150 (Unkn
org.kde.KScreen[8534]: failed to get the current screen resources
org.kde.KScreen[8534]: QXcbConnection: XCB error: 173 (Unknown), sequence: 163, resource id: 87, major code: 150 (Unknown),
org.kde.KScreen[8534]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is:  1 . 2
org.kde.KScreen[8534]: failed to get the current screen resources
org.kde.KScreen[8534]: QXcbConnection: XCB error: 173 (Unknown), sequence: 163, resource id: 87, major code: 150 (Unknown),
org.kde.KScreen[8534]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is:  1 . 2
polkitd[1208]: Registered Authentication Agent for unix-session:557 (system bus name :1.2316 [/usr/lib64/libexec/polkit-kde-
org.kde.KScreen[8534]: failed to get the current screen resources
org.kde.KScreen[8534]: QXcbConnection: XCB error: 173 (Unknown), sequence: 163, resource id: 87, major code: 150 (Unknown),
org.kde.KScreen[8534]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is:  1 . 2
kernel: kscreen_backend[8681]: segfault at 8 ip 00007f3ca9876de3 sp 00007ffecc86b170 error 4 in KSC_XRandR.so[7f3ca9861000+2
sshd[7638]: pam_unix(sshd:session): session closed for user nx

The crash can be reproduced every time.

-- Backtrace:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f49c090d780 (LWP 7774))]

Thread 2 (Thread 0x7f49ab5c8700 (LWP 7776)):
#0  0x00007f49bec9dbbd in poll () from /lib64/libc.so.6
#1  0x00007f49be19c422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f49be19e00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f49ad91d3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f49bf01444f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007f49bc6ae0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f49beca5fed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f49c090d780 (LWP 7774)):
[KCrash Handler]
#6  0x00007f49ad6d72dc in XIFreeDeviceInfo () from /usr/lib64/libXi.so.6
#7  0x00007f49a91f565f in ?? () from /usr/lib64/qt5/plugins/kcm_input.so
#8  0x00007f49a91f8761 in kcminit_mouse () from /usr/lib64/qt5/plugins/kcm_input.so
#9  0x00007f49addcbdd9 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#10 0x00007f49addcc69c in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#11 0x00007f49addccca3 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#12 0x00007f49addcddfb in kdemain () from /usr/lib64/libkdeinit5_kcminit_startup.so
#13 0x0000000000408cc3 in ?? ()
#14 0x000000000040578f in main ()
Comment 12 Christoph Feck 2016-03-04 03:45:35 UTC
*** Bug 360018 has been marked as a duplicate of this bug. ***
Comment 13 Christoph Feck 2016-03-04 03:45:59 UTC
*** Bug 359010 has been marked as a duplicate of this bug. ***
Comment 14 kentaur 2016-03-15 15:35:59 UTC
*** This bug has been confirmed by popular vote. ***
Comment 15 aidanamarks 2016-05-10 03:31:13 UTC
Also seeing kcminit crash with FreeNX after upgrading to plasma5.  Can't get a desktop.  Complete backout to kde4 in progress.
Comment 16 Christoph Feck 2016-05-16 11:50:11 UTC
*** Bug 363065 has been marked as a duplicate of this bug. ***
Comment 17 Fabian Köster 2016-06-28 13:45:28 UTC
Still happening with Qt 5.6.1 and Plasma 5.7 Beta:

Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a59c25800 (LWP 3059))]

Thread 3 (Thread 0x7f7a462a3700 (LWP 3060)):
#0  0x00007f7a582b43ed in poll () from /lib64/libc.so.6
#1  0x00007f7a591538f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f7a591556df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f7a481dc009 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f7a58618e2c in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007f7a55f09434 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f7a582bd50d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7a3ffff700 (LWP 3062)):
#0  0x00007f7a582b43ed in poll () from /lib64/libc.so.6
#1  0x00007f7a5518cf2c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f7a5518d03c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f7a5880b40c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007f7a587bd12a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f7a58614674 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007f7a59b7b235 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007f7a58618e2c in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x00007f7a55f09434 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f7a582bd50d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7a59c25800 (LWP 3059)):
[KCrash Handler]
#6  XIFreeDeviceInfo (info=0x0) at /hdd/tmp/portage/x11-libs/libXi-1.7.6/work/libXi-1.7.6/src/XIQueryDevice.c:118
#7  0x00007f7a3f174cef in MouseSettings::apply (this=this@entry=0x7ffe22d91590, force=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.6.95/work/plasma-desktop-5.6.95/kcms/input/mouse.cpp:730
#8  0x00007f7a3f177c35 in MouseSettings::apply (this=this@entry=0x7ffe22d91590, force=force@entry=true) at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.6.95/work/plasma-desktop-5.6.95/kcms/input/mouse.cpp:734
#9  0x00007f7a3f17ade4 in kcminit_mouse () at /hdd/tmp/portage/kde-plasma/plasma-desktop-5.6.95/work/plasma-desktop-5.6.95/kcms/input/main.cpp:56
#10 0x00007f7a48294a08 in KCMInit::runModule (this=this@entry=0x7ffe22d91990, libName=..., service=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.6.95-r1/work/plasma-workspace-5.6.95/startkde/kcminit/main.cpp:86
#11 0x00007f7a482951ef in KCMInit::runModules (this=this@entry=0x7ffe22d91990, phase=phase@entry=0) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.6.95-r1/work/plasma-workspace-5.6.95/startkde/kcminit/main.cpp:128
#12 0x00007f7a48295998 in KCMInit::KCMInit (this=this@entry=0x7ffe22d91990, args=...) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.6.95-r1/work/plasma-workspace-5.6.95/startkde/kcminit/main.cpp:204
#13 0x00007f7a48296931 in kdemain (argc=1, argv=<optimized out>) at /hdd/tmp/portage/kde-plasma/plasma-workspace-5.6.95-r1/work/plasma-workspace-5.6.95/startkde/kcminit/main.cpp:268
#14 0x000000000040828f in launch (argc=argc@entry=1, _name=0x615331 "kcminit_startup", args=<optimized out>, args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40ad53 "0") at /hdd/tmp/portage/kde-frameworks/kinit-5.23.0/work/kinit-5.23.0/src/kdeinit/kinit.cpp:744
#15 0x0000000000404d20 in main (argc=5, argv=<optimized out>) at /hdd/tmp/portage/kde-frameworks/kinit-5.23.0/work/kinit-5.23.0/src/kdeinit/kinit.cpp:1827
Comment 18 Christoph Feck 2016-07-27 11:45:15 UTC
*** Bug 366015 has been marked as a duplicate of this bug. ***
Comment 19 Christoph Feck 2016-08-14 11:07:05 UTC
*** Bug 366687 has been marked as a duplicate of this bug. ***
Comment 20 Samuel Bernardo 2016-08-16 11:05:12 UTC
Reading the x2go desktop compatibility page, they don't support GLX 1.3 used in KDE5. So plasmashell can't work as expected, as mentioned in the following page:
http://wiki.x2go.org/doku.php/doc:de-compat

So in plasma 5 this is not a bug, but a limitation from x2go.
Comment 21 Fabian Köster 2016-08-16 11:17:26 UTC
(In reply to Samuel Bernardo from comment #20)
> Reading the x2go desktop compatibility page, they don't support GLX 1.3 used
> in KDE5. So plasmashell can't work as expected, as mentioned in the
> following page:
> http://wiki.x2go.org/doku.php/doc:de-compat

In fact Plasma 5 is working quite well using x2go, so I am wondering if this limitation is really true.

> So in plasma 5 this is not a bug, but a limitation from x2go.

This bug is about KCMInit crashing, which does not necessarily have to to with x2go lacking support for GLX 1.3. Maybe someone with deeper knowledge of the Plasma X11 stack can tell from which component this bug really comes from and whether it should be fixed or if we should wait for proper Wayland Remote Desktop support in Plasma.
Comment 22 Samuel Bernardo 2016-08-16 12:13:15 UTC
(In reply to Fabian Köster from comment #21)
> In fact Plasma 5 is working quite well using x2go, so I am wondering if this
> limitation is really true.

I have a segfault with KCMInit at login and plasmashell at logout.
I'm using KDE 5.7.3.

> This bug is about KCMInit crashing, which does not necessarily have to to
> with x2go lacking support for GLX 1.3. Maybe someone with deeper knowledge
> of the Plasma X11 stack can tell from which component this bug really comes
> from and whether it should be fixed or if we should wait for proper Wayland
> Remote Desktop support in Plasma.

I confirm that I can use remote x2go session besides the mentioned bugs of login and logout. All applications I use seems to work without any problem, but maybe that happens because they don't use GLX 1.3.
I'll be waiting for an answer of someone expert in KDE and x2go. I already sent an email to x2go-users mailing list.
Comment 23 Samuel Bernardo 2016-08-16 12:34:54 UTC
I'm detecting another problem with x2go session with kde5. GPU memory associated with X is always growing where x2go client is running...
I can't reproduce the problem when using other applications.
Can anyone reproduce the same memory leak on GPU?

I'm using x2goclient 4.0.3.2 and x2goserver 4.0.1.19.

I mentioned this because I don't know if it's related with KCMInit crash.
Comment 24 Samuel Bernardo 2016-08-16 17:06:51 UTC
(In reply to Samuel Bernardo from comment #23)
> I'm detecting another problem with x2go session with kde5. GPU memory
> associated with X is always growing where x2go client is running...
> I can't reproduce the problem when using other applications.
> Can anyone reproduce the same memory leak on GPU?
> 
> I'm using x2goclient 4.0.3.2 and x2goserver 4.0.1.19.
> 
> I mentioned this because I don't know if it's related with KCMInit crash.

I tested x2go with mate and the gpu memory problem persists with X. Maybe this is another problem related to the kde or the nvidia driver in my local PC. I don't know how to analyse the problem, since I haven't a gpu from another manufacturer and can't get the context of X process inside GPU memory...

I'm using kde 5.7.3 and nvidia driver 367.35.
Comment 25 Monty Scroggins 2016-09-14 19:07:52 UTC
I have been doing some testing since I cannot get kde to start over x2go with plasma5 (linux Mint 18 x64).  I am getting the same KCMInit issue on startup.   

To see if the issue is X2go related, I downloaded and installed nomachine.   I did not experience the same DCMInit issue and the desktop did load remotely.   Unfortunately nomachine isnt nearly as fast as x2go (at least for me over my internet connection) so its not a viable alternative. 

Linux Mint 18 KDE
x2goclient 4.0.5.1-1
x2goserver 4.0.1.19-0~1064~ubuntu16.04.1

I hope this info is helpful
Comment 26 Bernd Lentes 2016-09-26 17:12:59 UTC
Hi,

i'm having the problem on a SLES 12 SP1 with KDE "i don't know exactly".
This is my output from rpm:
kde-cli-tools5-5.5.5-9.1.x86_64
kde-cli-tools5-lang-5.5.5-9.1.noarch
kdepim-15.12.3-3.2.x86_64
kde-user-manager-5.5.5-3.1.x86_64
kdelibs4-core-4.14.18-2.1.x86_64
kde4-filesystem-4.14-2.1.x86_64
kde-oxygen-fonts-0.4.0-2.1.noarch
kdepim-runtime-15.12.3-3.1.x86_64
kded-lang-5.20.0-2.1.noarch
kdelibs4support-5.20.0-3.1.x86_64
kdeclarative-components-5.20.0-2.1.x86_64
kded-5.20.0-2.1.x86_64
kdelibs4-4.14.18-2.1.x86_64
kde-gtk-config5-5.5.5-2.1.x86_64
kde-gtk-config5-lang-5.5.5-2.1.noarch
kdelibs4-branding-upstream-4.14.18-2.1.x86_64
kdebase4-runtime-15.12.3-3.3.x86_64
kdelibs4support-lang-5.20.0-3.1.noarch
kdeconnect-kde5-0.8.99git.20160610T230134~dc2a2b5-3.1.x86_64
kdepimlibs4-4.14.10-3.1.x86_64

Login locally is possible. Login via nomachine NX not.
I'm using NX 3.5. As Fabian mentioned i can start programs like xconsole or xterm via ALT+F2, although system seems to be stucked.

While login via NX i get the error:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f782f3780 (LWP 30488))]

Thread 2 (Thread 0x7f7f637f6700 (LWP 30490)):
#0  0x00007f7f763e5bfd in poll () from /lib64/libc.so.6
#1  0x00007f7f76d992f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f7f76d9adcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f7f6620d199 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f7f7675c32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007f7f73e800a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f7f763ee02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7f782f3780 (LWP 30488)):
[KCrash Handler]
#6  0x00007f7f65fc72cc in XIFreeDeviceInfo () from /usr/lib64/libXi.so.6
#7  0x00007f7f60b3468f in ?? () from /usr/lib64/qt5/plugins/kcm_input.so
#8  0x00007f7f60b37791 in kcminit_mouse () from /usr/lib64/qt5/plugins/kcm_input.so
#9  0x00007f7f666bae79 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#10 0x00007f7f666bb73c in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#11 0x00007f7f666bbd43 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#12 0x00007f7f666bce91 in kdemain () from /usr/lib64/libkdeinit5_kcminit_startup.so
#13 0x0000000000408e3c in ?? ()
#14 0x00000000004059af in main ()

/var/log/messages says:
2016-09-26T18:28:15.661431+02:00 pc65518 org.kde.KScreen[30463]: failed to get the current screen resources
2016-09-26T18:28:15.902590+02:00 pc65518 org.kde.KScreen[30463]: QXcbConnection: XCB error: 173 (Unknown), sequence: 167, resource id: 87, major code: 150 (Unknown), minor code: 20
2016-09-26T18:28:15.904917+02:00 pc65518 kernel: [262612.809146] kscreen_backend[30589]: segfault at 8 ip 00007f6b989c16f3 sp 00007ffca0f07070 error 4 in KSC_XRandR.so[7f6b989ac000+20000]

Monty, which NX version did you try ?

If i can assist with further information please let me know.

Bernd
Comment 27 Monty Scroggins 2016-09-26 17:51:16 UTC
I am using the latest X2Go which is a branch of the NX libraries.

One thing about this..  Searching around, I found discussions where it was mentioned that error is that plasma 5 requires GLX 1.3..  but I am not sure this is the cause..  I think GLX 1.3 is pretty old..  I loaded the nvidia drivers and they show GLX 1.4..    

Another interesting thing..  I was doing some testing with the KDE Neon distro..   It discovered it will work with this release.. The KCMInit error still occurs, but the taskbar etc still get loaded and the desktop seems fine afterwards..     I posted a message on one of the LinuxMint message boards to see if anyone had any ideas as to what package it is that is causing the problem, but I havent had any responses.
Comment 28 Monty Scroggins 2016-09-26 18:19:42 UTC
If someone can forward the commands to collect the version info you want I will be happy to post.. I am not a newbie but dont know exactly how to get the info.

Monty
Comment 29 Bernd Lentes 2016-09-26 20:50:35 UTC
Wrong question.
Monty, which nomachine version did you try ?

Bernd
Comment 30 Monty Scroggins 2016-09-26 20:57:04 UTC
I am using x2go is based off a branch of the nx package (like nomachine is)

I did do some testing last week and downloaded the latest nomachine packages from their website.. I had the same issue and removed the nomachine bundle.   It looks like the version I tested was 5.1.44_1 x64
Comment 31 Bernd Lentes 2016-09-26 22:42:56 UTC
Monty, i'm a bit confused.
You wrote: I downloaded and installed nomachine.   I did not experience the same DCMInit issue and the desktop did load remotely.  

Some comments later you said:

I did do some testing last week and downloaded the latest nomachine packages from their website.. I had the same issue and removed the nomachine bundle. 

Did you have the same issue or not ?

Bernd
Comment 32 Monty Scroggins 2016-09-26 23:01:09 UTC
Ah dang I should have proof read the posting better.. I had the same exact behavior with nomachine and then removed the packages.
Comment 33 Bernd Lentes 2016-09-27 09:31:53 UTC
OK. My first impression is that this points very clearly to a KDE bug.
But does not FreeNX and X2Go depend on libraries from nomachine ?
So that they have the same or a similiar codebase ?

Bernd
Comment 34 Monty Scroggins 2016-09-27 11:39:25 UTC
I am not a developer, but Yes i believe FreeNX, X2Go, Nomachine (and others) all are based the NX libraries.
Comment 35 Bernd Lentes 2016-09-27 11:56:52 UTC
Hi,
sorry to ask something very fundamental, but this is my first time i'm participating in a bug tracking system.
Status "confirmed" means that the KDE Developer say "Yes, that's a bug in our software" ?
Assigned to "unassigned bugs mailing list" means what ? No one really cares about it ? We have to wait and pray ?

Importance: "NOR crash with 187 votes (vote)" means what ? The more votes a bug has the more important it seems to be from the point of view from the users ?
I gave one vote. What means "nor crash" ?

Can we do anything ?

Bernd
Comment 36 David Edmundson 2016-09-28 18:27:25 UTC
Git commit 46f58907179f92ebf64d0411a5dca20a0d318150 by David Edmundson.
Committed on 28/09/2016 at 18:27.
Pushed by davidedmundson into branch 'Plasma/5.8'.

Check fetching XIQueryDevice succeeded

This can crash on systems without XI, such as x2go

M  +3    -0    kcms/input/mouse.cpp

http://commits.kde.org/plasma-desktop/46f58907179f92ebf64d0411a5dca20a0d318150
Comment 37 Christoph Feck 2017-08-06 02:23:23 UTC
*** Bug 383178 has been marked as a duplicate of this bug. ***
Comment 38 Christoph Feck 2018-06-03 11:41:57 UTC
*** Bug 394985 has been marked as a duplicate of this bug. ***