kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #156931
[Bug 1536249] [NEW] XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend
Public bug reported:
With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
"reboot" and "shut down" buttons don't do anything, and from the CLI I
get:
$ reboot
Failed to execute operation: Transaction is destructive.
I imagine it's associated with closing the lid to suspend because when I
first start the system it reboots fine. It resumes fine when I open the
lid in the sense that I can enter my password and continue to use
Ubuntu, but it would make sense if there's something hanging about in
the background. I don't know how to check this.
(I initially found this "wontfix" bug which describes the same problem:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536249
Title:
XPS 13 9350: reboot fails with "Transaction is destructive" after
resume from suspend
Status in linux package in Ubuntu:
New
Bug description:
With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
"reboot" and "shut down" buttons don't do anything, and from the CLI I
get:
$ reboot
Failed to execute operation: Transaction is destructive.
I imagine it's associated with closing the lid to suspend because when
I first start the system it reboots fine. It resumes fine when I open
the lid in the sense that I can enter my password and continue to use
Ubuntu, but it would make sense if there's something hanging about in
the background. I don't know how to check this.
(I initially found this "wontfix" bug which describes the same
problem:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536249/+subscriptions
Follow ups