Processed: Re: Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

2019-05-27 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 921267 -1 Bug #921267 {Done: Michael Biebl } [systemd] systemd fails to reach shutdown.target when rebooting or shutting down the system after resuming from suspend Bug #929655 [systemd] Obscure "Failed to set invocation ID for unit: File exists" error

Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

2019-05-27 Thread Michael Biebl
Control: forcemerge 921267 -1 Am 28.05.19 um 00:59 schrieb Kathryn Tolsen: > Package: systemd > Version: 241-3 > Severity: Serious > > All systemd services are failing to start, best guess is, this is > related to: > > https://github.com/systemd/systemd/issues/11810 This is already fixed in

Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

2019-05-27 Thread Kathryn Tolsen
Package: systemd Version: 241-3 Severity: Serious All systemd services are failing to start, best guess is, this is related to: https://github.com/systemd/systemd/issues/11810