On 25/06/19 3:46 AM, Michael Biebl wrote:
>> Why is there no "the graphical session is ready"
>> systemd target?
> There is, incidentally it is named graphical-session.target :-)
> See man systemd.special
>
> Unfortunately, no display/session manager is hooked up yet to manage the
> lifetime of
Hi
> Why is there no "the graphical session is ready"
> systemd target?
There is, incidentally it is named graphical-session.target :-)
See man systemd.special
Unfortunately, no display/session manager is hooked up yet to manage the
lifetime of that target, so you can't make use of that target
On 21/06/19 8:33 PM, Jonathan Dowland wrote:
> On Fri, Jun 21, 2019 at 06:50:14PM +1200, Aidan Gauland wrote:
>> Someone else suggested running xautolock from my .xsessionrc script so
>> that it is always run after X is running, and that seems to work. I
>> wanted to run this via systemd because
On 21/06/19 7:24 PM, john doe wrote:
> Is it always working if you run the command manually?
It has so far, yes.
On Fri, Jun 21, 2019 at 06:50:14PM +1200, Aidan Gauland wrote:
Someone else suggested running xautolock from my .xsessionrc script so
that it is always run after X is running, and that seems to work. I
wanted to run this via systemd because that's easier to restart after
making tweaks than
On 6/21/2019 8:50 AM, Aidan Gauland wrote:
> On 21/06/19 6:25 PM, Ansgar Burchardt wrote:
>> Aidan Gauland writes:
>>> I have a user service for running xautolock that does not start on login
>>> reliably, and I have no idea why, because there is no error message,
>>> just an exit code of 1.
On 21/06/19 6:25 PM, Ansgar Burchardt wrote:
> Aidan Gauland writes:
>> I have a user service for running xautolock that does not start on login
>> reliably, and I have no idea why, because there is no error message,
>> just an exit code of 1. (Unit file and output of systemctl status
>>
Aidan Gauland writes:
> I have a user service for running xautolock that does not start on login
> reliably, and I have no idea why, because there is no error message,
> just an exit code of 1. (Unit file and output of systemctl status
> attached.) Any suggestions on what to do next to
I have a user service for running xautolock that does not start on login
reliably, and I have no idea why, because there is no error message,
just an exit code of 1. (Unit file and output of systemctl status
attached.) Any suggestions on what to do next to troubleshoot this?
Regards,
Aidan
9 matches
Mail list logo
