April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1083699] New: [Build 148.1] openQA test fails in reboot_icewm
by bugzilla_noreply＠novell.com 12 Aug '22

12 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1083699 Bug ID: 1083699 Summary: [Build 148.1] openQA test fails in reboot_icewm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/623420/modules/reboo t_icewm/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 762487 --> http://bugzilla.opensuse.org/attachment.cgi?id=762487&action=edit no clock widget shown in lxqt ## Observation openQA test in scenario opensuse-15.0-NET-x86_64-otherDE_lxqt@64bit in https://openqa.opensuse.org/tests/623420/modules/reboot_icewm/steps/7 shows no clock widget. The attached screenshot shows that the widget is activated and shows up as "Unknown". ~/.xsession-errors does not show any relevant information. ## Reproducible Fails reproducibly every build. ## Expected result Last good: [openSUSE Leap 42.3 GM](https://openqa.opensuse.org/tests/451668#step/reboot_icewm/7) showing the clock widget in the bottom right corner. ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?flavor=NET&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1073043] New: Krusader hang when copy or move files
by bugzilla_noreply＠novell.com 11 Aug '22

11 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1073043 Bug ID: 1073043 Summary: Krusader hang when copy or move files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: seifert(a)alesak.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After some recent updates Krusader is unable to copy or move files (F5 or F6) however Dolphin, Copy/Paste or Drag and Drop in Krusader works normally There is no errors or crashes, running in gdb and break in hang state: #0 0x00007ffff17f7f40 in nanosleep () from /lib64/libc.so.6 #1 0x00007ffff2493cad in ?? () from /usr/lib64/libQt5Core.so.5 #2 0x00007ffff236e770 in QLockFile::tryLock(int) () from /usr/lib64/libQt5Core.so.5 #3 0x00007ffff49f3d69 in ?? () from /usr/lib64/libKF5ConfigCore.so.5 #4 0x00007ffff49ddb8f in KConfig::sync() () from /usr/lib64/libKF5ConfigCore.so.5 #5 0x00007ffff49de8e5 in KConfig::~KConfig() () from /usr/lib64/libKF5ConfigCore.so.5 #6 0x00007ffff4f155a6 in KRecentDocument::add(QUrl const&, QString const&) () from /usr/lib64/libKF5KIOCore.so.5 #7 0x00007ffff4f156cf in KRecentDocument::add(QUrl const&) () from /usr/lib64/libKF5KIOCore.so.5 #8 0x000055555567d113 in ?? () #9 0x000055555567dbdd in ?? () #10 0x0000555555636191 in ?? () #11 0x0000555555647ae9 in ?? () #12 0x0000555555647d2a in ?? () #13 0x00007ffff246b63a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #14 0x00007ffff33cd982 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #15 0x00007ffff33cfe1c in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #16 0x00007ffff33d0625 in QAction::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x00007ffff33d3afc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x00007ffff33daeb4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x00007ffff243e128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x00007ffff2a32272 in QShortcutMap::dispatchEvent(QKeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #21 0x00007ffff2a3233a in QShortcutMap::tryShortcut(QKeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #22 0x00007ffff29e4897 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /usr/lib64/libQt5Gui.so.5 #23 0x00007ffff2a029e7 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #24 0x00007ffff2a076e5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #25 0x00007ffff29e0f9b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5 #26 0x00007fffe876d420 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #27 0x00007fffed2f9f97 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007fffed2fa1d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007fffed2fa25c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007ffff249423f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #31 0x00007ffff243c73a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #32 0x00007ffff2444fc4 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #33 0x00005555555edcb9 in ?? () #34 0x00007ffff1752f4a in __libc_start_main () from /lib64/libc.so.6 #35 0x00005555555ef49a in _start () to me it looks like it is waiting to obtain some lock but not sure... Interestingly enough when same Krusader is running in Root mode everything works normally. Version 2.6.0 Frameworks 5.40.0 Qt 5.9.2 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1041443] New: Raspberry Pi 3: zypper unclear conflict resolution problem message
by bugzilla_noreply＠novell.com 10 Aug '22

