https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c1 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com, | |yfjiang@suse.com Flags| |needinfo?(fcrozat@suse.com) --- Comment #1 from Gerald Pfeifer <gp@suse.com> --- Frederic, Yijan, would you mind having a look 1) in context of upstream/LEO work 2) 15 SP3 (ideally) or 15 SP4 3) openQA or whatever automated testing in place ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c7 Jia Zhaocong <zcjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zcjia@suse.com --- Comment #7 from Jia Zhaocong <zcjia@suse.com> --- (In reply to Gerald Pfeifer from comment #1)

Frederic, Yijan, would you mind having a look 1) in context of upstream/LEO work 2) 15 SP3 (ideally) or 15 SP4 3) openQA or whatever automated testing in place ?

Just tested in SLE15SP3 RC1, on a 24inch 4K display, the password promote has small font, but it is perfectly readable. The password dialog is on the center of bottom of the screen, it is perfectly usable, unlike the screenshot of TW. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c15 --- Comment #15 from Gerald Pfeifer <gp@suse.com> --- Created attachment 847968 --> https://bugzilla.suse.com/attachment.cgi?id=847968&action=edit Grub disk encryption prompt - before Good news, and not so good news (yet): The secondary, graphical disk password screen still shows the artifacts marked with violet in the original screenshot. The proposed change (and the packages I updated manually) address the original disk encryption prompts in Grab. This is an issue I have not filed yet, but observed, and this is a very welcome change. Thank you! In fact, the font now even feels too large, consuming the entire screen width. Let me share how it looked originally - tiny, tiny font size, practically unreadable. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c18 --- Comment #18 from Gerald Pfeifer <gp@suse.com> --- Created attachment 848299 --> https://bugzilla.suse.com/attachment.cgi?id=848299&action=edit /var/log/plymouth-debug.log Thank you, Cliff! I finally managed to download all the RPMs (manually, one by one) and update them and reboot. (Is there a way to have a repository that I can use 'zypper up --from'?) Now my system has the following: libply-boot-client5-0.9.5+git20201026+53c83cc-332.10.x86_64 libply-splash-core5-0.9.5+git20201026+53c83cc-332.10.x86_64 libply-splash-graphics5-0.9.5+git20201026+53c83cc-332.10.x86_64 libply5-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-branding-openSUSE-84.87.20200106-2.1.noarch plymouth-dracut-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-plugin-label-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-plugin-label-ft-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-plugin-two-step-0.9.5+git20201026+53c83cc-332.10.x86_64 plymouth-scripts-0.9.5+git20201026+53c83cc-332.10.noarch plymouth-theme-bgrt-0.9.5+git20201026+53c83cc-332.10.noarch plymouth-theme-spinner-0.9.5+git20201026+53c83cc-332.10.noarch The initial password screen in Grub now again looks like https://bugzilla.suse.com/attachment.cgi?id=847968 not like the much bigger font I shared in comment #16. The later screen (attachment "Screenshot of the startup screen") looks unchanged, i.e., the small text, that is sliced horizontally, to half to the right, bottom half to the left, still is there. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c23 --- Comment #23 from Gerald Pfeifer <gp@suse.com> --- (In reply to Cliff Zhao from comment #22)

I am still working on this bug. These weeks there have 3 high level bugs are working together, one is release ship-stopper; one is reported by L3 team; 2 of them is to be pushed by the senior product manager. This bug and bsc#1184309 is in processing, but maybe not update very quickly.

Thank you for the update, Cliff, and no worries.

And I have 1 question: the title of this bug indicates your notebook screen is HiDPI, but the hardware test shows your screen is "96x96 dots per inch" which means it is not. So after you login to the desktop, does the interface have any difference with normal notebook on the resolution?

This is a good observation, and it made me curious. Here is an interesting aspect I found: # xdpyinfo | grep dimensions dimensions: 3840x2160 pixels (1016x571 millimeters) As you can see, this indeed is 4K/UHD resolution, alas the size is very off. This is a 14" notebook screen, and definitely not a meter wide and half a meter tall. ;-) I assume this is where the incorrect DPI values come from? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c25 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fcrozat@suse.com) | --- Comment #25 from Gerald Pfeifer <gp@suse.com> --- (In reply to Cliff Zhao from comment #24)

Could you please take a try of the test edition? I could make a deep examination of your widget arrangement. You just have to run the following steps

Thank you Cliff, I'll be happy to do so. Before I give it a go, an observation I confirmed today with most current Tumbleweed: When I reboot my system, the password prompt we are looking for completely lacks the help text and looks as in attachment https://bugzilla.suse.com/attachment.cgi?id=848488 Given this, do you still want me to run this exercise? As a minor note, the following commands will leave my system in a different state since I've got three repositories which are not enabled right now:

