Debian Bug report logs - #779606
daemon-reexec or daemon-reload starts plymouth-start.service

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: daemon-reexec starts plymouth-start.service service

Date: Tue, 03 Mar 2015 01:05:19 +0100

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

Message #10 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

Cc: 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Tue, 03 Mar 2015 01:21:34 +0100

[Message part 1 (text/plain, inline)]

Am 03.03.2015 um 01:05 schrieb Michael Biebl:
> I've chosen severity important, because if you run that command on the
> console, it makes any input impossible.

What I mean by that: If you e.g. run daemon-reexec on tty1, plymouth
shows its splash screen, but for some reason, no keyboard input is
possible anymore. I can't switch to another tty, nor stop the splash
screen via ESC nor reboot the computer with ctrl+alt+del


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #17 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Michael Biebl <biebl@debian.org>, 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Thu, 2 Apr 2015 10:48:38 +0200

Hey Michael,

Michael Biebl [2015-03-03  1:05 +0100]:
> I have plymouth installed and enabled (via "splash" on the kernel
> command line").
> 
> When I run "systemctl daemon-reexec", plymouth is (re)started:

I could reproduce this (and other restarted services) until recently,
but it seems fixed with the v219-stable updates (for me and also for
the original reporter in the Ubuntu bug LP#1431200). Do you still get this
with 219-6? If so, can you please put the "journalctl -f" output here
that happens when you do systemctl daemon-reload (and/or -reexec).

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Message #22 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Thu, 02 Apr 2015 12:32:58 +0200

[Message part 1 (text/plain, inline)]

Hi!

Am 02.04.2015 um 10:48 schrieb Martin Pitt:

> Michael Biebl [2015-03-03  1:05 +0100]:
>> I have plymouth installed and enabled (via "splash" on the kernel
>> command line").
>>
>> When I run "systemctl daemon-reexec", plymouth is (re)started:
> 
> I could reproduce this (and other restarted services) until recently,
> but it seems fixed with the v219-stable updates (for me and also for
> the original reporter in the Ubuntu bug LP#1431200). Do you still get this
> with 219-6? If so, can you please put the "journalctl -f" output here
> that happens when you do systemctl daemon-reload (and/or -reexec).

Have you run a git bisect on the v219-stable branch to find the relevant
commit?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #27 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Michael Biebl <biebl@debian.org>, 779606@bugs.debian.org

Cc: Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 6 Apr 2015 13:49:58 +0200

[Message part 1 (text/plain, inline)]

Hello Michael,

Michael Biebl [2015-04-02 12:32 +0200]:
> Have you run a git bisect on the v219-stable branch to find the relevant
> commit?

I didn't yet. I couldn't reliably reproduce it before either, so I'm
not sure how to bisect reliably. At this point I'd like to collect
data from reporters whether it still actually happens for them.

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 06 Apr 2015 22:59:19 +0200

[Message part 1 (text/plain, inline)]

Am 06.04.2015 um 13:49 schrieb Martin Pitt:
> Hello Michael,
> 
> Michael Biebl [2015-04-02 12:32 +0200]:
>> Have you run a git bisect on the v219-stable branch to find the relevant
>> commit?
> 
> I didn't yet. I couldn't reliably reproduce it before either, so I'm
> not sure how to bisect reliably. At this point I'd like to collect
> data from reporters whether it still actually happens for them.

I'm currently back to v215. the release is close so I want to run what
we are going to ship.
Will test v219 again once jessie is out.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #37 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 779606@bugs.debian.org, Michael Biebl <biebl@debian.org>

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 27 Apr 2015 15:03:15 +0200

[Message part 1 (text/plain, inline)]

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=88401
Control: fixed -1 219-6

Hello again,

Martin Pitt [2015-04-02 10:48 +0200]:
> Hey Michael,
> 
> Michael Biebl [2015-03-03  1:05 +0100]:
> > I have plymouth installed and enabled (via "splash" on the kernel
> > command line").
> > 
> > When I run "systemctl daemon-reexec", plymouth is (re)started:
> 
> I could reproduce this (and other restarted services) until recently,
> but it seems fixed with the v219-stable updates (for me and also for
> the original reporter in the Ubuntu bug LP#1431200). Do you still get this
> with 219-6? If so, can you please put the "journalctl -f" output here
> that happens when you do systemctl daemon-reload (and/or -reexec).

I'm fairly sure this is the same as
https://bugs.freedesktop.org/show_bug.cgi?id=88401 which got fixed in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e392c9c45 and
was part of the v219-stable patch set.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #46 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 27 Apr 2015 15:08:51 +0200

[Message part 1 (text/plain, inline)]

Am 27.04.2015 um 15:03 schrieb Martin Pitt:
> Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=88401
> Control: fixed -1 219-6
> 
> Hello again,
> 
> Martin Pitt [2015-04-02 10:48 +0200]:
>> Hey Michael,
>>
>> Michael Biebl [2015-03-03  1:05 +0100]:
>>> I have plymouth installed and enabled (via "splash" on the kernel
>>> command line").
>>>
>>> When I run "systemctl daemon-reexec", plymouth is (re)started:
>>
>> I could reproduce this (and other restarted services) until recently,
>> but it seems fixed with the v219-stable updates (for me and also for
>> the original reporter in the Ubuntu bug LP#1431200). Do you still get this
>> with 219-6? If so, can you please put the "journalctl -f" output here
>> that happens when you do systemctl daemon-reload (and/or -reexec).
> 
> I'm fairly sure this is the same as
> https://bugs.freedesktop.org/show_bug.cgi?id=88401 which got fixed in
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e392c9c45 and
> was part of the v219-stable patch set.
> 

Hm, but this patch was reverted again in
be847e82cf95bf8eb589778df2aa2b3d1d7ae99e
so it's likely that the final v220 won't have a fix for that.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #51 received at 779606@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: 779606@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 27 Apr 2015 15:58:00 +0200

[Message part 1 (text/plain, inline)]

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.

That said, adding RemainAfterExit=true to things like
alsa-restore.service certainly sounds plausible too.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #58 received at 779606-done@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 779606-done@bugs.debian.org

Subject: Re: Bug#779606: daemon-reexec starts plymouth-start.service service

Date: Mon, 01 Jun 2015 19:21:40 +0200

[Message part 1 (text/plain, inline)]

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 (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.