August 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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

[Bug 1148809] New: yast2 bootloader fails when lvmcache is in use
by bugzilla_noreply＠novell.com 28 Jul '22

28 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1148809 Bug ID: 1148809 Summary: yast2 bootloader fails when lvmcache is in use Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aspiers(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- [ Originally reported at: https://github.com/openSUSE/libstorage-ng/issues/664 ] I added an lvmcache cachepool to the LV for my root filesystem, and now YaST's bootloader module fails due to not being able to detect the root filesystem. How to reproduce: 1. Start with lvmcache disabled (i.e. normal LVM / filesystem, backed by mdraid) 2. Observe `yast2 bootloader` works fine 3. Activate the cache LV which I previously setup: lvconvert --type cache --cachepool system/cache-root system/root 4. Run `yast2 bootloader` again 5. Observe that an Error dialog pops up, filled with a) lots of (apparently harmless) warnings about an fd leak, and b) an error right at the end showing that it cannot find the disk by LVM UUID: Execution of command "[["/usr/bin/grub2-editenv", "list"]]" failed. Exit code: 1 Error output: File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 7 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 8 (pipe:[4428632]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 9 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv File descriptor 10 (pipe:[4428633]) leaked on vgs invocation. Parent PID 18319: /usr/bin/grub2-editenv /usr/bin/grub2-editenv: error: disk `lvmid/m4f2UJ-widt-pyk9-QkKY-KyJQ-pbwq-V8zzwL/MsUIK0-r51d-MJck-aQwk-ZiAS-A2BI-XdT2vl' not found. 6. Click OK (the only available button) on this dialog 7. Now I see the same dialog I originally reported at the top of this issue. 8. Click `Continue` 9. Observe another dialog: Probing file system with UUID cad8b62c-88e5-4c19-ad24-06e75c0a8987 failed Unexpected situation found in the system. Click below to see more details (English only). Continue despite the error? Continue Abort Details 10. Clicking `Details` shows: device not found, name:/dev/mapper/system-root 11. Click `OK` then `Continue` to continue despite the error 12. Observe another error dialog: Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/share/YaST2/modules/BootStorage.rb:246:in `detect_disks' Details: Missing '/' mount point 13. Click `OK` and yast exits. Clearly there is some side effect of attaching the cache LV which somehow confuses the disk detection code. I see in the error above that it's looking for `lvmid/m4f2UJ-widt-pyk9-QkKY-KyJQ-pbwq-V8zzwL/MsUIK0-r51d-MJck-aQwk-ZiAS-A2BI-XdT2vl`, which seems to correspond OK to the uuids shown here: # dmsetup info system-root Name: system-root State: ACTIVE Read Ahead: 1024 Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 UUID: LVM-m4f2UJwidtpyk9QkKYKyJQpbwqV8zzwLMsUIK0r51dMJckaQwkZiASA2BIXdT2vl # lvdisplay system/root --- Logical volume --- LV Path /dev/system/root LV Name root VG Name system LV UUID MsUIK0-r51d-MJck-aQwk-ZiAS-A2BI-XdT2vl LV Write Access read/write LV Creation host, time install, 2018-12-31 13:15:41 +0000 LV Cache pool name cache-root LV Cache origin name root_corig LV Status available # open 1 LV Size 500.00 GiB Cache used blocks 0.04% Cache metadata blocks 6.47% Cache dirty blocks 0.00% Cache read hits/misses 2 / 15 Cache wrt hits/misses 653 / 572 Cache demotions 0 Cache promotions 336 Current LE 128000 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 1024 Block device 254:0 -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1138858] New: grub2 dns unreliable
by bugzilla_noreply＠novell.com 28 Jul '22

28 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1138858 Bug ID: 1138858 Summary: grub2 dns unreliable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On powerpc DNS resolution does not always work: IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> insmod http grub> net_add_dns 10.160.0.1 grub> linux (http,download.suse.de)/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DVD 1/boot/ppc64le/linux install=http://download.suse.de/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DVD1 error: no DNS reply received. grub> net_add_dns 10.160.0.100 grub> linux (http,download.suse.de)/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DV D1/boot/ppc64le/linux install=http://download.suse.de/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DVD1 error: no DNS reply received. grub> linux (http,download.suse.de)/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DV D1/boot/ppc64le/linux install=http://download.suse.de/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DVD1 grub> initrd (http,download.suse.de)/install/SLP/SLE-12-SP4-Server-GM/ppc64le/DVD1/boot/ppc64le/initrd grub> boot Is this known issue? How do I tell which exact grub version I have? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1036969] New: VUL-1: libmad: assertion failure in layer3.c
by bugzilla_noreply＠novell.com 27 Jul '22

27 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1036969 Bug ID: 1036969 Summary: VUL-1: libmad: assertion failure in layer3.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 723246 --> http://bugzilla.opensuse.org/attachment.cgi?id=723246&action=edit 00213-libmad-heapoverflow-mad_layer_III_reproducer Ref: https://blogs.gentoo.org/ago/2017/04/30/libmad-assertion-failure-in-layer3-… ================================================ Description: libmad stays for “M”peg “A”udio “D”ecoder library. The same testcase provided in the article: libmad: heap-based buffer overflow in mad_layer_III (layer3.c) is able to show an assertion failure if libmad was compiled with debug (–enable-debugging). The complete output of the failure: # madplay -v -i -o raw:out $FILE madplay: /tmp/portage/media-libs/libmad-0.15.1b-r8/work/libmad-0.15.1b/layer3.c:2633: mad_layer_III: Assertion `stream->md_len + md_len - si.main_data_begin <= MAD_BUFFER_MDLEN' failed. Affected version: 0.15.1b Fixed version: N/A Commit fix: N/A Credit: This bug was discovered by Agostino Sarubbo of Gentoo. CVE: N/A Reproducer: https://github.com/asarubbo/poc/blob/master/00213-libmad-heapoverflow-mad_l… Timeline: 2017-01-01: bug discovered and reported to upstream 2017-04-30: blog post about the issue Note: This bug was found with American Fuzzy Lop. ================================================ (open-)SUSE: https://software.opensuse.org/package/libmad 0.15.1b (TW, 42.{1,2}, multimedia:libs repo) -- You are receiving this mail because: You are on the CC list for the bug.

2 3