Bug 351931

Summary: startkde should validate $KDEWM before using it
Product: [Unmaintained] ksmserver Reporter: Stefan Majewsky <majewsky>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED FIXED    
Severity: minor CC: bshah, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.2.90   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Stefan Majewsky 2015-08-29 10:35:52 UTC 
When a friend upgraded his notebook from Plasma 4 to 5, KWin did not start initially. It turned out that the problem was an "export KDEWM=kwin_gles" in his .profile; and that binary was gone with KWin 5.x

It would be nice if startkde would validate the existence of the executable given in $KDEWM before using it, so that such long-forgotten adjustments don't confuse other upgraders.

Reproducible: Always
Comment 1 David Edmundson 2015-08-30 00:38:41 UTC 
startkde simply sends it to ksmserver, I think ksmserver should do the validating based on whether  it can/can't launch the given app. Reassigning.
Comment 2 Nate Graham 2020-09-29 04:03:49 UTC 
None of this is relevant anymore, thankfully. :)