Bug 384579 - KDE crashes and seems to blame ksmserver.
Summary: KDE crashes and seems to blame ksmserver.
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.6.2
Platform: Mageia RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-11 01:27 UTC by Mark Adams
Modified: 2021-01-16 04:36 UTC (History)
2 users (show)

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


Attachments
Crash Reporting Assistant fail (30.74 KB, image/png)
2017-09-11 01:27 UTC, Mark Adams
Details
valgrind output for ksmserver (68.01 KB, text/x-log)
2017-11-21 15:18 UTC, DaveNull42
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Adams 2017-09-11 01:27:31 UTC
Created attachment 107791 [details]
Crash Reporting Assistant fail

The Crash Reporting Assistant was unable to file this bug:
Error sending the crash report: /Received unexpected error code 320000 from bugzilla.  Error message was: The version value '0.4' is not active../

The contents of the report were: 

Application: ksmserver (ksmserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbb85894840 (LWP 3332))]

Thread 2 (Thread 0x7fbb7adb9700 (LWP 3342)):
#0  0x00007fbb97da100d in poll () from /lib64/libc.so.6
#1  0x00007fbb8d356c94 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#2  0x00007fbb8d356d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007fbb931a4e2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#4  0x00007fbb9315049a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#5  0x00007fbb92f8a3bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x00007fbb98438635 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5
#7  0x00007fbb92f8eff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#8  0x00007fbb8dee866d in start_thread () from /lib64/libpthread.so.0
#9  0x00007fbb97dace4d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fbb85894840 (LWP 3332)):
[KCrash Handler]
#4  0x00007fbb9744541b in _IceTransAccept () from /lib64/libICE.so.6
#5  0x00007fbb974403ad in IceAcceptConnection () from /lib64/libICE.so.6
#6  0x00007fbb9807d33b in KSMServer::newConnection(int) () from /lib64/libkdeinit5_ksmserver.so
#7  0x00007fbb9317d90c in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#8  0x00007fbb931f4c9e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#9  0x00007fbb931892eb in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007fbb93a64d0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007fbb93a69e76 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007fbb93152628 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007fbb931a52ad in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#14 0x00007fbb8d356ac7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#15 0x00007fbb8d356cf8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#16 0x00007fbb8d356d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#17 0x00007fbb931a4e06 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#18 0x00007fbb9315049a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007fbb931587e1 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#20 0x00007fbb9807c5d9 in kdemain () from /lib64/libkdeinit5_ksmserver.so
#21 0x00007fbb97cd7600 in __libc_start_main () from /lib64/libc.so.6
#22 0x0000000000400769 in _start ()
Comment 1 Mark Adams 2017-09-11 01:29:51 UTC
For some reason this information never made it into the bug report:

Application: ksmserver (0.4)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.43-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
It varies. Seems to happen at random. 

- Unusual behavior I noticed:
I'm working along doing whatever - browsing the web, editing a photo with the Gimp, literally whatever - and kde just siezes up. I generally go to another tty, killall Xorg and get logged back in. When I get back to the desktop, a "KSM server has crashed" dialog box shows up. I click "Okay" or whatever to clear it, the desktop then immediately reloads and I'm good to go until the next crash.

I've reinstalled the OS (Linux spike 4.9.43-desktop-1.mga6 #1 SMP Sun Aug 13 15:52:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) and it didn't resolve the issue.  I'm starting to suspect maybe a bad motherboard(?).  Google isn't helping me with this one. Below is backtrace info.
Comment 2 DaveNull42 2017-11-21 15:18:44 UTC
Created attachment 108995 [details]
valgrind output for ksmserver
Comment 3 DaveNull42 2017-11-21 15:19:44 UTC
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.
Comment 4 Justin Zobel 2020-12-17 05:32:38 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 5 Bug Janitor Service 2021-01-01 04:37:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-01-16 04:36:23 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!