[X2Go-User] client kde-wayland crashes

Fri May 3 13:15:39 CEST 2019

client is fedora 30, using kde/wayland.  Server is also fedora 30
(mate).  Xwayland was running.  Legacy X
clients are supported.
x2goclient segfaulted on startup.
Here is the trace:

Application: x2goclient (x2goclient), signal: Segmentation fault

Using host libthread_db library "/lib64/libthread_db.so.1".

[Current thread is 1 (Thread 0x7f97e923fb40 (LWP 17000))]

Thread 4 (Thread 0x7f97d7fff700 (LWP 17004)):

#0 0x00007f97ec8132b7 in poll () from /lib64/libc.so.6

#1 0x00007f97ee0a98e7 in ?? () from /lib64/libssh.so.4

#2 0x00007f97ee0aa8e0 in ?? () from /lib64/libssh.so.4

#3 0x00007f97ee090e13 in ssh_channel_poll () from /lib64/libssh.so.4

#4 0x00007f97ee094e15 in ssh_select () from /lib64/libssh.so.4

#5 0x0000558c21444ba7 in ?? ()

#6 0x0000558c2144988b in ?? ()

#7 0x00007f97ecbda8a6 in ?? () from /lib64/libQt5Core.so.5

#8 0x00007f97ecb045a2 in start_thread () from /lib64/libpthread.so.0

#9 0x00007f97ec81e023 in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f97de5e3700 (LWP 17003)):

#0 0x00007f97ecb0a4e5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0

#1 0x00007f97de9dd54b in ?? () from /usr/lib64/dri/i965_dri.so

#2 0x00007f97de9dd28b in ?? () from /usr/lib64/dri/i965_dri.so

#3 0x00007f97ecb045a2 in start_thread () from /lib64/libpthread.so.0

#4 0x00007f97ec81e023 in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f97dfc01700 (LWP 17002)):

#0 0x00007f97ecb0dbdc in read () from /lib64/libpthread.so.0

#1 0x00007f97eb74196f in ?? () from /lib64/libglib-2.0.so.0

#2 0x00007f97eb6f9e27 in g_main_context_check () from /lib64/libglib-2.0.so.0

#3 0x00007f97eb6fa283 in ?? () from /lib64/libglib-2.0.so.0

#4 0x00007f97eb6fa413 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0

#5 0x00007f97ecdd6543 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /lib64/libQt5Core.so.5

#6 0x00007f97ecd8041b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5

#7 0x00007f97ecbd9745 in QThread::exec() () from /lib64/libQt5Core.so.5

#8 0x00007f97e2567f3b in ?? () from /lib64/libQt5DBus.so.5

#9 0x00007f97ecbda8a6 in ?? () from /lib64/libQt5Core.so.5

#10 0x00007f97ecb045a2 in start_thread () from /lib64/libpthread.so.0

#11 0x00007f97ec81e023 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f97e923fb40 (LWP 17000)):

[KCrash Handler]

#6 0x00007f97ede7be06 in XDefaultRootWindow () from /lib64/libX11.so.6

#7 0x0000558c213da1d5 in ?? ()

#8 0x0000558c213da4fd in ?? ()

#9 0x0000558c2141457b in ?? ()

#10 0x0000558c214a478b in ?? ()

#11 0x00007f97ecdab6ab in QMetaObject::activate(QObject*, int, int,
void**) () from /lib64/libQt5Core.so.5

#12 0x00007f97ecdb7e3b in QTimer::timeout(QTimer::QPrivateSignal) ()
from /lib64/libQt5Core.so.5

#13 0x00007f97ecdac495 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5

#14 0x00007f97ed89ec56 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /lib64/libQt5Widgets.so.5

#15 0x00007f97ed8a80a0 in QApplication::notify(QObject*, QEvent*) ()
from /lib64/libQt5Widgets.so.5

#16 0x00007f97ecd81428 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () from /lib64/libQt5Core.so.5

#17 0x00007f97ecdd5786 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5

#18 0x00007f97ecdd603c in ?? () from /lib64/libQt5Core.so.5

#19 0x00007f97eb6f9fd0 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0

#20 0x00007f97eb6fa368 in ?? () from /lib64/libglib-2.0.so.0

#21 0x00007f97eb6fa413 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0

#22 0x00007f97ecdd6524 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /lib64/libQt5Core.so.5

#23 0x00007f97ecd81619 in
QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>,
int) () from /lib64/libQt5Core.so.5

#24 0x0000558c21413d41 in ?? ()

#25 0x0000558c21416d25 in ?? ()

#26 0x0000558c21417510 in ?? ()

#27 0x0000558c21417e71 in ?? ()

#28 0x0000558c21418adc in ?? ()

#29 0x0000558c214a4b00 in ?? ()

#30 0x00007f97ecdab6ab in QMetaObject::activate(QObject*, int, int,
void**) () from /lib64/libQt5Core.so.5

#31 0x00007f97ecd0cb4e in
QProcess::readyReadStandardError(QProcess::QPrivateSignal) () from
/lib64/libQt5Core.so.5

#32 0x00007f97ecd12905 in ?? () from /lib64/libQt5Core.so.5

#33 0x00007f97ecd12d02 in ?? () from /lib64/libQt5Core.so.5

#34 0x00007f97ecdab6ab in QMetaObject::activate(QObject*, int, int,
void**) () from /lib64/libQt5Core.so.5

#35 0x00007f97ecdb790c in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5

#36 0x00007f97ecdb7c71 in QSocketNotifier::event(QEvent*) () from
/lib64/libQt5Core.so.5

#37 0x00007f97ed89ec56 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /lib64/libQt5Widgets.so.5

#38 0x00007f97ed8a80a0 in QApplication::notify(QObject*, QEvent*) ()
from /lib64/libQt5Widgets.so.5

#39 0x00007f97ecd81428 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () from /lib64/libQt5Core.so.5

#40 0x00007f97ecdd6e77 in ?? () from /lib64/libQt5Core.so.5

#41 0x00007f97eb6f9fd0 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0

#42 0x00007f97eb6fa368 in ?? () from /lib64/libglib-2.0.so.0

#43 0x00007f97eb6fa413 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0

#44 0x00007f97ecdd64b2 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /lib64/libQt5Core.so.5

#45 0x00007f97ecd8041b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5

#46 0x00007f97ecd88106 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5

#47 0x0000558c21476d5b in ?? ()

#48 0x0000558c214a3544 in ?? ()

#49 0x0000558c213a6eea in ?? ()

#50 0x00007f97ec746f33 in __libc_start_main () from /lib64/libc.so.6

#51 0x0000558c213a70de in ?? ()

[Inferior 1 (process 17000) detached]

On Fri, May 3, 2019 at 3:21 AM Ulrich Sibiller <uli42 at gmx.de> wrote:
>
> On Fri, May 3, 2019 at 2:22 AM Neal Becker <ndbecker2 at gmail.com> wrote:
> >
> > After updating to fedora 30, it looks like kde on wayland is working better.
> > So I tried firing up x2go, but on attempting to connect to a server
> > x2goclient crashed.
>
> Just to get this straight: You are not running a local X server but
> wayland? And do you just see the connection failing or does x2goclient
> vanish? Can you please describe your setup?
>
> Uli

--
Those who don't understand recursion are doomed to repeat it