[opensuse] 42.2 - plymouth-start.service: Failed with result 'core-dump'.
Moving a machine from 42.1/LXDE(gtk) to 42.2/XFCE by fresh install. From the log: systemd[1]: Received SIGRTMIN+21 from PID 306 (plymouthd). display-manager[1419]: error: unexpectedly disconnected from boot status daemon systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV systemd[1]: plymouth-start.service: Unit entered failed state. systemd[1]: plymouth-start.service: Failed with result 'core-dump'. But the machine boots fine, including asking for the two different required LUKS passwords, then the user password, and then into the gui. What is? Thanks. Ralph ~> uname -a Linux msb4hp 4.4.62-18.6-default #1 SMP Fri Apr 21 16:14:48 UTC 2017 (84f9824) x86_64 x86_64 x86_64 GNU/Linux -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 20, 2017 3:55:11 AM PDT, listreader <suselist@cableone.net> wrote:
Moving a machine from 42.1/LXDE(gtk) to 42.2/XFCE by fresh install.
From the log:
systemd[1]: Received SIGRTMIN+21 from PID 306 (plymouthd). display-manager[1419]: error: unexpectedly disconnected from boot status daemon systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV systemd[1]: plymouth-start.service: Unit entered failed state. systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
But the machine boots fine, including asking for the two different required LUKS passwords, then the user password, and then into the gui.
What is? Thanks.
Ralph
Uninstall Plymouth - all of it Disable all systemd Plymouth units. Rebuild initrd , or just ignore the message until the next minor kernal patch forces That for you. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 20 May 2017 08:08:51 -0700 John Andersen <jsamyth@gmail.com> wrote:
On May 20, 2017 3:55:11 AM PDT, listreader <suselist@cableone.net> wrote:
systemd[1]: Received SIGRTMIN+21 from PID 306 (plymouthd). display-manager[1419]: error: unexpectedly disconnected from boot status daemon systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV systemd[1]: plymouth-start.service: Unit entered failed state. systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
But the machine boots fine, including asking for the two different required LUKS passwords, then the user password, and then into the gui.
Uninstall Plymouth - all of it Disable all systemd Plymouth units.
Well, yeah, there's that. So, when you get a paper cut on your finger do you also fix that by cutting off your entire hand? :-/ Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/20/2017 02:18 PM, listreader wrote:
Well, yeah, there's that. So, when you get a paper cut on your finger do you also fix that by cutting off your entire hand? :-/
My hand has many valid functions. Plymouth supplies nothing but a coat of paint over scrolling boot messages. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen composed on 2017-05-20 15:40 (UTC-0700):
Plymouth supplies nothing but a coat of paint over scrolling boot messages.
That's not true. It supplies several other things: 1-more things for the CPU and gfxchip to do during boot 2-more time to breathe waiting for boot and routine updates to complete 3-more time to read the initrd load message from Grub 4-more messages to scroll off screen when building each initrd 5-more directory entries 6-more that can go wrong trying to boot 7-more threads in help forums and mailing lists :-D -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello! https://bugzilla.opensuse.org/show_bug.cgi?id=1012142 , right? 20.05.2017 13:55, listreader пишет:
Moving a machine from 42.1/LXDE(gtk) to 42.2/XFCE by fresh install.
From the log:
systemd[1]: Received SIGRTMIN+21 from PID 306 (plymouthd). display-manager[1419]: error: unexpectedly disconnected from boot status daemon systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV systemd[1]: plymouth-start.service: Unit entered failed state. systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
But the machine boots fine, including asking for the two different required LUKS passwords, then the user password, and then into the gui.
What is? Thanks.
Ralph
~> uname -a Linux msb4hp 4.4.62-18.6-default #1 SMP Fri Apr 21 16:14:48 UTC 2017 (84f9824) x86_64 x86_64 x86_64 GNU/Linux
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 20 May 2017 18:19:14 +0300 Mikhail Kasimov <mikhail.kasimov@gmail.com> wrote:
Hello!
https://bugzilla.opensuse.org/show_bug.cgi?id=1012142 , right?
Yes, I think. I saw that bugzilla but as you filed it last November and it was last updated over 3 months ago I was hoping that there was some newer news. Core-dumping subsystems should have some higher importance than "Priority: P5 - None Severity: Normal", IMHO, but what do I know... I will 'bump' your bugzilla by adding a new comment, later this weekend when I get back into that machine. Thanks for reply. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Felix Miata -
John Andersen -
listreader -
Mikhail Kasimov