[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Bernd Lentes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #35 from Bernd Lentes  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Bernd Lentes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #33 from Bernd Lentes  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Bernd Lentes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #31 from Bernd Lentes  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Bernd Lentes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #29 from Bernd Lentes  ---
Wrong question.
Monty, which nomachine version did you try ?

Bernd

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Bernd Lentes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

Bernd Lentes  changed:

   What|Removed |Added

 CC||bernd.lentes@helmholtz-muen
   ||chen.de

--- Comment #26 from Bernd Lentes  ---
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  0x7f7f763e5bfd in poll () from /lib64/libc.so.6
#1  0x7f7f76d992f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f7f76d9adcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f7f6620d199 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7f7675c32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f7f73e800a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f7f763ee02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7f782f3780 (LWP 30488)):
[KCrash Handler]
#6  0x7f7f65fc72cc in XIFreeDeviceInfo () from /usr/lib64/libXi.so.6
#7  0x7f7f60b3468f in ?? () from /usr/lib64/qt5/plugins/kcm_input.so
#8  0x7f7f60b37791 in kcminit_mouse () from
/usr/lib64/qt5/plugins/kcm_input.so
#9  0x7f7f666bae79 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#10 0x7f7f666bb73c in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#11 0x7f7f666bbd43 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so
#12 0x7f7f666bce91 in kdemain () from
/usr/lib64/libkdeinit5_kcminit_startup.so
#13 0x00408e3c in ?? ()
#14 0x004059af 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 7f6b989c16f3 sp 7ffca0f07070
error 4 in KSC_XRandR.so[7f6b989ac000+2]

Monty, which NX version did you try ?

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

Bernd

-- 
You are receiving this mail because:
You are watching all bug changes.