April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[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 1177358] New: EFI system partition: VFAT or FAT16 or FAT12 or FAT32?
by bugzilla_noreply＠suse.com 17 Aug '22

17 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177358 Bug ID: 1177358 Summary: EFI system partition: VFAT or FAT16 or FAT12 or FAT32? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kaykaykay123(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Why openSUSE installer specifies "EFI system partition" as VFAT? What file system is actually used? By standard we need FAT32 for EFI system partition + fixed drives: https://en.wikipedia.org/wiki/EFI_system_partition "FAT32 is always expected on fixed drives". VFAT is not equal to FAT32: https://en.wikipedia.org/wiki/File_Allocation_Table Windows requires FAT32 for EFI system partition. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[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 1174755] New: virt-install installs openSUSE Tumbleweed aarch64 DVD iso failed.
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1174755 Bug ID: 1174755 Summary: virt-install installs openSUSE Tumbleweed aarch64 DVD iso failed. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried to use virt-install to install openSUSE-Tumbleweed-DVD-aarch64-Current.iso. I got "Couldn't find kernel for install tree." error message and failed. My virt-install command: virt-install --location /home/joeyli/iso/openSUSE-Tumbleweed-DVD-aarch64-Current.iso -r 2048 --accelerate --arch aarch64 -n opensuseTW-aarch64 -f /home/joeyli/qemu-vm/opensuseTW-aarch64.qcow2 --network bridge=br0 --vcpus 2 --graphics none --extra-args="-enable-kvm -vnc :91" --boot loader=/usr/share/qemu/qemu-uefi-aarch64.bin Error message: Starting install... ERROR Couldn't find kernel for install tree. Domain installation does not appear to have been successful. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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 1183582] New: transactional server role has very inconsistent package selection (TW, SLE, Leap)
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1183582 Bug ID: 1183582 Summary: transactional server role has very inconsistent package selection (TW, SLE, Leap) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Selecting the transactional server role results in a very different selection of patterns and packages. On Tumbleweed: https://openqa.opensuse.org/tests/1667896#step/disable_grub_timeout/13 Documentation, Minimal Base, Enhanced Base, AppArmor, YaST Base, Software Management, Minimal Appliance Base On SLE 15 SP3: https://openqa.suse.de/tests/5670408#step/disable_grub_timeout/14 Minimal Base, Enhanced Base, AppArmor, 32-Bit Runtime Environment On Leap 15.3: https://openqa.opensuse.org/tests/1667171#step/disable_grub_timeout/13 Minimal Base, Minimal Appliance Base -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1175037] New: Sporadic endless loop in claws-mail/RSSyl - pango or harfbuzz related?
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175037 Bug ID: 1175037 Summary: Sporadic endless loop in claws-mail/RSSyl - pango or harfbuzz related? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 840462 --> http://bugzilla.opensuse.org/attachment.cgi?id=840462&action=edit gdb backtrace of claws-mail In claws-mails (3.17.6 from Tumbleweed) RSS reader RSSyl some messages cause "endless loops". The problem happens in Tumbleweed and Leap 15.2 (in Leap 15.2 observed with claws-mail 3.17.5 from GA and also with 3.17.6 from the update - repo). But it is not identical, a message which triggers the endless loop in Tumbleweed can be viewed without problem in Leap 15.2. Luckily it is only a small percentage of messages which cause this, but if it happens claws-mail needs to be killed. Viewing the same message after the restart will trigger the problem again. In backtraces taken while in this endless loop state I always observed harfbuzz or pango related entries last on the stack. So maybe the actual problem is in this area. Attached several stack traces from claws-mail looping over the same message. 38 is the related message which caused this in Tumbleweed snapshot 20200807 which can be opened in Leap 15.2 with up to date fixes. I did not observe something similar with Leap 15.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[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