Hi,
Sorry to reopen the issue, but I have faced the same problem today. There was
un upgrade, but I don't think anything related to systemd or login. Anyway,
nothing helped : halt -p, poweroff, systemctl poweroff... Neither as user nor
as root, from console or gnome terminal... The physical pow
Like
https://bugzilla.kernel.org/buglist.cgi?quicksearch=systemd
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=systemd
https://wiki.debian.org/systemd#Known_Issues_and_Workarounds
?
> Could you please point me (us?) to a good and reasonably short summary
> about the known is
On Thu, 2014-12-18 at 22:24 +0100, Michael wrote:
> Florian,
>
> Well, you can see it this way. I'd rather seen a bit more sensibility in
> doing that 'big step' when it means so much damage.
>
> > systemd is a big step for debian, but its not the cause for everything.
>
> Yes, true.
>
> Well
On 12/19/14 08:02, Rainer H. Rauschenberg wrote:
> On Thu, 18 Dec 2014, Florian Reitmeir wrote:
>> On 12/18/14 21:22, Michael wrote:
>>> i did not mean it literally. I meant that systemd upstream rejected to
>>> care for any other kernel, than Linux, and that was the result. I can
>>> dig up the
On Thu, 18 Dec 2014, Florian Reitmeir wrote:
> On 12/18/14 21:22, Michael wrote:
> > i did not mean it literally. I meant that systemd upstream rejected to
> > care for any other kernel, than Linux, and that was the result. I can
> > dig up the respective mails if you require me too, but it wil
Florian,
Well, you can see it this way. I'd rather seen a bit more sensibility in doing
that 'big step' when it means so much damage.
> systemd is a big step for debian, but its not the cause for everything.
Yes, true.
Well, anyway, poweroff button stopped working for me too, on both my lapto
Hi,
for openbsd like other architectures .. e.g. GNU/HURD, M68, PowerPC
there were simply not enough developers and users.
if the openbsd-debian people perform and get their port in order, there
is no problem in releasing the next time.
systemd is a big step for debian, but its not the cause for
Florian,
i did not mean it literally. I meant that systemd upstream rejected to care for
any other kernel, than Linux, and that was the result. I can dig up the
respective mails if you require me too, but it will be some work since i did
not bookmark them (and i have no browser history).
But,
Hi again,
Just for completeness: the laptop went power off normally after a normal
day of work. No idea what my have triggered the odd behaviour from
Monday 15 to Wednesday 17, neither about what solved the issue today: I
haven't made any significant upgrade since Monday...
Thanks to all who pro
Hi,
On 12/18/14 12:56, Michael wrote:
>> The systemd point of view is that any breakage is caused by other
>> packages failing to detect that systemd is installed.
>
> And besides, that's how they shot down the Debian OpenBSD port, just like
> that.
thats not true.
greetings
--
Florian Rei
Bjørn,
> Yes, systemd will happily break existing ACPI PM setups without any
> warning.
>
> The systemd point of view is that any breakage is caused by other
> packages failing to detect that systemd is installed.
And besides, that's how they shot down the Debian OpenBSD port, just like that.
Hi,
Big thanks to Eddy (yes, I can read French :-) ), Michael and Bjørn for
your responses.
Just a note: in /etc/default/halt I already had:
HALT=poweroff
Having said that, great mystery: I touched nothing, and poweroff works
today... Well, this is actually what I did after reading your three
me
Michael writes:
> Edit /etc/default/halt and change the value as Eddy writes.
>
> Yes, systemd is probably the cause, it replaced pm acpi by its own
> terminology, disregarding the legacy convention.
Yes, systemd will happily break existing ACPI PM setups without any
warning.
The systemd point
Edit /etc/default/halt and change the value as Eddy writes.
Yes, systemd is probably the cause, it replaced pm acpi by its own terminology,
disregarding the legacy convention.
if nothing else helps, replace systemd with systemd-shim emulation (maybe also
switching back to sysvinit).
--
To UN
Le 17 déc 2014 à 10:36 (+0100)
Miguel Ortiz Lombardía a écrit:
>
> Hi,
>
> I'm running Debian testing (jessie) on an HP EliteBook 840 G1 laptop.
> Everything goes reasonably well, even very well, except that after
> running apt-get update/upgrade on Monday (15 December) I cannot halt
> (powerof
Hi,
I'm running Debian testing (jessie) on an HP EliteBook 840 G1 laptop.
Everything goes reasonably well, even very well, except that after
running apt-get update/upgrade on Monday (15 December) I cannot halt
(poweroff) the computer. When I try to switch it off it just reboots. I
manage to get i
16 matches
Mail list logo
