Bug 356614 - ksmserver crashes after unlocking screens
Summary: ksmserver crashes after unlocking screens
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-13 17:17 UTC by Gordon Robert Speirs
Modified: 2018-11-01 18:41 UTC (History)
2 users (show)

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


Attachments
kcrash data (3.07 KB, text/plain)
2015-12-13 17:17 UTC, Gordon Robert Speirs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Robert Speirs 2015-12-13 17:17:26 UTC
Created attachment 96040 [details]
kcrash data

kinit5 crashed after the screens were unlocked. 

libxcb version is 1.11.1-1.1 (from opensuse tumbleweed packages)
Qt version is 5.5.1

Unable to provide more information other than attachment due to the following bug: https://bugs.kde.org/show_bug.cgi?id=335932

I went through the journal as well as the X logs and there was no indications that anything went wrong.
Comment 1 Andrew Crouthamel 2018-11-01 13:49:39 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Gordon Robert Speirs 2018-11-01 16:45:46 UTC
(In reply to Andrew Crouthamel from comment #1)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!

Unable to reproduce and has not been an issue for quite a while. This bug can likely be closed.
Comment 3 Andrew Crouthamel 2018-11-01 18:41:39 UTC
Thanks for the update!