I don't really know what we can do about failed upgrades when /run is
full, this part is pretty much a "wont fix". The thing worth looking at
is why you have so many user sessions running. Can you reproduce this?
In a case where you have that many, please copy&paste the output of
"systemd-cgls", "loginctl", and "loginctl show-session XX" for a few XX
values of the output of "loginctl", i. e. session names like "c2" or
"35". Thanks!

** Summary changed:

- package systemd 208-8ubuntu8.2 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
+ package upgrade failed due to full /dev/shm

** Summary changed:

- package upgrade failed due to full /dev/shm
+ package upgrade failed due to full /run

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

** Summary changed:

- package upgrade failed due to full /run
+ lots of logind sessions fill up /run

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518116

Title:
  lots of logind sessions fill up /run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1518116/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to