Le 28/12/2017 à 15:31, Didier Kryn a écrit :
The files listed below are all part of package acpi-support.
/etc/acpi/events/lidbtn causes the invocation of /etc/acpi/lid.sh
on lid events
/etc/acpi/lid/sh invokes a function called CheckPolicy(), which is
in file /usr/share/acpi-support
On Friday 29 December 2017 at 10:44:16, Didier Kryn wrote:
> Found a simple solution to suspend on lid close:
>
> 1) uninstall xfce4-power-manager (probably true with power-managers
> from other DEs). It doesn't work and it prevents the default acpi
> methods to be called.
>
> 2)
1. I converted the Clearlooks-Phenix-Purpy theme from jessie to ascii
to replace the broken jessie version currently in ascii repos.
2. The openbox theme for Clearlooks-Phenix-DarkPurpy has been
completed. I would appreciate if some of you OB users could please test
it. The attached file is
Am 2017-12-29 10:50, schrieb Antony Stone:
Did the machine wake up again on opening the lid under Debian Wheezy or
did
you have to operate the power button there as well?
This sounds like a hardware feature of the particular laptop to me.
My observation is also, that waking up through openin
Le 29/12/2017 à 10:44, Didier Kryn a écrit :
Found a simple solution to suspend on lid close:
1) uninstall xfce4-power-manager (probably true with
power-managers from other DEs). It doesn't work and it prevents the
default acpi methods to be called.
2) edit /etc/default/acpi-sup
Am 2017-12-29 12:27, schrieb Didier Kryn:
Actualy xscreensaver also prevents the suspend. I didn't notice
the first time because it seems to take a logout-login before the
presence of the daemon to be noticed.
There is a hackish workaround: comment the following 3 lines in
/etc/acpi/lid.
Le 29/12/2017 à 12:35, J. Fahrner a écrit :
Am 2017-12-29 12:27, schrieb Didier Kryn:
Actualy xscreensaver also prevents the suspend. I didn't notice
the first time because it seems to take a logout-login before the
presence of the daemon to be noticed.
There is a hackish workaround: co
Am 2017-12-29 15:35, schrieb Didier Kryn:
Sure, but it comes just naked with essentially the right-click to
offer you to open a terminal emulator. That's not a very productive
way of working, compared to xfce4's panel.
You don't need to start with only X11 and xterm. Use openbox, tint2,
sp
On 29/12/17 13:57, Rick Moen wrote:
> One can also reasonably say that the ext2/ext3/ext4 codebase has
> benefited from more real-world testing than any other *ix fileystem code
> in history. (ext4 departs significantly more from ext3 than the latter
> did from ext2, as detailed here:
> https://
On 2017-12-29 04:05, J. Fahrner wrote:
Am 2017-12-29 11:02, schrieb goli...@dyne.org:
2. The openbox theme for Clearlooks-Phenix-DarkPurpy has been
completed. I would appreciate if some of you OB users could please
test it. The attached file is compatible with both
Clearlooks-Phenix-Purpy and
On Thu, Dec 28, 2017 at 08:41:13PM -0500, Steve Litt wrote:
> On Fri, 29 Dec 2017 01:15:10 +0100
> Harald Arnesen wrote:
>
> > I see what you mean, and I have never had a problem with ext4 either.
> > But I have used btrfs on all my main machines for the last years, and
> > have not had any (file
On 2017-12-29 04:02, goli...@dyne.org wrote:
1. I converted the Clearlooks-Phenix-Purpy theme from jessie to ascii
to replace the broken jessie version currently in ascii repos.
2. The openbox theme for Clearlooks-Phenix-DarkPurpy has been
completed. I would appreciate if some of you OB users
Quoting Adam Borowski (kilob...@angband.pl):
[enabling metadata checksums on relatively old ext4 filesystems:]
> Thus, if you created your filesystem with mkfs.ext4 older than
> stretch/ascii, it's vital that you do the following, on an unmounted
> filesystem (ie, need to boot from alternate medi
13 matches
Mail list logo
