Bug 375152

Summary: Restart KWin when not loaded
Product: [Plasma] kwin Reporter: Matthias <shalokshalom>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: mahen, subdiff
Priority: NOR Keywords: triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: attachment-20815-0.html

Description Matthias 2017-01-16 18:51:48 UTC
Hi there :)

It happens sometimes to me, that KWin does not start, while Plasma does. 

Is it possible to check frequently, if KWin is running, and launch it, if not?

Like its already the case for Plasma?

Thanks a lot
Comment 1 Matthias 2017-01-16 19:30:27 UTC
Here some infos about my system, if that helps to detect the reason for the failed start process of KWin:

https://gist.github.com/ShalokShalom/b5427e7ea92add24c5e6ddeef9d83283
Comment 2 Martin Flöser 2017-01-16 20:17:43 UTC
There is neither a watchdog for KWin nor for Plasma. They get restarted on crash by the KCrash framework.

What exactly do you mean by "KWin does not start"? Did it crash?
Comment 3 Matthias 2017-01-19 12:49:11 UTC
Both - crash on running session and no start from the very beginning. 

This is confirmed by other users, including from other distros, as well. 

It happens rarely, what can i do the next time, when it happens?
Comment 4 Martin Flöser 2017-01-19 13:13:26 UTC
Created attachment 103531 [details]
attachment-20815-0.html

Get the backtrace of the crash so that we can fix the crash.
Comment 5 Matthias 2017-01-19 13:14:55 UTC
And when its not loaded in the first instance? 
On boot? Is it also then possible to get a backtrace?
Comment 6 Martin Flöser 2017-01-19 15:49:39 UTC
KCrash should always show a DrKonqi. Even on boot.
Comment 7 Matthias 2017-01-19 16:35:07 UTC
Ok, i guess its not a crash then
Comment 8 Mahendra Tallur 2017-01-29 10:36:25 UTC
I was about to ask the same question...

For some unknown reason, windows decorations have not been present after rebooting for a few days, which made me need to start kwin manually.

I don't know if it's a crash or something else.

I figured out this issue would stop occurring when disabling the session restoration at startup.

If that's a crash, it should have been restarted automatically. But if it wasn't a crash, why would my decoration reappear when starting kwin ?

I'll double check the bugs tracker to help identify this :)

[Using KDE Neon LTS]
Comment 9 Mahendra Tallur 2017-01-29 10:44:29 UTC
Anyway, I'll file a distinct bug as it seems unrelated. BTW, is there any additional package that needs to be installed under Neon ? I do not recall ever seing DrKonqi pop up and I did not find any package explicitely related to KDE & crashes under my package manager. (except apport-kde).

Cheers & Thanks so much Martin for your hard work ! Neon & Plasma LTS is a dream coming true :)
Comment 10 Mahendra Tallur 2017-01-30 08:06:55 UTC
I suspect this is the restoration of a specific app that causes this issue. As obviously enabling the automatic session restoration doesn't automatically causes the decorations to disappear at each startup. Trying to pinpoint this...
Comment 11 Martin Flöser 2017-07-22 12:50:08 UTC
Unfortunately we kind of lack information on what's going on here. KWin seems not to crash, but doesn't start. That's kind of impossible. Best idea I have is an issue created by the distribution.

For me there is nothing which can be done to further investigate. In case you have further information please reopen.
Comment 12 Matthias 2017-07-23 19:24:21 UTC
(In reply to Mahendra Tallur from comment #10)
> I suspect this is the restoration of a specific app that causes this issue.
> As obviously enabling the automatic session restoration doesn't
> automatically causes the decorations to disappear at each startup. Trying to
> pinpoint this...

This is pretty much possible, since i changed this to always start a new session (which is anyway the more senseful option) and i never got the issue again.
Comment 13 Andrew Crouthamel 2018-09-28 02:28:55 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 14 Andrew Crouthamel 2018-10-28 03:18:36 UTC
Dear Bug Submitter,

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!