http://bugzilla.opensuse.org/show_bug.cgi?id=965737 Bug ID: 965737 Summary: plymouth doesn't show passphrase idetification label Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jjletho67-esus@yahoo.it QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installing the patch systemd-210.1453291613.c8d5bdf-25.30.1 to solve the bug 962080 (https://bugzilla.opensuse.org/show_bug.cgi?id=962080) I encountered this problem: while booting, when plymouth shows the textbox in which you can enter the passphrase to unlock an ecrypted device/partition it does not show the identification label that allow you to identify and distinguish every encrypted partition. If i disable plymouth at boot with the kernel option "rd.plymouth=0" the text boot sequence allow me to insert the passphrase, and the name of the partition is correctly showed. Toghether with the systemd patch i also installed those packages: java-1_8_0-openjdk-headless1.8.0.72-21.1 libudev1210.1453291613.c8d5bdf-25.30.1 libudev1-32bit210.1453291613.c8d5bdf-25.30.1 systemd-32bit210.1453291613.c8d5bdf-25.30.1 Mesa-libglapi010.3.7-91.12.1 libgbm110.3.7-91.12.1 libvdpau_nouveau10.3.7-91.12.1 libwayland-egl110.3.7-91.12.1 java-1_7_0-openjdk-headless1.7.0.95-16.1 systemd210.1453291613.c8d5bdf-25.30.1 libtevent-util0-32bit4.1.22-26.1 libOSMesa910.3.7-91.12.1 Mesa-libGLESv2-210.3.7-91.12.1 Mesa-libEGL110.3.7-91.12.1 java-1_8_0-openjdk1.8.0.72-21.1 java-1_7_0-openjdk1.7.0.95-16.1 udev210.1453291613.c8d5bdf-25.30.1 libdcerpc-binding0-32bit4.1.22-26.1 Mesa10.3.7-91.12.1 systemd-sysvinit210.1453291613.c8d5bdf-25.30.1 libtevent-util04.1.22-26.1 libgudev-1_0-0210.1453291613.c8d5bdf-25.30.1 samba-libs-32bit4.1.22-26.1 Mesa-libGL110.3.7-91.12.1 libdcerpc-binding04.1.22-26.1 libsamba-util0-32bit4.1.22-26.1 xorg-x11-server7.6_1.16.1-31.1 libndr-nbt04.1.22-26.1 libndr0-32bit4.1.22-26.1 libgensec04.1.22-26.1 libsamba-hostconfig0-32bit4.1.22-26.1 samba-credentials04.1.22-26.1 libsamba-credentials0-32bit4.1.22-26.1 lsamba-libs4.1.22-26.1 llibsamdb0-32bit4.1.22-26.1 libsamba-util04.1.22-26.1 libgensec0-32bit4.1.22-26.1 libndr04.1.22-26.1 libndr-nbt0-32bit4.1.22-26.1 llibsamba-hostconfig04.1.22-26.1 libndr-standard0-32bit4.1.22-26.1 llibndr-standard04.1.22-26.1 llibsmbclient-raw0-32bit4.1.22-26.1 libsmbconf04.1.22-26.1 libdcerpc0-32bit4.1.22-26.1 libsamdb04.1.22-26.1 libndr-krb5pac0-32bit4.1.22-26.1 libwbclient04.1.22-26.1 libsmbconf0-32bit4.1.22-26.1 libpdb04.1.22-26.1 ibwbclient0-32bit4.1.22-26.1 ibsmbclient-raw04.1.22-26.1 libpdb0-32bit4.1.22-26.1 libdcerpc04.1.22-26.1 libnetapi0-32bit4.1.22-26.1 libsmbldap04.1.22-26.1 libsmbldap0-32bit4.1.22-26.1 libndr-krb5pac04.1.22-26.1 samba-32bit4.1.22-26.1 libnetapi04.1.22-26.1 samba-client-32bit4.1.22-26.1 libsmbclient04.1.22-26.1 libregistry04.1.22-26.1 samba-winbind-32bit4.1.22-26.1 samba-client4.1.22-26.1 samba4.1.22-26.1 samba-winbind4.1.22-26.1 So i'm not completely sure it's a regression of the systemd package, because of the concurrent upddate of all this packages -- You are receiving this mail because: You are on the CC list for the bug.