Re: [aur-general] Moving xss-lock to community

On 2018-02-03 14:41:33 (+0100), Pierre Neidhardt wrote: > You are probably right about that. I think however that this should be > reported upstream to systemd rather than being part of the xss-lock > package. Hmm, I could find a (probably) related RFE [1]. [1]

Re: [aur-general] Moving xss-lock to community

David Runge writes: >> I'm no systemd expert: what is the intent of the suggest systemd unit? > This would only ensure, that lock already happens right before suspend > (in the case, someone wants that). > This use-case gets around the problem of showing a small portion of >

Re: [aur-general] Moving xss-lock to community

On 2018-02-03 14:00:29 (+0100), Pierre Neidhardt wrote: > As far as I can tell, xss-lock is already run when I resume from a > suspend. Ah lol... I was under the impression, that xss-lock would need to be told to lock. It seems loginctl sends out the 'lock-sessions' after waking up from suspend by

Re: [aur-general] Moving xss-lock to community

David Runge writes: > Could you also include a service file, that propagates the lock-sessions > command, in the vein of what was suggested upstream [1]? As far as I can tell, xss-lock is already run when I resume from a suspend. I'm no systemd expert: what is the intent of

Re: [aur-general] Moving xss-lock to community

Hi Pierre, On 2018-01-23 10:14:12 (+0100), Pierre Neidhardt via aur-general wrote: > No answer from the dev so far, so I've packaged the latest commit as Eli > suggested. > Let me know if there is anything wrong. nice to see this in [community]! Could you also include a service file, that

Re: [aur-general] Moving xss-lock to community

Eli Schwartz via aur-general writes: > source=("https://bitbucket.org/raymonad/xss-lock/get/${_commit}.tar.gz;) No answer from the dev so far, so I've packaged the latest commit as Eli suggested. Let me know if there is anything wrong. -- Pierre Neidhardt The time

Re: [aur-general] Moving xss-lock to community

Original Message On January 19, 2018 11:52 AM, David Runge wrote: >Fwitw (and sorry for hijacking), I recently tried xprintidle (with a forked >upstream, different from the one in the AUR) and it seems to work. > This might still be used in a script to lock

Re: [aur-general] Moving xss-lock to community

On January 19, 2018 9:42:26 AM GMT+01:00, Bennett Piater wrote: > > >On 01/18/2018 09:37 PM, Alad Wenter via aur-general wrote: >> See the bug report I linked in the first reply. >> >>

Re: [aur-general] Moving xss-lock to community

On 01/18/2018 09:37 PM, Alad Wenter via aur-general wrote: > See the bug report I linked in the first reply. > > https://bitbucket.org/raymonad/xss-lock/issues/17/does-not-report-activity-to-systemd-logind Right, that is actually something else than what I did. I used `xset s` to trigger on

Re: [aur-general] Moving xss-lock to community

On Thu, Jan 18, 2018 at 09:32:46PM +0100, Bennett Piater wrote: > > > On 01/18/2018 09:25 PM, Alad Wenter via aur-general wrote: > > On Thu, Jan 18, 2018 at 09:24:04PM +0100, Bennett Piater wrote: > > Except, as noted, that "major feature" doesn't work at all... > > Doesn't it? > It appeared to

Re: [aur-general] Moving xss-lock to community

On 01/18/2018 09:25 PM, Alad Wenter via aur-general wrote: > On Thu, Jan 18, 2018 at 09:24:04PM +0100, Bennett Piater wrote: > Except, as noted, that "major feature" doesn't work at all... Doesn't it? It appeared to work when I tried it, and that was this morning... Cheers, Bennett -- GPG

Re: [aur-general] Moving xss-lock to community

On Thu, Jan 18, 2018 at 09:24:04PM +0100, Bennett Piater wrote: > This doesn't take care of locking on inactivity though, which is the other > major feature of xss-lock. > That said, a short implementation may look as follows:

Re: [aur-general] Moving xss-lock to community

On Thu, Jan 18, 2018 at 09:24:04PM +0100, Bennett Piater wrote: > This doesn't take care of locking on inactivity though, which is the other > major feature of xss-lock. > Except, as noted, that "major feature" doesn't work at all... Alad signature.asc Description: PGP signature

Re: [aur-general] Moving xss-lock to community

This doesn't take care of locking on inactivity though, which is the other major feature of xss-lock. Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808

Re: [aur-general] Moving xss-lock to community

On Thu, Jan 18, 2018 at 08:52:23PM +0100, Pierre Neidhardt wrote: > > Alad Wenter via aur-general writes: > > > If you use polkit and acpid, a "simple" alternative is to use > > systemd-inhibit, and run actions based on acpid events. Not sure there's > > a ready

Re: [aur-general] Moving xss-lock to community

On 01/18/2018 03:02 PM, Pierre Neidhardt via aur-general wrote: > > It's only 4 commits since 0.3.0, two of them being critical fixes. > I could backport those two commits (just tried: no conflict); it feels > needlessly pedantic however, compared to using "master" straight away. > > I've

Re: [aur-general] Moving xss-lock to community

It's only 4 commits since 0.3.0, two of them being critical fixes. I could backport those two commits (just tried: no conflict); it feels needlessly pedantic however, compared to using "master" straight away. I've contacted the developer, see if he replies within a few days. If not, I'll go

Re: [aur-general] Moving xss-lock to community

Alad Wenter via aur-general writes: > If you use polkit and acpid, a "simple" alternative is to use > systemd-inhibit, and run actions based on acpid events. Not sure there's > a ready implementation with X support in mind. Could you detail this? How do you set it

Re: [aur-general] Moving xss-lock to community

On January 18, 2018 7:26:33 PM GMT+01:00, Pierre Neidhardt via aur-general wrote: > >The 100%-cpu issue should be fixed upstream on master (and thus also in >the -git package). >I've mentioned this on the wiki: > Why not simply backporting it via a patch file then?

Re: [aur-general] Moving xss-lock to community

On Thu, Jan 18, 2018 at 07:26:33PM +0100, Pierre Neidhardt wrote: > > The 100%-cpu issue should be fixed upstream on master (and thus also in the > -git package). > I've mentioned this on the wiki: > > https://wiki.archlinux.org/index.php/Power_management#xss-lock > Since that's a fairly

Re: [aur-general] Moving xss-lock to community

The 100%-cpu issue should be fixed upstream on master (and thus also in the -git package). I've mentioned this on the wiki: https://wiki.archlinux.org/index.php/Power_management#xss-lock I'll ask the author if he's still maintaining it. I might consider a fork otherwise. -- Pierre Neidhardt

Re: [aur-general] Moving xss-lock to community

On Tue, Jan 16, 2018 at 10:59:49AM +0100, Pierre Neidhardt via aur-general wrote: > > Seems fairly popular, plus it's useful to lock the screen on sleep > without systemd. I realize I'm somewhat late with this response, but upstream hasn't updated their project in years and the release has

[aur-general] Moving xss-lock to community

Seems fairly popular, plus it's useful to lock the screen on sleep without systemd. -- Pierre Neidhardt signature.asc Description: PGP signature