2, sudo zypper mr -da 12, sudo zypper mr -ea

I can handle that, just wanted to point it out. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c28 --- Comment #28 from Gerald Pfeifer <gp@suse.com> --- Created attachment 849607 --> https://bugzilla.suse.com/attachment.cgi?id=849607&action=edit /var/log/plymouth-debug.log based on comment #27 Thank you. Please find attached the log file following the instructions from comment #27. As for the visual appearance, this was very different now - not graphical, but a text based prompt in the first row of the screen. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c31 --- Comment #31 from Gerald Pfeifer <gp@suse.com> --- Created attachment 849806 --> https://bugzilla.suse.com/attachment.cgi?id=849806&action=edit /var/log/plymouth-debug.log I looked into this in detail, and believe see what has been happening and why I have been getting a text-only screen in comment #28: My system has "installRecommends = yes" disabled in /etc/zypp/zypper.conf When I reinstalled plymouth with zypper install --recommends -r bsc1183425_plymouth_HiDPI plymouth I got a password screen that had the full text in tiny font (and no graphical effects whatsover, essentially text on a graphics screen). Attaching /var/log/plymouth-debug.log from that run. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c33 --- Comment #33 from Cliff Zhao <qzhao@suse.com> --- Thanks, it's great! it helps a lot. It looks like in the first time your system didn't update all packages, but in the last time, it works. Currently, openSUSE's Plymouth and its libraries have dependence between each other, which means it could not work in cross editions. When you see a no graphic interface, but only a password question at the top of the screen, it means Plymouth already quit for some exception. According to the last comment's log, Plymouth works again, which is very good. But the label and label-ft still could not be loading. So could you please confirm plymouth-plugin-label and plymouth-plugin-label has been update in your system? :~> rpm -q plymouth-plugin-label :~> rpm -q plymouth-plugin-label-ft Thank you -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c35 --- Comment #35 from Cliff Zhao <qzhao@suse.com> --- In this situation, Could you please run :~> ls -l /usr/lib64/plymouth/ |grep label :~> rpm -V plymouth-plugin-label And show me the output. The log says that the "label.so" is missing, no such file or directory, that is strange. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c37 --- Comment #37 from Cliff Zhao <qzhao@suse.com> --- Okay, the file's privilege looks fine, and installation is successful. Based on this factor, could you show me the disk information by: :~> lsblk -f Thank you so much! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c39 --- Comment #39 from Cliff Zhao <qzhao@suse.com> --- Hi Gerald: Did you see the prompt in the next reboot at the last? Or maybe my reply email didn't reach to you, I realize the email is updating recently today. In this case, you also could try my test repo, I have updated it to provide an easy way to confirm. Steps are the same with comment27. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c41 --- Comment #41 from Cliff Zhao <qzhao@suse.com> --- (In reply to Gerald Pfeifer from comment #40)

(In reply to Cliff Zhao from comment #39)

...

Did you see the prompt in the next reboot at the last?

Hi Cliff, I have tried twice now (last night and a few days before), and in both cases there was no text label associated with the prompt.

It's strange, so what will output when you run: :~> sudo lsinitrd /boot/initramfs-`uname -r`.img |grep 'otf\|label'

...

In this case, you also could try my test repo, I have updated it to provide an easy way to confirm. Steps are the same with comment27.

I'll be happy to do so, just will take a bit since I'm worried my system may break due to /usr-merge on Tumbleweed (so first need to make a full backup/clone to an external drive and prepare a rescue system). OK, that's all right. I'm in no hurry. :)

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

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c43 --- Comment #43 from Gerald Pfeifer <gp@suse.com> --- (In reply to Cliff Zhao from comment #41)

It's strange, so what will output when you run: :~> sudo lsinitrd /boot/initramfs-`uname -r`.img |grep 'otf\|label'

