http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c2 Antoine Belvire changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |info@itwrx.org --- Comment #2 from Antoine Belvire --- *** Bug 1169794 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c3 Antoine Belvire changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antoine.belvire@opensuse.or | |g, qzhao@suse.com --- Comment #3 from Antoine Belvire --- cc plymouth maintainer -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c5 --- Comment #5 from IT wrx --- In my case, it successfully prompts for the luks passphrase for both partitions on the root drive, but fails when it comes to a third, auxiliary internal sata drive. The first two are btrfs and the third is ext4, if that might matter. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Michiel Janssens changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michiel@nexigon.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Tyson Moore changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tyson@tyson.me -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c8 Marcel Kuehlhorn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann@suse.com --- Comment #8 from Marcel Kuehlhorn --- *** Bug 1169891 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c9 --- Comment #9 from Cliff Zhao --- Hi andy: could you show me the support-log? Thank you so much! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c11 --- Comment #11 from Bug Reporter --- (In reply to andy great from comment #7) Yes, your workaround does alleviate this, so plymouth likely is the culprit. Although recovery mode does not display a splash screen, it apparently still relies on plymouth. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c13 Antoine Belvire changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tneo@gmx.com --- Comment #13 from Antoine Belvire --- *** Bug 1169927 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c15 --- Comment #15 from andy great --- @Cliff Zhao What support-log? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c17 Keks Dose changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cookie170@web.de --- Comment #17 from Keks Dose --- I ran into this as well, openSuse TW. Machine stopped booting for no apparent reason and opened emergency prompt. After snapper rollback I locked all plymouth packages and made zypper dup again. Machine booted. So from my point ov fiew the new plymouth version is buggy. (Version: 0.9.5+git20191224+d7c737d as announced by DimStar April 16.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c19 --- Comment #19 from Cliff Zhao --- (In reply to Thomas Zimmermann from comment #18)

FTR: This bug also happens on new installs.

Okay Thomas, thank you so much for the confirmation. I will switch back to this issue when I finished the openSUSE:Leap gap problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c21 --- Comment #21 from Thomas Zimmermann --- (In reply to Cliff Zhao from comment #19)

