Bug 386521 - kmserver crashed when trying to login in after a logout
Summary: kmserver crashed when trying to login in after a logout
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.8.7
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-11-04 12:57 UTC by John Carrick Smith
Modified: 2018-09-28 16:55 UTC (History)
3 users (show)

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


Attachments
KDe generated crash report (10.67 KB, text/plain)
2017-11-04 12:57 UTC, John Carrick Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Carrick Smith 2017-11-04 12:57:22 UTC
Created attachment 108704 [details]
KDe generated crash report

The "Battery and Brightness" plasmoid had not appeared so I logged out of the session and back in again. Twice ksmserver crashed when trying to log in again. I created a bug report on the second occurrence but the crash handler refused to accept the crash with the message "0.4 is not a valid version".

Created this bug manually.
Comment 1 Christoph Feck 2017-11-08 20:22:48 UTC
Crashes in libpulse. To see the actual cause of the crash, please install the missing debug symbols, and add an updated backtrace.

For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thread 1 (Thread 0x7fc184dea940 (LWP 3311)):
[KCrash Handler]
#6  0x00007fc1846798d7 in raise () at /lib64/libc.so.6
#7  0x00007fc18467acaa in abort () at /lib64/libc.so.6
#8  0x00007fc1755f4f11 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#9  0x00007fc179e79a7c in  () at /usr/lib64/libpulse-mainloop-glib.so.0
#10 0x00007fc1789cb134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#11 0x00007fc1789cb388 in  () at /usr/lib64/libglib-2.0.so.0
#12 0x00007fc1789cb42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#13 0x00007fc17eccd18c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#14 0x00007fc17ec7abfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#15 0x00007fc17ec82ae6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#16 0x00007fc1849fb687 in kdemain () at /usr/lib64/libkdeinit5_ksmserver.so
#17 0x00007fc1846656e5 in __libc_start_main () at /lib64/libc.so.6
#18 0x0000000000400839 in _start ()
Comment 2 Andrew Crouthamel 2018-09-28 02:34:19 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 set the bug status 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 3 John Carrick Smith 2018-09-28 13:48:19 UTC
Currently unable to reproduce.
Comment 4 Andrew Crouthamel 2018-09-28 16:55:40 UTC
Ok, thanks for the update!