Hi there,
Maybe I'm being hopelessly naive, but is there any value in tying
ssh-agent to X11/Wayland or trying to make it behave like a session
service (as opposed to a user service), or having this "agent-launch"
init script at all?
Personally, I've been using a systemd "global" user unit to
Control: severity -1 minor
I consider this bug pretty minor since X11 stuff is going to be
installed for quite some time on Debian's Wayland based desktops, so
don't spend too much effort on this right now.
On Sat, 2020-05-23 at 15:57 +0100, Colin Watson wrote:
> My concern about that is that
On Sat, May 23, 2020 at 08:18:55PM +0800, Paul Wise wrote:
> On Sat, 2020-05-23 at 13:07 +0100, Colin Watson wrote:
> > What do you think?
>
> I don't think that will work because neither of the DISPLAY nor
> WAYLAND_DISPLAY environment variables are set for user services since
> they are user
On Sat, 2020-05-23 at 13:07 +0100, Colin Watson wrote:
> What do you think?
I don't think that will work because neither of the DISPLAY nor
WAYLAND_DISPLAY environment variables are set for user services since
they are user services *not* session services and systemd does not
support session
On Sat, May 23, 2020 at 09:45:55AM +0800, Paul Wise wrote:
> On pure-Wayland systems, the ssh-agent.service is not going to be able
> to start because x11-common won't nessecarily be installed. I think
> either the ConditionPathExists should get dropped and the script should
> check if the
Package: openssh-client
Version: 1:8.2p1-4
Severity: normal
File: /usr/lib/systemd/user/ssh-agent.service
Usertags: wayland
On pure-Wayland systems, the ssh-agent.service is not going to be able
to start because x11-common won't nessecarily be installed. I think
either the ConditionPathExists
6 matches
Mail list logo
