Bug#776171: same problem

[Fabien]

Same problem occured to me (just after "apt-get upgrade", trying to reboot the 
system). 

Please also see this link: 
 
http://unix.stackexchange.com/questions/274761/debian-wont-shut-down-failed-to-start-poweroff-target-transaction-is-destruct
 

Someone there says that killing the "systemd-sleep" process can help. When I 
tried, my system went to sleep immediately. When I resumed it, it went back to 
life but the screen stayed black (I had quit my desktop session and even 
stopped my desktop manager, so I was on a console, no GUI was running). I tried 
to type "poweroff" without the screen, it didn't work, but when I hit the power 
button, the machine finally stopped correctly...

Bug#776171: same problem

[Thomas Vaughan]

On Sun, 10 Jul 2016 15:36:57 +0200 Michael Biebl  wrote:
> Control: tags -1 + moreinfo
>
> Hi
>
> Am 25.02.2016 um 10:26 schrieb Vincent Bernat:
> >
> > Same problem here. Any poweroff, reboot, suspend targets answer with the
> > same message. Absolutely no clue how to debug this...
>
> Which systemd version do you use? Is this problem reproducible (on a
> current sid system)?

​I am seeing this "transaction is destructive" message still whenever,
after starting up my laptop docked, I try to do a shutdown.

When docked with lid closed, the machine is incapable of shutting down
normally.  If I log in as root and type 'poweroff', that's when I see
"transaction is destructive".

I run Debian sid, updated daily.

I think that this problem has existed for me ever since the forced
transition to systemd months and months ago.

This problem has tempted me to look at Devuan, but I have so far been too
lazy.

My work-around is to leave my laptop lid open when it is docked. However, I
don't like this because
(a) my keyboard grows needlessly ever dirtier with dust over the months, and
(b) the backlight is on and generates extra heat that I'd rather not inject
into my already-too-hot office.​

​Please help.​

​(I am using the stock '/etc/systemd/logind.conf'.​ I have tried mucking
with the various lid-switch settings, but nothing seems to work.)

​My machine is a Latitude E6530 with both Nvidia and Intel via Optimus.
When docked, I am using the proprietary Nvidia drivers via dkms.

Both Intel and Nvidia drivers are installed, and I manually switch between
them via the update-glx command when I transition between docked and
undocked configuration.

--
​Thomas E. Vaughan
tevaug...@gmail.com​

Bug#776171: same problem

[Vincent Bernat]

 ❦ 10 juillet 2016 15:36 CEST, Michael Biebl  :

>> Same problem here. Any poweroff, reboot, suspend targets answer with the
>> same message. Absolutely no clue how to debug this...
>
> Which systemd version do you use? Is this problem reproducible (on a
> current sid system)?

Hi!

For me, it was on an up-to-date sid system (updated almost daily). It
was the first time and it didn't occur a second time (either because of
more recent versions of systemd were running or because it occurs
rarely, dunno).
-- 
Use the fundamental control flow constructs.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#776171: same problem

[Michael Biebl]

Control: tags -1 + moreinfo

Hi

Am 25.02.2016 um 10:26 schrieb Vincent Bernat:
> 
> Same problem here. Any poweroff, reboot, suspend targets answer with the
> same message. Absolutely no clue how to debug this...

Which systemd version do you use? Is this problem reproducible (on a
current sid system)?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#776171: same problem on desktop

[Pavel Mendl]

I am experiencing this problem over multiple months (maybe a year) already. I 
hoped it will get soon fixed via standard package upgrades, but as it still 
persist and is really annoying I googled around and now send this message in 
hope to increase priority a bit ;).

In my case there are several facts I would like to share:
1) Plane desktop, no lid, no auto sleeping in setup. this particular Debian 
instalation worked without this issue for many years before. Only standard 
aptitude updates done under manual control, no dist-upgrade/updates.
2) As I do have auto-logging user (myself :) ) in KDE, if I choose reboot it 
simply relogs back to deskotp.
3) I do use only sleep (now called suspend to ram) via KDE kicker's Leave-
>suspend menu. Never experienced problems with waking up.
4) Workaround with sudo reboot -f works allways, however often I am getting 
some file reparations/removals reported on next boot. As I reboot often on 
dual-boot system, this scares me a bit.
5) Sometimes (about 1/4 cases) reboot works normally from KDE.

uname -a
Linux  4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 
GNU/Linux

Pavel Mendl

Bug#776171: same problem

[Vincent Bernat]

 ❦  1 septembre 2015 23:34 -0300, "M."  :

> Having exactly the same problem:
>
> sudo shutdown -h now 
> Failed to start poweroff.target: Transaction is destructive.

Same problem here. Any poweroff, reboot, suspend targets answer with the
same message. Absolutely no clue how to debug this...
-- 
I don't know half of you half as well as I should like; and I like less
than half of you half as well as you deserve.
-- J. R. R. Tolkien


signature.asc
Description: PGP signature

Bug#776171: same problem

[M.]

Having exactly the same problem:

sudo shutdown -h
now

Failed to start poweroff.target: Transaction is destructive.

Broadcast message from iser@endeavor on pts/1 (Ter 2015-09-01 22:28:39 BRT):

The system is going down for power-off NOW!


sudo shutdown -r
now

Failed to start reboot.target: Transaction is destructive.

Broadcast message from iser@endeavor on pts/1 (Ter 2015-09-01 22:33:16 BRT):

The system is going down for reboot NOW!

Nothing but opening the notebook lid and pressing the power button for 4
seconds shutdowns the system.

Cheers

Bug#776171: Same problem

[M.]

I'm running Debian Sid and have exactly the same problem: issuing a sudo
shutdown -r now gives me the error


Failed to start reboot.target: Transaction is destructive.

The system is going down for reboot NOW!