On 26.03.2015 08:21, Lennart Poettering wrote:
On Wed, 25.03.15 13:03, poma (pomidorabelisima(a)gmail.com) wrote:
> On 23.03.2015 05:25, Lennart Poettering wrote:
>> On Tue, 17.03.15 14:11, poma (pomidorabelisima(a)gmail.com) wrote:
>>
>>> On 17.03.2015 13:08, poma wrote:
>>>> On 17.03.2015 11:56, Olav Vitters wrote:
>>>>> On Tue, Mar 17, 2015 at 08:08:04AM +0100, Niels Weber wrote:
>>>>>> Is there any way that I missed so far? Or is it simply not
possible?
>>>>>
>>>>> Please try:
>>>>> $ loginctl list-sessions
>>>>> $ loginctl lock-session $ID
>>>>> $ loginctl unlock-session $ID
>>>>>
>>>>>
>>>>
>>>> Does it work for you?
>>>>
>>>>
>>>
>>> Mister Lennart, can we expect in the near future to be feasible?
>>>
>>> $ /usr/lib/systemd/systemd --version
>>> systemd 219
>>
>> Sorry, but I miss the context. What are you asking for?
>>
>> Lennart
>>
>
> Exactly, content is missing, "loginctl un/lock-session $ID" is doing
nothing, only placeholding, waiting for Baobab.
> ;)
Maybe your desktop environment does not listen to the logind signals
for locking/unlocking? GNOME does, not sure about others.
Lennart
This is a good idea to RFE.
Thanks for answering.