Control: fixed -1 219-1
Control: severity -1 important
Hello Tino,
Tino [2015-06-01 23:13 +0200]:
> This time it segfaulted while adding a job that should restart journald.
This is known to not work. Don't restart journald for 215, as it has
no way to save its open pipes from connected services
Processing control commands:
> fixed -1 219-1
Bug #787473 [systemd] systemd: Segfault while adding a new job
Marked as fixed in versions systemd/219-1.
> severity -1 important
Bug #787473 [systemd] systemd: Segfault while adding a new job
Severity set to 'important' from 'critical'
--
787473: ht
Am 01.06.2015 um 23:56 schrieb Tino:
> I don't know why or when this job was triggered. The uptime of the
> system was about 1.5-2 days until it happened.
> I don't have any custom or modified units. The only change i made with
> systemd is setting the log level to debug.
> I've seen a sefault whil
I don't know why or when this job was triggered. The uptime of the
system was about 1.5-2 days until it happened.
I don't have any custom or modified units. The only change i made with
systemd is setting the log level to debug.
I've seen a sefault while systemd was processing systemd-udevd events
t
Am 01.06.2015 um 23:13 schrieb Tino:
> Package: systemd
> Version: 215-17
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> systemd doesn't survive two days on my bare minimal headless NAS
> installation. I already purged all unused packages, reinstalled syste
Package: systemd
Version: 215-17
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
systemd doesn't survive two days on my bare minimal headless NAS
installation. I already purged all unused packages, reinstalled systemd
and reverted all config files to factory default, re
6 matches
Mail list logo
