On some more investigation, the problem seems to be with operating with
the laptop lid closed (while it is plugged in to an external monitor).
This is a standard usage for me. Upon booting, I usually close the lid
at the login screen or after logging in. The laptop display goes off,
everything gets
Reporting exact same issue.
Running 18.04.1 on System76 Serval WS.
(1) On clean boot, (most times) no network connection. Have to run:
> sudo service network-manager restart
(2) Suspend/power off fails, and have to kill existing hanging suspend
--
You received this bug notification because yo
Same problem here.
I'm using
- system: Ubuntu Desktop 18.04 LTS
- machine: Lenovo Thinkpad X1 Extreme (Nvidia GeForce GTX 1050 Ti graphic card)
- Thinkpad Thunderbold 3 docking station
- external monitor (display port from docking station)
I'm booting with the lid closed.
Directly after clean b
Hello
I have same issue, I'd reported in
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-
manager/+bug/1545188?comments=all
The file obtained with "journalctl -b > log.txt" is
https://pastebin.com/LNX2B4Ye
Thanks a lot
--
You received this bug notification because you are a member of Ubu
Hello.
I'm having the same problems with shutdown. Yesterday, I've choosed
"menu/logout/halt" option instead of "menu/logout/shutdown". And
problems started to happen: I could not even reboot or shutdown
computer, because every time when I wanted to do this, there was a
window to unblock session (
This still exists in Ubuntu 18.04(alpha)
I have the additional fun effect that my Dell M4800 laptop (lid closed, with 2
external monitors attached via docking station) suspends immediately after
logging into the display manager (doesnt matter if it is gdm3 or lightdm) on
boot. Only after waking
This still exists in Ubuntu 18.04(alpha)
I have the additional fun effect that my Dell M4800 laptop (lid closed, with 2
external monitors attached via docking station) suspends immediately after
logging into the display manager (doesnt matter if it is gdm3 or lightdm) on
boot. Only after waking
i have the same issue on 16.10 Dell Latitude E6430
i can't use the interface to shutdown or reboot and for
#shutdown -h
ubuntu Failed to power off system via logind: There's already a shutdown or
sleep operation in progress
and only i can reboot or shutdown using the -f
# shutdown -f
$ unam
I have same issue on XUbuntu 16.04 on a Acer Aspire One ZA3.
When I close the screen to go to sleep, then after that I can't get back the
wifi connection, and I can't shutdown.
Reboot -f works though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Xubuntu 16.04 user here on EXT4. I don't use suspend on my Dell Latitude
laptop at all. Was just trying to reboot after noticing my network
manager indicator icon was in limbo and 'lo and behold:
% sudo -H shutdown -P now
Failed to start poweroff.target: Transaction is destructive.
See system logs
Similar issue for me like, berend.
hanging "systemd-sleep suspend" process after wake up.
"reboot -f" does NOT work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Title:
hanging suspend job
This happened to me and I'm NOT using BTRFS. My partitions are EXT4
formatted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Title:
hanging suspend job prevents shutdown
To manage notificat
Same here, also system76 laptop. I think I get it after a failed
suspend. I.e. close laptop lid, and it won't suspend. When I open the
lid again, I have no network. Then I can't reboot. Factors that may
impact is that I have nfs directories mounted (using autofs, so
hopefully not mounted), and a bl
I could not agree more with Robert Jansen, as I also think the problem
is caused by the systemd plague. Steps to reproduce on a Thinkpad X1
Carbon 4th gen:
1) Turn on; shutdown -h now => no problem;
2) Turn on; sleep (e.g. close lid); wake up (e.g. open lid); shutdown -h now =>
problem!
Doing a
I think it is related to the monstrosity called systemd.
Using this command to suspend solves all suspend/resume problems here
echo mem> /sys/power/state
I guess this command directly tells the kernel to suspend, without
relying on buggy systemd crap.
--
You received this bug notification beca
Indeed it isn't related to btrfs, but we still don't want to allow
shutdown while the machine is suspending, and vice versa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Title:
hanging susp
pitti, please change the status of this bug as the problem is not
related to btrfs but is bug by itself. I'm experiening this since 16.04
without any btrfs file system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Same issue with XPS DE 9350 upgraded to 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Title:
hanging suspend job prevents shutdown
To manage notifications about this bug go to:
https
Had a couple of reports of this on System76 Machines. It appears this is
manifests as an incomplete resume, where some job in the resume doesn't
terminate, leading systemd to think the machine is still resuming, while
at the same time the system appears to be up and running normally. This
is a very
Had a couple of reports of this on System76 Machines. It appears this is
manifests as an incomplete resume, where some job in the resume doesn't
terminate, leading systemd to think the machine is still resuming, while
at the same time the system appears to be up and running normally.
--
You recei
Same problem here. Xubuntu 14.04 through 16.04.
Suspend, reboot, shutdown.
All fail in some or other way on all the above versions.
On 16.04:
shutdown -h now
Failed to start poweroff.target: Transaction is destructive.
and
systemctl suspend
fails because a suspend process is already in progre
I also have this problem. After a suspend I can't shutdown or reboot
either from Gnome/unity or a terminal.
I've got a clean install of Ubuntu 16.04 LTS running 4.4.0-21-generic on
a Dell XPS 13 9350 laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same problem here, Ubuntu 16.04 on dell xps 13 9350 4.4.0-21-generic
After a suspend I can not shutdown nor reboot, getting the error
mentioned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Same issue with Ubuntu 15.04. Systemd just suddenly decides to refuse
rebooting. System is not suspending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441253
Title:
hanging suspend job prevents s
Exact same issue for me also. Dell XPS 15 (9550) running Ubuntu 16.04.
The issue is ONLY reproducible after a suspend. Once the laptop is
suspended UI controls do nothing; from commandline, reboot, halt or
poweroff return the same error:
Failed to execute operation: Transaction is destructive
I
Same issue with 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 s
Confirm same issue in Lubuntu 15.10, with same step to produce this bug.
Root[system] file is locked, can't write anything in /
but not happen if i change options for "When Laptop lid is close" to "Switch
Off Display".
Confirm -f 'forcing' is work in reboot and poweroff.
--
You received this bug
Same here. Ubuntu 16.04 (as of today), asus laptop, no external
monitors. cannot poweroff, suspend, hibernate and reboot. reboot -f and
poweroff -f commands do NOT work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Same here. I have this problem since I updated to 15.04 that goes with the 3.19
kernels.
With the previous series of kernels 3.16 it was working just fine.
My laptop is a sony vaio vgn-cs11z. In my case failing to sleep has nothing to
do with external devices, it happens anyways.
Also after th
I just experienced the same issue, but I don't have anything related to
btrfs in logs. I also had a problem on a laptop (Thinkpad E540) with
external HDMI monitor not waking up. I tried to wake up the monitor by
closing and opening the lid. Finally I tried to shut down in the display
manager but no
We don't want to shutdown while a suspend is running, and vice versa.
This would be confusing and could lead to data loss in the worst case.
Can you please instead file a bug against the kernel about the btrfs
failure? We should fix suspend/the file system properly :-)
Note that you can still shut
The system is a Laptop in a docking station, two external monitors,
booted up with lid closed.
Last time I tried (a week ago) , the system suspended, but didn't wake
up properly (external monitors didn't turn on). At that time I
attributed that to the btrfs lookup that has been plaguing the system
32 matches
Mail list logo
