Hi Dan,
Here we go:
$ free
total used free shared buff/cache available
Mem: 31690904 1853316 27397880 1260984 2439708 28141244
Swap: 35651576 0 35651576
$ cat /proc/swaps
Filename Type Size Used Priority
/swapfile file 2097148 0 -2
/dev/sda1 partition 33554428 0 0
So there is plenty of (unused) swap space.
However, today I found out that with the latest SW update the problem
can not be (so easily) reproduced:
Kernel 5.3.0.28 --> 5.3.0.40
Chromium 79.0.3945 --> 80.0.3987
Systemd 237-3ubuntu10.38 --> 237-3ubuntu10.39
For example, the problem does no longer occur after a (forced) reboot
(killing chromium) and letting chrome/chromium do a recovery. This was
previously absolutely an easy way to reproduce the problem...
$ busctl call org.freedesktop.login1 /org/freedesktop/login1
org.freedesktop.login1.Manager CanHibernate
s "yes"
So, at the moment it is unclear as from when the problem will start to
occur, that is, if it is not solved by one of these patches.
>From the change logs
(http://changelogs.ubuntu.com/changelogs/pool/main/s/systemd/systemd_237-3ubuntu10.39/changelog,
https://www.ubuntuupdates.org/bugs?package_name=chromium-browse), it's
not obvious what could have fixed this...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862797
Title:
Systemd does not allow hibernation when Chrome/chromium is running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
