http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 http://bugzilla.opensuse.org/show_bug.cgi?id=1169783#c63 --- Comment #63 from Konstantin Voinov <kv@kott.no-ip.biz> --- (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.