I don't have /boot/initramfs* on my system. % ll /boot/init* lrwxrwxrwx 1 root root 23 Mai 22 09:40 /boot/initrd -> initrd-5.12.4-1-default -rw------- 1 root root 19M Mai 30 10:32 /boot/initrd-5.12.3-1-default -rw------- 1 root root 19M Mai 30 10:33 /boot/initrd-5.12.4-1-default Trying to adjust your command accordingly I get the following: % lsinitrd /boot/initrd | egrep 'otf|label' rootfs-block -rwxr-xr-x 1 root root 1242 Mar 3 13:38 lib/dracut/hooks/initqueue/timeout/99-rootfallback.sh -rwxr-xr-x 1 root root 4152 Mar 3 13:38 usr/lib/systemd/system-generators/dracut-rootfs-generator Does that give you any ideas? (To be clear, I never "played" with initrd, drakut or the likes, which might be a cause for some non-standard behavior.) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c45 --- Comment #45 from Gerald Pfeifer <gp@suse.com> --- sudo cat /etc/dracut.conf # PUT YOUR CONFIG IN separate files # in /etc/dracut.conf.d named "<name>.conf" # SEE man dracut.conf(5) for options And for bonus points, I also ran `more /etc/dracut.conf.d/*` :::::::::::::: /etc/dracut.conf.d/99-debug.conf :::::::::::::: # Below adds additional tools to the initrd which are not urgently necessary to # bring up the system, but help to debug problems. # See /usr/lib/dracut/modules.d/95debug/module-setup.sh which additional tools # are installed and add more if you need them. This specifically helps if you # use: # rd.break=[cmdline|pre-udev|pre-trigger|initqueue|pre-mount| # mount|pre-pivot|cleanup] # boot parameter or if you are forced to enter the dracut emergency shell. # add_dracutmodules+=debug :::::::::::::: /etc/dracut.conf.d/ostree.conf :::::::::::::: # Copyright (C) 2013 Colin Walters <walters@verbum.org> # # This library is free software; you can redistribute it and/or # modify it under the terms of the GNU Lesser General Public # License as published by the Free Software Foundation; either # version 2 of the License, or (at your option) any later version. # # This library is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # Lesser General Public License for more details. # # You should have received a copy of the GNU Lesser General Public # License along with this library; if not, write to the # Free Software Foundation, Inc., 59 Temple Place - Suite 330, # Boston, MA 02111-1307, USA. add_dracutmodules+=" ostree systemd " reproducible=yes -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c47 --- Comment #47 from Gerald Pfeifer <gp@suse.com> --- I had some problems with my system (and couldn't fully update due to the /lib -> /usr/lib change yet), but when I updated the system a bit earlier the text was back per the first attachment in this report. Following your instructions, I got the following output: sudo dracut -f /etc/dracut.conf:install_items+="/usr/lib64/plymouth/label.so /usr/share/fonts/truetype/Cantarell-Regular.otf /usr/share/fonts/truetype/Cantarell-Light.otf" dracut: WARNING: <key>+=" <values> ": <values> should have surrounding white spaces! dracut: WARNING: This will lead to unwanted side effects! Please fix the configuration file. dracut: Executing: /usr/bin/dracut -f dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: crypt *** dracut: *** Including module: dm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 60-persistent-storage-dm.rules dracut: Skipping udev rule: 55-dm.rules dracut: *** Including module: kernel-modules *** dracut: *** Including module: kernel-modules-extra *** dracut: *** Including module: lvm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 56-lvm.rules dracut: Skipping udev rule: 60-persistent-storage-lvm.rules dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-btrfs *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: ostree *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including module: suse-initrd *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done *** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin *** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: rd.luks.uuid=luks-653e6b16-6fbf-4d1a-919c-5509bee45ddd rd.luks.uuid=luks-36e940bd-6ab8-434f-8a7f-c705544a27b3 dracut: rd.lvm.lv=system/root rd.lvm.lv=system/swap dracut: root=/dev/mapper/cr_system-root rootfstype=ext4 rootflags=rw,relatime dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Creating image file '/boot/initrd-5.12.4-1-default' *** dracut: *** Creating initramfs image file '/boot/initrd-5.12.4-1-default' done *** <<<<< end <<<<< end <<<<< end <<<<< end <<<<< end <<<<< end <<<<< % sudo lsinitrd /boot/initrd-5.12.4-1-default | egrep 'Cantarell|label.so' -rwxr-xr-x 1 root root 23072 Apr 10 16:29 usr/lib64/plymouth/label.so -rw-r--r-- 1 root root 103432 Dec 23 2020 usr/share/fonts/truetype/Cantarell-Light.otf -rw-r--r-- 1 root root 100216 Dec 23 2020 usr/share/fonts/truetype/Cantarell-Regular.otf -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1183425 https://bugzilla.suse.com/show_bug.cgi?id=1183425#c49 --- Comment #49 from Cliff Zhao <qzhao@suse.com> --- (In reply to Gerald Pfeifer from comment #48)

Created attachment 850905 [details] Screenshot after following instructions in comment #46

Following the actions/instructions in comment #46 I rebooted into that kernel and IT WORKS!

The positioning of the text may not be optimal (I'd put it a little lower or, as previously, above the entry field), but it's there, well readable, and no undesired visual artifacts.

Good detective work, Cliff! :-)

Does this provide what you need to tackle this?

Thank you, Gerald, for your time, seems I have known the cause of this problem. And as for your suggestion, I will consider it carefully, sooner or later I will accomplish it. :-) -- You are receiving this mail because: You are on the CC list for the bug.