https://bugs.kde.org/show_bug.cgi?id=484878
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=484878
zvova7...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=484878
Bug Janitor Service changed:
What|Removed |Added
Resolution|BACKTRACE |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=484878
--- Comment #4 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=484878
--- Comment #3 from zvova7...@gmail.com ---
Important note: When you navigate to Kickoff -> sleep, and then after wakeup
Kickoff is still showing - there's no crash. However, if Kickoff has
disappeared, a protocol error occurs, leading to _exit(-1) in
https://bugs.kde.org/show_bug.cgi?id=484878
--- Comment #2 from zvova7...@gmail.com ---
I assume this won't help because the compositor simply raises the error, which
the client receives, prints, and then exit(). But if you sure that I'm wrong
I'll do breakpoint on the exit function and take the
https://bugs.kde.org/show_bug.cgi?id=484878
Marco Martin changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=484878
Bug Janitor Service changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail
