<table><tr><td style="">graesslin added inline comments.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D6004" rel="noreferrer">View Revision</a></tr></table><br /><div><strong>INLINE COMMENTS</strong><div><div style="margin: 6px 0 12px 0;"><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D6004#inline-25591" rel="noreferrer">View Inline</a><span style="color: #4b4d51; font-weight: bold;">tcberner</span> wrote in <span style="color: #4b4d51; font-weight: bold;">abstractlocker.cpp:62</span></div>
<div style="margin: 8px 0; padding: 0 12px; color: #74777D;"><p style="padding: 0; margin: 8px;">I'm not sure, if we can predictably get the name of the correct "broken" session from within the script -- of course, the script could just unlock all the sessions by iterating over them, but that seems rude. Maybe the error message <tt style="background: #ebebeb; font-size: 13px;">text</tt> could be modified to contain correct session name:</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">"# ck-unlock-session [the current session name]\n\n"</pre></div></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">That sounds reasonable and is what has been done for loginctl lately.</p></div></div><br /><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D6004#inline-25594" rel="noreferrer">View Inline</a><span style="color: #4b4d51; font-weight: bold;">tcberner</span> wrote in <span style="color: #4b4d51; font-weight: bold;">abstractlocker.cpp:67-70</span></div>
<div style="margin: 8px 0; padding: 0 12px; color: #74777D;"><p style="padding: 0; margin: 8px;">I think seeing this message annoys the users. So pointing them to possible solutions for future failures is a good thing, even when it might be a bit technical.</p></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">I doubt that. If the users see this message and don't have either consolekit or loginctl support either their distro messed things up or they compiled themselves and know what they are doing and have seen the cmake warnings. In both cases it doesn't really help to have this information then.</p></div></div></div></div></div><br /><div><strong>REPOSITORY</strong><div><div>R133 KScreenLocker</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D6004" rel="noreferrer">https://phabricator.kde.org/D6004</a></div></div><br /><div><strong>To: </strong>tcberner, FreeBSD, graesslin, Plasma<br /><strong>Cc: </strong>erichameleers, plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart, lukas<br /></div>