Your message dated Tue, 01 Jul 2014 01:29:03 +0200
with message-id <87d2dqm0xs.wl%[email protected]>
and subject line Re: Bug#753357: Power button broken due to systemd stealthily 
installed
has caused the Debian Bug report #753357,
regarding Power button broken due to systemd stealthily installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
753357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753357
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-8

After a recent upgrade, the power button on my laptop stopped doing
anything useful.

It turned out that a recent upgrade had installed systemd, but without
replacing init with it.  The powerbtn-acpi-support.sh script was detecting
a running systemd-logind, and therefore doing nothing.

Folks, I understand that you're excited about systemd, but this sort of
stealthy pulling in of code is something that really pisses people off.
If I'd rather not be running 150000 lines of code as pid 1, please respect
my wishes.

-- Juliusz

--- End Message ---
--- Begin Message ---
reopen 753357
thanks

Michael Biebl <[email protected]> wrote:

>> Folks, I understand that you're excited about systemd, but this sort of
>> stealthy pulling in of code is something that really pisses people off.

> If you don't want to run systemd as pid one and you want to use logind,
> then install systemd-shim.

Sorry, I'm afraid there was a misunderstanding.  I have no wish to run
logind.

The issue is that

  apt-get update
  apt-get dist-upgrade

stealthily installed systemd, which broke my system.  Fixing the issue was
a simple matter of

  apt-get purge systemd

but it took me the best part of an hour (including tracing the acpi
scripts) to find what the issue is.  Please add some conflicts to the
systemd package to make sure it doesn't happen in the future.

-- Juliusz

--- End Message ---

Reply via email to