10 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=1041443 Bug ID: 1041443 Summary: Raspberry Pi 3: zypper unclear conflict resolution problem message Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: jeroen.forums.opensuse.org(a)pluimers.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 726808 --> http://bugzilla.suse.com/attachment.cgi?id=726808&action=edit part of zypper.solverTestCase files # Steps leading into this 1. Install Tumbleweed on Raspberry Pi 3 from https://web.archive.org/web/20170526140155/http://download.opensuse.org/rep… 2. On 20170525 perform `zypper --versbose refresh --force` and `zypper dist-upgrade` 3. On 20170528 perform `zypper dist-upgrade --no-allow-vendor-change` Expected: succeed Actual: ``` # zypper dist-upgrade --no-allow-vendor-change Loading repository data... Reading installed packages... Computing distribution upgrade... Problem: problem with installed package kernel-default-4.4.68-7.1.aarch64 Solution 1: keep obsolete kernel-default-4.4.68-7.1.aarch64 Choose the above solution using '1' or cancel using 'c' [1/c] (c): ``` Two important points: 1. Basically both the 1 and c will abort the upgrade so there is no way to perform `--no-allow-vendor-change` upgrades any more. 2. The reason for the "problem" is not revealed so it is unclear to get out of 1. Details: https://gist.github.com/jpluimers/a9ed0802d4314ba3bd662663c2b219a9 which has all the zypper.solverTestCase files -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1111871] New: lxqt-powermanagement: battery not found, it requires upower (perhaps as libkf5solid dependency)
by bugzilla_noreply＠novell.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111871 Bug ID: 1111871 Summary: lxqt-powermanagement: battery not found, it requires upower (perhaps as libkf5solid dependency) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: danielmirkin(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed with LXQt installed on Sony Vaio PCG-71913L. Started LXQt, lxqt-powermanagement complains "Battery not found - LXQt could not find data about any battery - monitoring disabled". Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828697 , I've installed upower on Tumbleweed, and now lxqt-powermanagement is able to find battery data and to show Battery icon [SOLVED]. I suggest upower must be stated as Required to libkf5solid package (or perhaps to lxqt-powermanagement package itself). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1154126] New: hplip-systray does not work correctly with KDE Plasma 5.17
by bugzilla_noreply＠novell.com 07 Aug '22

07 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154126 Bug ID: 1154126 Summary: hplip-systray does not work correctly with KDE Plasma 5.17 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Given TW20191012 with KDE Plasma 5.17 (via KDE/Frameworks5 repo) hplip-systray (hplip-3.19.6-2.1.x86_64) is always shown, although it is configured as "Hide when inactive". As a matter of fact, changing the behaviour of the system tray icon via the HP Device Manager does not have any effect at all. On top of that, the icon is frozen. Any idea? -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1142574] New: cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector
by bugzilla_noreply＠novell.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1142574 Bug ID: 1142574 Summary: cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 811389 --> http://bugzilla.opensuse.org/attachment.cgi?id=811389&action=edit cryfs_standard__ppc64_201907240835.log cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector as reported in openSUSE:Factory:PowerPC (1) log saved as attachment. (1) https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/… === [ 1024s] lto1: error: builtin function '__builtin_crypto_vpmsumd' requires the '-mpower8-vector' option [ 1024s] lto1: fatal error: target specific builtin not available [ 1024s] lto-wrapper: fatal error: /usr/bin/c++ returned 1 exit status [ 1024s] /usr/lib64/gcc/powerpc64-suse-linux/9/../../../../powerpc64-suse-linux/bin/ld: error: lto-wrapper failed [ 1024s] collect2: error: ld returned 1 exit status [ 1042s] error: Bad exit status from /var/tmp/rpm-tmp.caXmGn (%build) === -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1140585] New: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor
by bugzilla_noreply＠novell.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1140585 Bug ID: 1140585 Summary: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: palica(a)liguros.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to use cryfs on an AMD PC: palica@sucellus:~> cryfs .Private/ 9_Private Illegal instruction (core dumped) palica@sucellus:~> sudo cryfs .Private/ 9_Private -o allow_other Illegal instruction palica@sucellus:~> zypper info cryfs Loading repository data... Reading installed packages... Information for package cryfs: ------------------------------ Repository : Main Repository (OSS) (20190704) Name : cryfs Version : 0.10.0-1.3 Arch : x86_64 Vendor : openSUSE Installed Size : 5.5 MiB Installed : Yes Status : up-to-date Source package : cryfs-0.10.0-1.3.src Summary : CryFS encryption Description : CryFS provides a FUSE-based mount that encrypts file contents, file sizes, metadata and directory structure. It uses encrypted same-size blocks to store both the files themselves and the blocks' relations to one another. These blocks are stored as individual files in the base directory, which can then be synchronized to remote storage (using an external tool). palica@sucellus:~> dmesg|tail [ 667.314215] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared) [ 891.504820] traps: cryfs[17825] trap invalid opcode ip:5596343a66df sp:7ffff48b2638 error:0 in cryfs[559634356000+20f000] [ 911.655522] traps: cryfs[18281] trap invalid opcode ip:5568d347c6df sp:7ffec8878018 error:0 in cryfs[5568d342c000+20f000] palica@sucellus:~> lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 16 Model: 4 Model name: AMD Phenom(tm) II X4 965 Processor Stepping: 3 CPU MHz: 800.000 CPU max MHz: 3400.0000 CPU min MHz: 800.0000 BogoMIPS: 6830.70 Virtualization: AMD-V L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 6144K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save I am happy to provide any other info needed. Thanks for help. PS: was already not working with 20190606, I thought that upgrading to latest would solve the issue. IMHO missing some cpu instruction set maybe? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1160019] New: "Metadata corruption detected at xfs_inode_buf_verify"
by bugzilla_noreply＠novell.com 31 Jul '22

