Upload on its way, thanks an awful lot for your help.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers!
On Sat, Nov 08, 2014 at 05:45:08PM +0100, Michael Meskes wrote:
> On Sat, Nov 08, 2014 at 08:08:04AM -0800, Josh Triplett wrote:
> > acpid does not contain any files in /etc/acpi/events/ by default. (Just
> > checked in the latest version of acpid, 1:2.0.23-1.)
>
> You are absolutely right of cou
On Sat, Nov 08, 2014 at 08:08:04AM -0800, Josh Triplett wrote:
> acpid does not contain any files in /etc/acpi/events/ by default. (Just
> checked in the latest version of acpid, 1:2.0.23-1.)
You are absolutely right of course. And I guess I, as the maintainer of both of
these source packages, lo
On Sat, Nov 08, 2014 at 04:43:41PM +0100, Michael Meskes wrote:
> On Wed, Nov 05, 2014 at 06:36:47AM -0800, Josh Triplett wrote:
> > If acpid needs to run to manage scripts in /etc/acpi/events/, then in
> > addition to the acpid.socket file, you should also ship an acpid.path
> > file, containing:
Am 08.11.2014 um 16:41 schrieb Michael Meskes:
> On Wed, Nov 05, 2014 at 02:04:29PM +0100, Michael Biebl wrote:
>> That's a decision that's up to the maintainer.
>
> Thanks for the explanation. That change in question was provided as a patch
> back in the day and to the day I hadn't even noticed t
On Wed, Nov 05, 2014 at 02:04:29PM +0100, Michael Biebl wrote:
> That's a decision that's up to the maintainer.
Thanks for the explanation. That change in question was provided as a patch
back in the day and to the day I hadn't even noticed that acpid wasn't running.
Michael
--
Michael Meskes
Mi
On Wed, Nov 05, 2014 at 06:36:47AM -0800, Josh Triplett wrote:
> If acpid needs to run to manage scripts in /etc/acpi/events/, then in
> addition to the acpid.socket file, you should also ship an acpid.path
> file, containing:
>
> [Path]
> ConditionDirectoryNotEmpty=/etc/acpi/events/
>
> [Install
Hi Michael
> b/ acpid's internal event processing which calls (shell) scripts on
> certain events which are defined in /etc/acpi/.
Yes, that one.
> I assume Norbert is using acpid in mode b/, so what he noticed was, that
> his shell scripts in /etc/acpi/ were not processed as he apparently
> do
On Wed, 05 Nov 2014 14:52:27 +0100 Michael Biebl wrote:
> Am 05.11.2014 um 14:25 schrieb Norbert Preining:
> > Hi TEd, hi Michael (Meskes),
> >
> >> override_dh_systemd_enable:
> >>dh_systemd_enable --no-enable debian/acpid.service
> >>dh_systemd_enable debian/acpid.socket
> >
>
Am 05.11.2014 um 14:25 schrieb Norbert Preining:
> Hi TEd, hi Michael (Meskes),
>
>> override_dh_systemd_enable:
>>dh_systemd_enable --no-enable debian/acpid.service
>>dh_systemd_enable debian/acpid.socket
>
> That --no-enable should probably removed in the rules file.
> There are
Hi TEd, hi Michael (Meskes),
> override_dh_systemd_enable:
>dh_systemd_enable --no-enable debian/acpid.service
>dh_systemd_enable debian/acpid.socket
That --no-enable should probably removed in the rules file.
There are more kernel modules out there (thinkpad?...) that
send acpi e
Am 05.11.2014 um 13:02 schrieb Norbert Preining:
> On Wed, 05 Nov 2014, Michael Biebl wrote:
>> A "systemctl enable systemd.service" will hook up acpid.service in
>
> acpid.service I guess. Yes, but how is that to be incorporated into
> the dpkg scripts?
>
> Does systemd provide any mechanism for
On Wed, 05 Nov 2014, Michael Biebl wrote:
> A "systemctl enable systemd.service" will hook up acpid.service in
acpid.service I guess. Yes, but how is that to be incorporated into
the dpkg scripts?
Does systemd provide any mechanism for that? When and how should
the script be run? On every postins
Hi Michael,
On Tue, 04 Nov 2014, Michael Meskes wrote:
> Unfortunately I do not know much about the way systemd works, either. In
> particular I wonder how that event you generate makes it to acpid (when it is
> running) but does not trigger a start. Anyone with a hint?
Yes. The event is generat
Am 05.11.2014 um 12:01 schrieb Michael Biebl:
> A "systemctl enable systemd.service" will hook up acpid.service in
I was just pointed at, that I probably wanted to say
"systemctl enable acpid.service" here :-)
--
Why is it that all of the instruments seeking intelligent life in the
universe a
Am 04.11.2014 um 17:04 schrieb Michael Meskes:
> On Tue, Oct 28, 2014 at 10:02:26AM +0900, Norbert Preining wrote:
>> But the point is that there are events generated from kbd that are
>> not coming over the socket, and thus are completely lost.
>
> The service file was provided by a member of the
On Tue, Oct 28, 2014 at 10:02:26AM +0900, Norbert Preining wrote:
> But the point is that there are events generated from kbd that are
> not coming over the socket, and thus are completely lost.
The service file was provided by a member of the systemd team IIRC.
Unfortunately I do not know much ab
Hi Ted, hi Systemd maintainers
SHort description for systemd maintainers: acpid seems not to be
started anymore automatically, thus custom events defined in
/etc/acpid/... are not processed anymore. In my case the touchpad
toggle key is a specific event and I have written an action that
should ac
On 10/27/2014 09:05 AM, Norbert Preining wrote:
The reason is that acpid is not started automatically anymore, but
some systemd tells me that something about socket activation etc.
I've not used systemd yet, but I'm pretty sure acpid works fine when
the socket is sent in as the stdin fd (or
Package: acpid
Version: 1:2.0.23-1
Severity: important
Hi everyone,
it seems with some of the systemd integration, features of acpid
are getting list.
What I see on my computer, a sony laptop, where I have a custom
event declared (sony touchpad toggle), is that there is no
effect, nothing happe
20 matches
Mail list logo
