May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1172028] New: Wrong patch4 in Plymouth.
by bugzilla_noreply＠suse.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 Bug ID: 1172028 Summary: Wrong patch4 in Plymouth. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: olivier.lahaye1(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please remove patch4 in Plymouth package as it seems counter productive on emu. I'm using emu-5.0.0 on MacOS-X with HVF acceleration, and my Plymouth theme with script module fails to go to graphic mode in my specially crafter initrd. (SystemImager-NG) If I rebuild the Plymouth package without the patch 4 (plymouth-only_use_fb_for_cirrus_bochs.patch), and if I re-generate my initrd, my theme works fine. (everything is displayed as expected) I'm using tianocore UEFI bios on emu-5.0.0 on MacOS with HVF acceleration. kernel: vmlinuz-5.3.18-lp152.14-default plymouth: plymouth-0.9.4+git20190304.ed9f201-lp152.4.4.x86_64 See more infos and log here: https://lists.freedesktop.org/archives/plymouth/2020-May/000890.html -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1162535] New: Update openSUSE Plymouth theme for 15.2 to bgrt
by bugzilla_noreply＠novell.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1162535 Bug ID: 1162535 Summary: Update openSUSE Plymouth theme for 15.2 to bgrt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: stasiek(a)michalski.cc QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Following Tumbleweed, change the line setting the default theme to `sed -i -e 's/spinner/bgrt/g' src/plymouthd.defaults` -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 980750] New: Plymouth prevents loading DRM/KMS driver for newly installed graphics card
by bugzilla_noreply＠novell.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=980750 Bug ID: 980750 Summary: Plymouth prevents loading DRM/KMS driver for newly installed graphics card Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: maximilian.staudt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When changing a VGA card in an already installed system, Plymouth will prevent its modern (DRM/KMS) kernel mode driver to be loaded. Example: 1. Install Leap 42.1 in QEMU using the emulated Cirrus card (-vga cirrus). 2. The system boots up with a splash screen. 3. Shut down the system. 4. Start the VM, this time with the Bochs VGA card (-vga std). 5. A splash screen will be shown, but then X falls back to the VESA driver. As a bonus, switching to a text VT (Ctrl-Alt-F1) only gives a blinking cursor. The VT works just fine and is usable, except the user has to operate it blindly as no video is shown. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1156421] New: devel:kubic:images: no persistent systemd journal for aarch64/armv7l
by bugzilla_noreply＠novell.com 18 Aug '22

18 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=1156421 Bug ID: 1156421 Summary: devel:kubic:images: no persistent systemd journal for aarch64/armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The images for Raspberry Pi 2/3 from devel:kubic:images have no persistent systemd journal logging, the x86-64 has. The /var/log/journal directory seems to exist, no idea why the log is written to /run/log/journal instead. -- You are receiving this mail because: You are on the CC list for the bug.

2 35

[Bug 1012883] New: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30)
by bugzilla_noreply＠novell.com 15 Aug '22

15 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1012883 Bug ID: 1012883 Summary: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jeckferson(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's an upstream systemd bug as described in: https://github.com/systemd/systemd/issues/1615 It also manifested in 42.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[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 1172059] New: windows:mingw:win{32,64}: packages including native and cross packages does not build with enabled debug info
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172059 Bug ID: 1172059 Summary: windows:mingw:win{32,64}: packages including native and cross packages does not build with enabled debug info Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ralf.habacker(a)freenet.de QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- If debug information support is enabled in the mentioned project, some packages will not be built due to a conflict when collecting debug information for native and cross-compiled packages. How to reproduce: 1. branch one of the following package into a local project mingw32-libqt4 mingw32-libqt4-static mingw32-libqt5-qtbase mingw32-libqt5-qtdeclarative mingw32-libqt5-qttools 2. enable debug info support at the created project What happens: The build fails with "error: Installed (but unpackaged) file(s) found:" /usr/lib/debug/... What is expected: The build should not fail with debug info support enabled at project or package level Adding debug information at the project level was originally proposed as a workaround for a non-stripping problem with the cross-gcc package reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1116889. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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