http://bugzilla.opensuse.org/show_bug.cgi?id=1020327
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327#c20
--- Comment #20 from Franck Bui
(In reply to Franck Bui from comment #18)
When the service fails, bugs like 927250 and its three dups happen. (Or the udev behaviour is buggy, in which case the .service should be removed entirely, I guess)
Can you comment on this^^^^?
Sorry but I can't parse other bugs currently, my plate is full ;)
I'd proceed this way for now:
- Change back RemainAfterExit in systemd
I'm not sure about this change at all and this should be discussed upstream first. But IMHO this not the (root) issue here it just exposes the shortcoming in plymouth.
AFAICS it's still wrong. Either systemd-vconsole-setup.service needs to go completely or set RemainAfterExit=true.
The only reason I can see for the existence of systemd-vconsole-setup.service is that others (3rd party) services are mentioning it. And plymouth is one of those... -- You are receiving this mail because: You are on the CC list for the bug.