Groups > linux.debian.bugs.dist > #1154476

Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock)

From	Ian Campbell <ijc@debian.org>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock)
Date	2023-07-16 13:20 +0200
Message-ID	<GS7Xb-CCi-9@gated-at.bofh.it> (permalink)
References	(4 earlier) <GS6HL-BGD-3@gated-at.bofh.it> <GQGml-aJP-7@gated-at.bofh.it> <GS7Xb-CCi-11@gated-at.bofh.it> <GQGml-aJP-7@gated-at.bofh.it> <GS7Xb-CCi-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sun, 2023-07-16 at 10:58 +0100, Nikolaus Rath wrote:
> If not, can you tell me how to test for it?

xss-lock uses dbus to talk to logind, specifically the service
org.freedesktop.login1, path /org/freedesktop/login1, via the
GetSessionByPID method of the org.freedesktop.login1.Manager interface,
I think what it does is equivalent to:

    dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.GetSessionByPID uint32:$$

The result for me is: object path /org/freedesktop/login1/session/_39

I'm afraid that is the limit of my knowledge of this stuff.

I can say that xss-lock works find, without any --session, when
launched directly from my .i3/config with i3's `exec`. Depending
how/where you are launching xss-lock it may not see the same envvars,
dbus setup etc as you see from the CLI.

Ian.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#1040917: xss-lock: Crashes after unlock Nikolaus Rath <Nikolaus@rath.org> - 2023-07-12 13:40 +0200
  Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock) "Nikolaus Rath" <nikolaus@rath.org> - 2023-07-12 19:50 +0200
    Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock) Ian Campbell <ijc@debian.org> - 2023-07-16 12:00 +0200
  Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock) Ian Campbell <ijc@debian.org> - 2023-07-16 13:20 +0200

csiph-web