31 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1160019 Bug ID: 1160019 Summary: "Metadata corruption detected at xfs_inode_buf_verify" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This happened on a fresh Leap15.1 installation on a laptop, SATA SSD, /home file system. Kernel 4.12.14-lp151.28.36-default. > Dec 28 19:02:47 pallas kernel: XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x72/0xf0 [xfs], xfs_inode block 0x4b860 > Dec 28 19:02:47 pallas kernel: XFS (dm-0): Unmount and run xfs_repair > Dec 28 19:02:47 pallas kernel: XFS (dm-0): First 64 bytes of corrupted metadata buffer: > Dec 28 19:02:47 pallas kernel: ffff8801f164f000: 49 4e 41 ed 03 01 00 00 00 00 04 58 00 00 00 64 INA........X...d > Dec 28 19:02:47 pallas kernel: ffff8801f164f010: 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 ................ > Dec 28 19:02:47 pallas kernel: ffff8801f164f020: 5e 01 34 bd 25 b4 38 63 5d ff e7 a6 01 cc 26 9e ^.4.%.8c].....&. > Dec 28 19:02:47 pallas kernel: ffff8801f164f030: 5d ff e7 a6 01 cc 26 9e 00 00 00 00 00 00 00 34 ].....&........4 The same message is repeated a few times, eventually the FS is mounted r/o, and all kinds of weird failures result. AFAICS in the code in fs/xfs/libxfs/xfs_inode_buf.c, the 15.1 kernel tests nothing but the magic number (byte 0-1, 49 4e) and version (byte 4, 03), so the pattern dumped should be correct. But this is only the 1st inode in the buffer, so subsequent inodes might be bad. However I dumped a full 4k block att offset 0x4b860 and all inode headers seem to be ok so that far. The FS couldn't be umounted, so I rebooted into single-user mode, umounted /home, and ran xfs_repair, which showed nothing of interest: > Phase 1 - find and verify superblock... > - block cache size set to 374008 entries > Phase 2 - using internal log > - zero log...u > zero_log: head block 55736 tail block 55736 > - scan filesystem freespace and inode maps... > - found root inode chunk > Phase 3 - for each AG... > - scan and clear agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > - agno = 1 > - agno = 2 > - agno = 3 > - process newly discovered inodes... > Phase 4 - check for duplicate blocks... > - setting up duplicate extent list... > - check for inodes claiming duplicate blocks... > - agno = 0 > - agno = 3 > - agno = 2 > - agno = 1 > Phase 5 - rebuild AG headers and trees... > - agno = 0 > - agno = 1 > - agno = 2 > - agno = 3 > - reset superblock... > Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - traversing filesystem ... > - agno = 0 > - agno = 1 > - agno = 2 > - agno = 3 > - traversal finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify and correct link counts... > > XFS_REPAIR Summary Sat Dec 28 21:02:45 2019 > > Phase Start End Duration > Phase 1: 12/28 21:02:44 12/28 21:02:45 1 second > Phase 2: 12/28 21:02:45 12/28 21:02:45 > Phase 3: 12/28 21:02:45 12/28 21:02:45 > Phase 4: 12/28 21:02:45 12/28 21:02:45 > Phase 5: 12/28 21:02:45 12/28 21:02:45 > Phase 6: 12/28 21:02:45 12/28 21:02:45 > Phase 7: 12/28 21:02:45 12/28 21:02:45 > > Total run time: 1 second > done A very similar was observed some days later after only a couple of minutes of uptime. > Jan 02 10:35:10 pallas.mittagstun.de kernel: XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x72/0xf0 [xfs], xfs_inode block 0x746b180 > Jan 02 10:35:10 pallas.mittagstun.de kernel: XFS (dm-0): Unmount and run xfs_repair > Jan 02 10:35:10 pallas.mittagstun.de kernel: XFS (dm-0): First 64 bytes of corrupted metadata buffer: > Jan 02 10:35:11 pallas.mittagstun.de kernel: ffff8801dd24d000: 49 4e 81 a4 03 02 00 00 00 00 04 58 00 00 00 64 IN.........X...d > Jan 02 10:35:11 pallas.mittagstun.de kernel: ffff8801dd24d010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ > Jan 02 10:35:11 pallas.mittagstun.de kernel: ffff8801dd24d020: 5e 07 ba 06 1c 4b f6 68 5e 07 ba 04 18 7a e7 4b ^....K.h^....z.K > Jan 02 10:35:11 pallas.mittagstun.de kernel: ffff8801dd24d030: 5e 07 ba 04 18 7a e7 4b 00 00 00 00 00 00 09 e8 ^....z.K........ I wonder if this is an indication of corrupt hardware, and if yes, what (SSD? CPU? Memory? Other?). The SSD in the laptop is brand new; the respective statement by the vendor is corroborated by SMART data (power-on hours). I have run a simple "surface test" (write pattern & verify) on the affected logical volume with fio, and found no errors (only a single test pass thus far). Perhaps noteworthy, I saw also some BTRFS checksum errors in the logs (from root file system): > Dec 28 19:04:17 pallas kernel: BTRFS warning (device sda2): sda2 checksum verify failed on 158384128 wanted D1502CDD found 7F3B5CF3 level 0 > > Jan 02 10:18:00 pallas.mittagstun.de kernel: BTRFS warning (device sda2): csum failed root 267 ino 232862 off 16384 csum 0xed735e63 expected csum 0x7e1dece1 mirror 1 > > Jan 02 10:28:27 pallas.mittagstun.de kernel: BTRFS warning (device sda2): csum failed root 267 ino 248644 off 0 csum 0x347357c0 expected csum 0x2e8516b0 mirror 1 -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1141017] New: installer logs contain user password
by bugzilla_noreply＠novell.com 28 Jul '22

28 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1141017 Bug ID: 1141017 Summary: installer logs contain user password Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- y2log-djV3TE/YaST2/yast-installation-logs/YaST2/y2log: 'text_userpassword' -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1123228] New: Yast2 installation too small fonts on installation menus on HiDPI displays
by bugzilla_noreply＠novell.com 28 Jul '22

28 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1123228 Bug ID: 1123228 Summary: Yast2 installation too small fonts on installation menus on HiDPI displays Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: terje(a)nordland-teknikk.no QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- As previous for Leap 15.0, the 15.1 YasT installer fonts are too small (difficult readable) on HiDPI display (XPS 13) already from the first boot menu. -- You are receiving this mail because: You are on the CC list for the bug.

2 13