Palo Kisa

Actually there is (undocumented?) option to provide user defined actions to trigger each of the "power actions": ```c++ bool CustomProvider::canAction(Power::Action action) const { switch (action) { case Power::PowerShutdown: return mSettings.contains("shutdownCommand");...

Please, what is the reason to not use the Qt's facility for regular expressions and do this std qt translations?

> using QRegularExpression adds yet another external dependency What additional dependency are you referring to? It is in Qt core, isn't it?

> Sorry, at this point I am very confused. You're confusing us. There is no additional dependency needed for using Qt regular expressions -> see the PR for your code.

@wxl This is just a blind guess, but can you give lxqt/lxqt-policykit#106 a try? It may help.

Hm... actually the PR may definitely help... as in the polkitqt1's Session destructor: ```cpp Session::~Session() { if (d->polkitAgentSession) g_object_unref(d->polkitAgentSession); delete d; } ``` and in the code after emitting `completed`...

We have few options here I can imagine now: 1. create a specific whitelist/regexp configuration of app names in session configuration 2. in lxqt-session examine some flag of the process...

This window is shown, if currently configured WM [is not found](https://github.com/lxqt/lxqt-session/blob/master/lxqt-session/src/lxqtmodman.cpp#L193): ```c++ // If previuos WM was removed, we show dialog. if (mWindowManager.isEmpty() || ! findProgram(mWindowManager.split(QL1C(' '))[0])) { mWindowManager =...

> Apparently, it should never happen. Why has it been reported several times? IMO when the user removes all "known" window managers w/o setting some existing into `lxqt-config-session`

Or there is a problem in the logic for checking if the window manager (its executable) is present...