Your message dated Mon, 01 Jun 2015 19:21:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#779606: daemon-reexec starts plymouth-start.service
service
has caused the Debian Bug report #779606,
regarding daemon-reexec or daemon-reload starts plymouth-start.service
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
779606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779606
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 219-4
Severity: important
I have plymouth installed and enabled (via "splash" on the kernel
command line").
When I run "systemctl daemon-reexec", plymouth is (re)started:
# systemctl --all | grep plymouth
systemd-ask-password-plymouth.path
loaded active waiting Forward Password Requests to Plymouth
Directory Watch
plymouth-quit-wait.service
loaded inactive dead Wait for Plymouth Boot Screen to Quit
plymouth-quit.service
loaded inactive dead Terminate Plymouth Boot Screen
plymouth-read-write.service
loaded inactive dead Tell Plymouth To Write Out Runtime Data
plymouth-start.service
loaded inactive dead Show Plymouth Boot Screen
systemd-ask-password-plymouth.service
loaded inactive dead Forward Password Requests to Plymouth
# systemctl daemon-reexec
# systemctl --all | grep plymouth
systemd-ask-password-plymouth.path
loaded active waiting Forward Password Requests to Plymouth
Directory Watch
plymouth-quit-wait.service
loaded inactive dead Wait for Plymouth Boot Screen to Quit
plymouth-quit.service
loaded inactive dead Terminate Plymouth Boot Screen
plymouth-read-write.service
loaded inactive dead Tell Plymouth To Write Out Runtime Data
plymouth-start.service
loaded active running Show Plymouth Boot Screen
systemd-ask-password-plymouth.service
I've chosen severity important, because if you run that command on the
console, it makes any input impossible.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libapparmor1 2.9.0-3+exp1
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-5
ii libc6 2.19-15
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libmount1 2.25.2-5
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 219-4
ii mount 2.25.2-5
ii sysv-rc 2.88dsf-58
ii udev 219-4
ii util-linux 2.25.2-5
Versions of packages systemd recommends:
ii dbus 1.8.16-1
ii libpam-systemd 219-4
Versions of packages systemd suggests:
ii systemd-ui 3-2
-- Configuration Files:
/etc/systemd/journal-upload.conf fbc67bdd554f87d2f189c1a5fbdcfb27 [Errno 2]
Datei oder Verzeichnis nicht gefunden: u'/etc/systemd/journal-upload.conf
fbc67bdd554f87d2f189c1a5fbdcfb27'
/etc/systemd/journald.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 220-1
Am 27.04.2015 um 15:58 schrieb Martin Pitt:
> Michael Biebl [2015-04-27 15:08 +0200]:
>> Hm, but this patch was reverted again in
>> be847e82cf95bf8eb589778df2aa2b3d1d7ae99e
>> so it's likely that the final v220 won't have a fix for that.
>
> Allegedly this commit replaces it:
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=f78f265f405a6
>
> At least systemctl daemon-reload does not trigger unit starts like
> alsa-restore.service with systemd from upstream git head here.
>
> But judging by the current mailing list responses this doesn't fully
> fix it. This is still under active discussion though, so let's hope
> there's something better for it.
There was another followup commit 4370633083dd9453da183c468cf89cc17254ac39
> That said, adding RemainAfterExit=true to things like
> alsa-restore.service certainly sounds plausible too.
Since I can't reproduce the problem anymore, I'm going to close this bug
report for v220.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
