On Wed, Aug 21, 2019 at 03:52:23PM +0200, Thorsten Glaser wrote:
> On Wed, 21 Aug 2019, Mark Hindley wrote:
>
> > You need xss-lock to join logind to xscreensaver:
> >
> > xss-lock -- xscreensaver-command -lock &
> > loginctl lock-session
> >
> > Does that work for lid events too?
>
>
On Wed, 21 Aug 2019, Mark Hindley wrote:
> You need xss-lock to join logind to xscreensaver:
>
> xss-lock -- xscreensaver-command -lock &
> loginctl lock-session
>
> Does that work for lid events too?
/bin/mksh: xss-lock: inaccessible or not found
With the ACPI tools the mere existence of
On Wed, Aug 21, 2019 at 12:36:48PM +0100, Mark Hindley wrote:
> On Tue, Aug 20, 2019 at 11:19:30PM +0200, Thorsten Glaser wrote:
> > >I think you might need
> > >
> > >HandleLidSwitch=lock
> > >
> > >in /etc/elogind/logind.conf for that behaviour.
> >
> > I’ve made a few adjustments following
On Tue, Aug 20, 2019 at 11:19:30PM +0200, Thorsten Glaser wrote:
> >I think you might need
> >
> >HandleLidSwitch=lock
> >
> >in /etc/elogind/logind.conf for that behaviour.
>
> I’ve made a few adjustments following that suggestion (see
> below), dist-upgraded sid to ensure I’ve got the latest
>
Package: elogind
Version: 241.3-1+debian1
Followup-For: Bug #919694
Mark Hindley wrote:
>I think you might need
>
>HandleLidSwitch=lock
>
>in /etc/elogind/logind.conf for that behaviour.
I’ve made a few adjustments following that suggestion (see
below), dist-upgraded sid to ensure I’ve got the
On Mon, Aug 19, 2019 at 11:14:35PM +, Thorsten Glaser wrote:
> My laptop also doesn’t lock the screen any more when I close it.
> This used to work at least while X11 is running (it started
> xlock -mode blank), now it works neither when logged in on the
> text (framebugger) console nor under
Dixi quod…
>I just ran into this myself. Why is this still unfixed?
>Freezing the laptop(’s playing music) just because I close it
>is utterly inacceptable as a default setting.
My laptop also doesn’t lock the screen any more when I close it.
This used to work at least while X11 is running (it
Package: elogind
Version: 241.3-1+debian1
Followup-For: Bug #919694
I just ran into this myself. Why is this still unfixed?
Freezing the laptop(’s playing music) just because I close it
is utterly inacceptable as a default setting.
See below for a change to /etc/elogind/logind.conf which,
after
On Wed, Mar 20, 2019 at 01:37:50PM +, Mark Hindley wrote:
> Tags: moreinfo
>
> On Sat, Jan 19, 2019 at 10:34:02AM +, Mark Hindley wrote:
> > One issue I will pass upstream is why the Docked status is taking so long to
> > update. Once docked elogind should be ignoring lid events by
Tags: moreinfo
On Sat, Jan 19, 2019 at 10:34:02AM +, Mark Hindley wrote:
> One issue I will pass upstream is why the Docked status is taking so long to
> update. Once docked elogind should be ignoring lid events by default. (I know
> this doesn't address the underlying issue in this case, but
> So I think this aspect of this bug should be reassigned to acpi-
> support. I will
> try and prepare a patch and then clone the bug. acpi-support
> maintainers, are
> you OK with that?
Sure. Thanks.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
On Sat, Jan 19, 2019 at 10:34:02AM +, Mark Hindley wrote:
> > I'd expect systemd and acpi-support to conflict for the same reason,
> > but they don't. Maybe the problem is solved there in a different way?
> > Or maybe installing systemd on a machine with previously configured
> > acpi-support
On Sat, Jan 19, 2019 at 12:06:14PM +0100, KatolaZ wrote:
> My impression is that making elogind Conflict: with acpi-support is
> irrelevant for most elogind users, and a potential source of breakage
> for acpi-support users. A typical loss-loss case, IMHO.
>
> Users should be warned of potential
On Sat, Jan 19, 2019 at 10:34:02AM +, Mark Hindley wrote:
[cut]
> >
> > That seems unfortunate as the two packages are not exact functional
> > replacements of each other, but it would solve this particular problem.
>
> Yes I agree, but I cannot see a way for elogind to tell if another
Tags: upstream
On Fri, Jan 18, 2019 at 04:58:22PM -0500, Zygo Blaxell wrote:
> > > I encountered a similar problem on another laptop some months ago, where
> > > that laptop's lid switch was always reporting closed. That system was
> > > running systemd, and the fix was to set
On Fri, Jan 18, 2019 at 09:27:27PM +, Mark Hindley wrote:
> On Fri, Jan 18, 2019 at 03:19:11PM -0500, Zygo Blaxell wrote:
> > I get:
>
> [snipped]
>
> > HandleLidSwitch=suspend
> > HandleLidSwitchDocked=ignore
> > Docked=yes
>
> > It seems there is some significant lag
On Fri, Jan 18, 2019 at 03:19:11PM -0500, Zygo Blaxell wrote:
> I get:
[snipped]
> HandleLidSwitch=suspend
> HandleLidSwitchDocked=ignore
> Docked=yes
> It seems there is some significant lag (several seconds, maybe a minute
> or two) before "Docked" changes to the correct
On Fri, Jan 18, 2019 at 05:00:19PM +, Mark Hindley wrote:
> On Fri, Jan 18, 2019 at 11:18:27AM -0500, Zygo Blaxell wrote:
> > Source: elogind
> > Version: 239.3-4+debian1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I installed elogind on a laptop because it was a dependency of
On Fri, Jan 18, 2019 at 11:18:27AM -0500, Zygo Blaxell wrote:
> Source: elogind
> Version: 239.3-4+debian1
> Severity: important
>
> Dear Maintainer,
>
> I installed elogind on a laptop because it was a dependency of other
> packages. When I attempted to use the laptop in a docking station
>
Source: elogind
Version: 239.3-4+debian1
Severity: important
Dear Maintainer,
I installed elogind on a laptop because it was a dependency of other
packages. When I attempted to use the laptop in a docking station
with the lid closed, it immediately and repeatedly went into suspend,
despite my
20 matches
Mail list logo