(In reply to Thomas Zimmermann from comment #18)

...

FTR: This bug also happens on new installs.

Okay Thomas, thank you so much for the confirmation. I will switch back to this issue when I finished the openSUSE:Leap gap problem.

Well, I don't know, but this bug breaks many users' systems. I'd prioritize this one. Simply reverting Plymouth back to the old version would be an improvement. -- You are receiving this mail because: You are on the CC list for the bug.

(In reply to Cliff Zhao from comment #19)

...

(In reply to Thomas Zimmermann from comment #18)

...

FTR: This bug also happens on new installs.

Okay Thomas, thank you so much for the confirmation. I will switch back to this issue when I finished the openSUSE:Leap gap problem.

Well, I don't know, but this bug breaks many users' systems. I'd prioritize this one. Simply reverting Plymouth back to the old version would be an improvement. Okay, I'll come up with some remedies if I can not deal with them in a short term.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c23 --- Comment #23 from Cliff Zhao --- Created attachment 836470 --> http://bugzilla.opensuse.org/attachment.cgi?id=836470&action=edit Tumbleweed boot with an encrypted partition (In reply to Thomas Zimmermann from comment #21) the attachment is the test for the latest Tumbleweed installed with encrypted partition but it seems works fine. I don't know if there has any difference between us. Do you have any suggestions? Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c25 --- Comment #25 from t neo --- I can't speak for Andy, but the issue is in the update to 2020-04-16 for me. The path in the plymouth.service file was not updated correctly. A fresh install with the same snapshot gave the same error. Thus a way to replicate is installing snapshot 2020-04-10 and upgrade to 2020-04-16. Or install snapshot 2020-04-16 fresh. Once the path in plymouth.service is fixed a new upgrade with zypper dup did not throw an issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c27 --- Comment #27 from Bug Reporter --- In my case, the problem occurs with an extraneous encrypted drive that is unlocked at boot (via /etc/crypttab), but not mounted. Hence, filesystem and partition layout do not seem to matter. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c29 --- Comment #29 from andy great --- Created attachment 836774 --> http://bugzilla.opensuse.org/attachment.cgi?id=836774&action=edit Support log from Andy -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c31 --- Comment #31 from Robert Kaiser --- (In reply to t neo from comment #16)

In the file /usr/lib/systemd/system/systemd-ask-password-plymouth.service

FWIW, that file does not exist in my installation or in the plymouth package. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c33 --- Comment #33 from andy great --- Created attachment 836775 --> http://bugzilla.opensuse.org/attachment.cgi?id=836775&action=edit Screenshot for Gparted and YaST Partition. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c35 --- Comment #35 from Robert Kaiser --- (In reply to andy great from comment #32)

(In reply to Robert Kaiser from comment #31)

...

(In reply to t neo from comment #16)

...

In the file /usr/lib/systemd/system/systemd-ask-password-plymouth.service

FWIW, that file does not exist in my installation or in the plymouth package.

I do have that file on my TW installation.

Ugh, yes, my fault, I looked for plymouth-* when it clearly isn't. But this looks strange:

grep "pid" /usr/lib/systemd/system/*plymouth* /usr/lib/systemd/system/plymouth-start.service:ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session /usr/lib/systemd/system/systemd-ask-password-plymouth.path:ConditionPathExists=/run/plymouth/pid /usr/lib/systemd/system/systemd-ask-password-plymouth.service:ConditionPathExists=/var/run/plymouth/pid

Note that the middle one, in .path, points to /run and not to /var/run as the other two... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c37 --- Comment #37 from Robert Kaiser --- That said, switching all those paths to /var/run did not fix it for me, but then, I also do not run into the timeout any more that ended up giving me the possibility to work around the issue, so my system doesn't boot at all any more atm and I have to use the rescue system from a Leap 15.1 DVD to get to anything. This new problem happened after upgrading from Tumbleweed 20200416 to 20200422, and looking through the emails on packages updates in between those I see systemd 245, pointing to https://github.com/openSUSE/systemd/blob/SUSE/v245/NEWS whioch mentions an "UPGRADE ISSUE" connected to plymouth which lead me to https://bugzilla.redhat.com/show_bug.cgi?id=1807771 and https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/99 - which could also be connected. Now applying that on the system before rebooting does not fix this for me yet, though I see the prompt for a very short time on the console output screen. I did reboot and try to enter the password when that was visible, but not not complete that (3-4 stars appeared there), but then when the switch to the three-dot-text screen of plymouth comes up, now it actually switches to the text-screen plymouth prompt and that works correctly... So not completely fixed but getting closer... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c39 --- Comment #39 from Robert Kaiser --- Sorry for yet another comment, but it seems I can enter it there but it may not work. Entering it on the console prompt before the switch happens does work though. Thankfully my passphrase is not too long to be entered in that short time. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c40 Konstantin Voinov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kv@kott.no-ip.biz --- Comment #40 from Konstantin Voinov --- I'm stuck with this bug too. Is there "official" workaround? If it needs logs/diags from my suffering system - please tell. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c42 --- Comment #42 from andy great --- (In reply to Konstantin Voinov from comment #40)

I'm stuck with this bug too. Is there "official" workaround? If it needs logs/diags from my suffering system - please tell.

Also more system logs will be beneficial. Do it as comment 22 says. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c44 --- Comment #44 from andy great --- (In reply to Jacob W from comment #43)

I had this issue too, but my setup is more standard and oddly enough, I had it *much* worse than others. I only have /home encrypted via LUKS. Paritions are standard for TW (meaning / is btrfs with default TW setup).

So while I could not get the password prompt to work at all, even if disabling plymouth via grub, I also had the "pleasure" of having all my snapshots removed! I could not rollback because all snapshots disappeared from grub and from /.snapshots in recovery mode.

After much cursing (which helps a lot in these types of situations & I highly recommend it), many reboots and trial and error, including editing crypttab because the man page has wrong info re the password entry, by some miracle, I finally got my snapshots to show up in grub again. I took no further risks, and immedietly proceeding to rollback, locked every package that has anything to do with plymouth, and zypper dup again. Now my system works fine.

I hate plymouth with a passion. Years ago I had a similar situation but without the disappearing snapshots (I reported a bug, but plymouth maintainer decided to ignore it after some time).

There was talk awhile back of removing plymouth from openSUSE. This needs to be done, not just talked about.

I'm most definitely not risking more horrors & decided not to "retry" to get logs.

Plymouth have ability to delete .snapshots? Maybe this have to be filed in a separate bug/feature request to limit plymouth permission? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c46 --- Comment #46 from Konstantin Voinov ---

...

Tumbleweed snapshot 20200425 with new plymouth update release, have anyone try it?

the same -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c48 --- Comment #48 from Thomas Zimmermann --- (In reply to andy great from comment #45)

Tumbleweed snapshot 20200425 with new plymouth update release, have anyone try it?

It actually got worse. There is a systemd update as part of the snapshot. And now it doesn't even seem to t go into emergency mode (within a few minutes?) automatically. So booting and repairing just got harder. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Jürgen Spitzmüller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juergen@spitzmueller.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c51 --- Comment #51 from J Merkel <459874983@gmx.net> --- (In reply to J Merkel from comment #49)

A question for clarification, hoping some of you could answer. I'm not (yet) affected by this bug, because I've stopped updating when I saw this bug report on the mailing list. All 3 partitions on my TW installation are encrypted, and I've configured the system i.e. grub to ask only once for the passphrase, all three partitions are then unlocked by a keyfile provided in cryptab later in the process. I do not see plymouth involved in this case so, in case I would do an upgrade would the configuration I've described be affected at all by the bug ?

To answer myself for the sake of others in similar situation: My assumption was right, I did an upgrade to 20200428, my config boots without problem. Plymouth is showing the three dots while decrypting the drives but is not screwing the boot process. Why on earth is plymouth being used on TW - a (b)leading edge rolling release where probably most users want to see the diagnostics at boot and push the ESC key anyhow??? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c53 --- Comment #53 from t neo --- Moving forward to the latest Tumbleweed the issue is still here. I was not easily able to fix it this time around and rolled back to my previous working snapshot. @Cliff Zhao do you have an update on the fix for the upgrade path with Plymouth? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c54 --- Comment #54 from Cliff Zhao --- (In reply to t neo from comment #53)

Moving forward to the latest Tumbleweed the issue is still here. I was not easily able to fix it this time around and rolled back to my previous working snapshot.

@Cliff Zhao do you have an update on the fix for the upgrade path with Plymouth?

Right now, I have 2~3 priorities beyond this problem on my to-do list, and if I take it upon myself to prioritize it, I will be criticized. sorry. but don't worry, I will do it as soon as possible. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c56 --- Comment #56 from Konstantin Voinov --- I'm not gonna switch. But no any official statement makes things worse. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c58 --- Comment #58 from t neo --- I'm not going to switch, but it is worrisome that this issue is not given priority. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c61 Daniel Molkentin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.molkentin@suse.com --- Comment #61 from Daniel Molkentin --- I think I have a fix for the crypto partition unlock problem: The run directory, which is critical to the process is incorrect after dropping a patch that hard codes it, in favor of letting configure auto guess. Unfortunately, due to variations in the build environment, this goes wrong (which is consistent with #c16). If I am correct, the package from https://software.opensuse.org//download.html?project=home%3Admolkentin%3Abranches%3ABase%3ASystem&package=plymouth fixes the Problem. Could someone please try that? Andreas: Clearing the console is another issue, and it probably should be in a separate report. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c63 --- Comment #63 from Konstantin Voinov --- (In reply to Daniel Molkentin from comment #61)

I think I have a fix for the crypto partition unlock problem: The run directory, which is critical to the process is incorrect after dropping a patch that hard codes it, in favor of letting configure auto guess. Unfortunately, due to variations in the build environment, this goes wrong (which is consistent with #c16).

If I am correct, the package from https://software.opensuse.org//download. html?project=home%3Admolkentin%3Abranches%3ABase%3ASystem&package=plymouth fixes the Problem. Could someone please try that?

Andreas: Clearing the console is another issue, and it probably should be in a separate report.

I've tried. Switched to your repo, but plymouth fails on start: -- Logs begin at Fri 2020-05-08 13:38:13 +10, end at Fri 2020-05-08 13:42:19 +10. -- мая 08 13:38:14 kot-sony systemd[1]: Starting Show Plymouth Boot Screen... мая 08 13:38:14 kot-sony plymouthd[345]: /usr/sbin/plymouthd: symbol lookup error: /usr/sbin/plymouthd: undefined symbol: ply_kernel_command_line_get_key_value мая 08 13:38:14 kot-sony plymouthd[343]: failed to read status from child immediately after starting to daemonize: Success мая 08 13:38:14 kot-sony systemd[1]: plymouth-start.service: Control process exited, code=exited, status=1/FAILURE мая 08 13:38:14 kot-sony systemd[1]: plymouth-start.service: Failed with result 'exit-code'. мая 08 13:38:14 kot-sony systemd[1]: Failed to start Show Plymouth Boot Screen. мая 08 13:38:16 kot-sony systemd[1]: Starting Show Plymouth Boot Screen... мая 08 13:38:16 kot-sony plymouthd[448]: /usr/sbin/plymouthd: symbol lookup error: /usr/sbin/plymouthd: undefined symbol: ply_kernel_command_line_get_key_value мая 08 13:38:16 kot-sony plymouthd[447]: unexpectedly exited with status 127 immediately after starting to daemonize мая 08 13:38:16 kot-sony systemd[1]: plymouth-start.service: Control process exited, code=exited, status=1/FAILURE мая 08 13:38:16 kot-sony systemd[1]: plymouth-start.service: Failed with result 'exit-code'. мая 08 13:38:16 kot-sony systemd[1]: Failed to start Show Plymouth Boot Screen. мая 08 13:38:18 kot-sony systemd[1]: Starting Show Plymouth Boot Screen... мая 08 13:38:19 kot-sony systemd[1]: Started Show Plymouth Boot Screen. At least text console with password prompt appears. zypper se -si plymouth Загрузка данных о репозиториях... Чтение установленных пакетов... С | Имя | Тип | Версия | Архитектура | Репозиторий ---+----------------------------+-------+---------------------------------+-------------+------------------------------------- i+ | plymouth | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-branding-openSUSE | пакет | 84.87.20191004-3.7 | noarch | openSUSE:Tumbleweed i+ | plymouth-branding-openSUSE | пакет | 84.87.20191004-3.7 | noarch | openSUSE:Factory i+ | plymouth-branding-openSUSE | пакет | 84.87.20191004-3.7 | noarch | openSUSE-Tumbleweed-Oss i+ | plymouth-dracut | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-plugin-label | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-plugin-label-ft | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-plugin-script | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-plugin-two-step | пакет | 0.9.5+git20200418+14e91cc-290.1 | x86_64 | home:dmolkentin:branches:Base:System i+ | plymouth-scripts | пакет | 0.9.5+git20200418+14e91cc-290.1 | noarch | home:dmolkentin:branches:Base:System i+ | plymouth-theme-bgrt | пакет | 0.9.5+git20200418+14e91cc-290.1 | noarch | home:dmolkentin:branches:Base:System i+ | plymouth-theme-spinner | пакет | 0.9.5+git20200418+14e91cc-290.1 | noarch | home:dmolkentin:branches:Base:System -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Ignacio Taranto changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |itaranto7@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c67 --- Comment #67 from Konstantin Voinov --- Hi, Sadly no. I updated to that version and was unable to boot again. Can I provide some debug info? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 IT wrx changed: What |Removed |Added ---------------------------------------------------------------------------- CC|info@itwrx.org | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c70 --- Comment #70 from Cliff Zhao --- (In reply to Konstantin Voinov from comment #69)

...

It's strange.

Should I update all packages to this repo or just plymouth?

Just plymouth is fine.

...

You are using a virtual-machine or a real workstation?

This is real laptop with two ssd, one ssd is encrypted /home

Thanks, understand.

...

what do you mean by "unable to boot"? you can not login to desktop, or you can't get the TTY console?

Plymouth's animation rotates forever. When I press ESC I get console with these last lines:

[ OK ] Reached target Initrd Root File System. Starting Reload Configuration from the Real Boot...

(I can upload a photo if needed) OK, by the way, you use gdm or sddm?

...

please provide the debuginfo, supportlog and plymouth.log.

Hmmm, how can I get it in such situation? for supportlog: 1, $ zypper install supportutils 2, $ supportconfig 3, Upload the tar file from your system "/var/log/scc_...txz" to here as an attachment.

for plymouthlog: 1, Edit /boot/grub2/grub.cfg, find the line of kernel paramter (which would looks like: "linux /boot/vmlinuz-5.3.18-lp152.19-default root=UUID=3a6c732b-0ae4-4950-853f-217548143fe2 splash=silent mitigations=auto quiet") 2, Add "plymouth:debug" in the tail of this line. 3, reboot. 4, Log into the system. You will find the log in "/var/log/plymouth-debug.log" 5, Upload the log as an attachment to this bug. Thank you very much! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c72 --- Comment #72 from Konstantin Voinov --- Sorry for delay. I use this laptop everyday, so not much time for experiments. I cannot boot in this btrfs snapshot at all. All I can is the change boot option in grub directly during boot then try to get log from other working boot config. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c74 --- Comment #74 from Cliff Zhao --- (In reply to Konstantin Voinov from comment #72)

Sorry for delay. I use this laptop everyday, so not much time for experiments. I cannot boot in this btrfs snapshot at all. All I can is the change boot option in grub directly during boot then try to get log from other working boot config.

You can generate the support-log from the snapshot which works for you. and upload it first. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c76 --- Comment #76 from Konstantin Voinov --- (In reply to Cliff Zhao from comment #75)

Hi Konstantin: Are you still there?

being busy, i'll do tests and report in this weekend -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c78 --- Comment #78 from Konstantin Voinov --- Created attachment 840946 --> http://bugzilla.opensuse.org/attachment.cgi?id=840946&action=edit plymouth dbg K. Voinov -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Ignacio Taranto changed: What |Removed |Added ---------------------------------------------------------------------------- CC|itaranto7@gmail.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c81 --- Comment #81 from Konstantin Voinov --- (In reply to Cliff Zhao from comment #80)

(In reply to Konstantin Voinov from comment #79)

...

I've added files from healthy config. Will try to get plymouth log from broken.

I am checking the support log and debug log these days, Thanks for the corrperate. May I ask what will be the result when you run: $ plymouth-set-default-theme?

It means, changing the theme then upgrade plymouth? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c83 --- Comment #83 from Cliff Zhao --- and could you please have a try with https://api.opensuse.org/package/binaries/Base:System/plymouth/openSUSE_Fact... I only update the source with upstream. and don't forget to use the latest edition of plymouth-branding, if not do so, plymouth will quit unexpectedly. Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c85 --- Comment #85 from Cliff Zhao --- Hi Andy: Could you please try the update of plymouth in https://api.opensuse.org/package/binaries/Base:System/plymouth/openSUSE_Fact... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c86 --- Comment #86 from Konstantin Voinov --- (In reply to Cliff Zhao from comment #84)

Hi Konstantin: Could you please try the update of plymouth in https://api.opensuse.org/package/binaries/Base:System/plymouth/ openSUSE_Factory?

Hi, I've tried today and as i can see the plymouth is updated in main repo: v | plymouth | пакет | 0.9.5+git20200921+20778f2-307.22 | x86_64 | Base:System Factory Devel Project (openSUSE_Factory) i+ | plymouth | пакет | 0.9.5+git20200921+20778f2-1.1 | x86_64 | openSUSE:Tumbleweed So, i don't know should i change repo or is the bug resolved? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c88 --- Comment #88 from Cliff Zhao --- (In reply to Hans-Peter Jansen from comment #87)

Cliff, I'm using the latest B:S/plymouth on several systems and harvest bootsplash regressions (filed upstream) on 3 (very different) systems. In those cases, plymouthd crashes.

In home:frispete:Tumbleweed/plymouth, I've updated to latest GIT, but see no difference. An attempt to go back to some 0.9.5-2019 version (rebuilt) fails in similar ways, which points to some other issue. Might be glibc, dracut, kernel, whatever...

Want me to file another bugzilla here?

Could you please check the branding package first? have you updated it already? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c90 --- Comment #90 from Cliff Zhao --- (In reply to Hans-Peter Jansen from comment #87)

Cliff, I'm using the latest B:S/plymouth on several systems and harvest bootsplash regressions (filed upstream) on 3 (very different) systems. In those cases, plymouthd crashes.

In home:frispete:Tumbleweed/plymouth, I've updated to latest GIT, but see no difference. An attempt to go back to some 0.9.5-2019 version (rebuilt) fails in similar ways, which points to some other issue. Might be glibc, dracut, kernel, whatever...

Want me to file another bugzilla here?

A little question: How do you update? with "zypper" or "rpm"? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c92 --- Comment #92 from Cliff Zhao --- (In reply to Hans-Peter Jansen from comment #91)

I always use zypper.

...

solved it for *all* crashing systems. Upstream doesn't want to apply a simple fix to prevent a DeviceTimeout=0 setting, hence we might want to deal with this in %post or apply a local patch. Probably we just missed to install a properly adjusted plymouthd.defaults. But I haven't fully grokked the plymouthd.conf and plymouthd.defaults handling, yet, sorry.

This has been discussed. option "DeviceTimeout" could not be pre-defined in the program because a lot of people install Linux in a server without display server. In this case the server will wait for an additional meaningless time when booting to OS. Only the administrator knows how many seconds is appropriate. and the recommended time is already been set in the config file. so it could not be modified. But you said that "plymouthd could crash, if DeviceTimeout is undefined" because currently, Plymouth config file is migrated to branding package, I will confirm if it is correct. if there has any problem, I will update. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.