Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1154468
| From | Ian Campbell <ijc@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock) |
| Date | 2023-07-16 12:00 +0200 |
| Message-ID | <GS6HL-BGD-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <GQM8p-e9S-7@gated-at.bofh.it> <GQGml-aJP-7@gated-at.bofh.it> <GQM8p-e9S-5@gated-at.bofh.it> <GQGml-aJP-7@gated-at.bofh.it> <GQM8p-e9S-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Nikolaus,
Thanks for your report.
On Wed, 2023-07-12 at 18:38 +0100, Nikolaus Rath wrote:
> It seems that running xss-lock as `xss-lock --
> session=${XDG_SESSION_ID}` works around this problem.
That's correct, you either need a working logind session (which your
"Error getting session" suggests you either don't or you are launching
xss-lock in a way which doesn't find it properly) or you must use this
option to tell xss-lock the session.
I don't know enough about gnome-flashback to know if it is supposed to
have a working logind or not or how one should launch xss-lock to
properly use it if it does.
Ian.
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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