Bug 351931 - startkde should validate $KDEWM before using it
Summary: startkde should validate $KDEWM before using it
Status: RESOLVED FIXED
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: 5.2.90
Platform: Other Other
: NOR minor
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-29 10:35 UTC by Stefan Majewsky
Modified: 2020-09-29 04:03 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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. :)