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

--- Comment #3 from DaveNull42 <daven...@tuxfamily.org> ---
I have a similar bug in Debian when I logous from a remote X2go session: Not
sure if it woks properly without X2Go since I don't have a physical access to
this computer

KDE version: kde-plasma-desktop 5:92
Operating System: Linux 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
Distribution: "Debian 9"

Here's the crash report for ksmserver

Application: ksmserver (ksmserver), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8aeaff8e00 (LWP 8622))]

Thread 2 (Thread 0x7f8ae3df5700 (LWP 8634)):
#0  0x00007f8af310e104 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f8af30c7ed0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8af30c891b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8af30c8b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8afa2d606b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f8afa27f9ca in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f8afa0ad0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f8aff56c6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x00007f8afa0b1da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f8af4ff9494 in start_thread (arg=0x7f8ae3df5700) at
pthread_create.c:333
#10 0x00007f8afeee3aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 1 (Thread 0x7f8aeaff8e00 (LWP 8622)):
[KCrash Handler]
#6  0x00007f8a00000001 in ?? ()
#7  0x00007f8ae33f053d in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeXcbPlugin0.so
#8  0x00007f8afee30910 in __run_exit_handlers (status=0, listp=0x7f8aff1945d8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:83
#9  0x00007f8afee3096a in __GI_exit (status=<optimized out>) at exit.c:105
#10 0x00007f8afee1b2b8 in __libc_start_main (main=0x5616afb96810 <main>,
argc=1, argv=0x7ffd50040ed8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffd50040ec8) at ../csu/libc-start.c:325
#11 0x00005616afb9684a in _start ()

Note : I runned also ksmserver from valgrind, the output is uploaded as an
attached file.

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

Reply via email to