A bit more info. It appears that the sequence of events may be the
following:
I lock the screen from the keyboard. That key is bound to i3lock --dpms
--inactivity-timeout 10 --color=220022 .
A bit later, xautolock decides to lock the screen as well. That command,
by chance, is not quite the
Good idea, thanks, I'll bind my lock key to that. I think I learned of
xautolock after learning that I could lock the screen by binding i3lock to
a key.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255-- only if I'm in the UK
http://jeff.purple.com/
http://blog.purple.com/jeff/
On 1 May
On 1 May 2015 at 17:40, Jeff Abrahamson j...@purple.com wrote:
I lock the screen from the keyboard. That key is bound to i3lock --dpms
--inactivity-timeout 10 --color=220022 .
If you use xautolock, better trigger a lock through it then, I use the
Pause button to lock it like this:
Sure thing.
Just to be clear, do you mean that instead of launching i3lock .. I
substitute strace -o/tmp/i3lock-log-$(date +%s) i3lock ...?
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255-- only if I'm in the UK
http://jeff.purple.com/
http://blog.purple.com/jeff/
On 17 April 2015 at
Interesting. How does setuid have this effect on i3lock but only under
strace?
Any idea where the setuid is coming from or how to find out? The system is
pretty vanilla ubuntu 14.10 (they have a good installer) aside from running
i3 instead of gnome.
The exec path that's visible once I'm
Yes, but also use -f (to follow child processes) and -s 2048 (to increase
the size of strings) and -tt (to get timing).
On Fri, Apr 17, 2015 at 9:23 AM, Jeff Abrahamson j...@purple.com wrote:
Sure thing.
Just to be clear, do you mean that instead of launching i3lock .. I
substitute strace
Ugh, then you’re running it in a setuid setup. You’ll need to start i3lock
and then attach strace afterwards using -p.
On Fri, Apr 17, 2015 at 9:56 AM, Jeff Abrahamson j...@purple.com wrote:
I invoke i3lock at the commandline thus:
[S-18]jeff@siegfried:gtd $ strace -o/tmp/i3lock-log-$(date
See http://superuser.com/a/248127 for why setuid is ignored when
running under strace.
Given that you run i3lock on linux, it might be PAM which uses setuid
in some of its modules.
On Fri, Apr 17, 2015 at 1:20 AM, Jeff Abrahamson j...@purple.com wrote:
Interesting. How does setuid have this
Thanks. I understand (and a bit better, now) why strace/ptrace may have
problems with a program that calls setuid. On the other hand, i3lock
doesn't have the setuid bit set, and the strace logs do not show an attempt
to call strace.
[S-18]jeff@siegfried:~ $ stat /usr/bin/i3lock
File:
I invoke i3lock at the commandline thus:
[S-18]jeff@siegfried:gtd $ strace -o/tmp/i3lock-log-$(date +%s) -f -s 2048
-tt i3lock --dpms --inactivity-timeout 10 --color=220022
[S-18]jeff@siegfried:gtd $
and the result is that i3lock does not recognize my password. It does echo
my typing, it just
10 matches
Mail list logo
