openSUSE Bugs August 2021

bugs@lists.opensuse.org

1 participants
2913 discussions

[Bug 1186669] New: postfix.service has "Requires=var-run.mount"

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1186669 Bug ID: 1186669 Summary: postfix.service has "Requires=var-run.mount" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It's been spotted in bsc#1181970 that postfix.service has "Requires=var-run.mount". This is probably incorrect as adding a dependency on /var/run, which is essentially the same as specifying a dep on /run these days, seems unneeded as /run is guaranteed to be mounted before any services are started. So would it possible to drop this requirement ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 hour, 29 minutes

[Bug 1156421] New: devel:kubic:images: no persistent systemd journal for aarch64/armv7l

by bugzilla_noreply＠novell.com

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.

16 hours, 53 minutes

[Bug 1177358] New: EFI system partition: VFAT or FAT16 or FAT12 or FAT32?

by bugzilla_noreply＠suse.com

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 day, 18 hours

[Bug 1187820] New: VUL-0: CVE-2021-35525: postsrsd: Denial of service (subprocess hang) if Postfix sends certain long data fields

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1187820 Bug ID: 1187820 Summary: VUL-0: CVE-2021-35525: postsrsd: Denial of service (subprocess hang) if Postfix sends certain long data fields Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/303128/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1977067 PostSRSd before 1.11 allows a denial of service (subprocess hang) if Postfix sends certain long data fields such as multiple concatenated email addresses. NOTE: the PostSRSd maintainer acknowledges "theoretically, this error should never occur ... I'm not sure if there's a reliable way to trigger this condition by an external attacker, but it is a security bug in PostSRSd nevertheless." References: https://github.com/roehling/postsrsd/commit/077be98d8c8a9847e4ae0c7dc09e747… https://bugs.gentoo.org/793674 https://github.com/roehling/postsrsd/releases/tag/1.11 References: https://bugzilla.redhat.com/show_bug.cgi?id=1977067 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35525 https://github.com/roehling/postsrsd/releases/tag/1.11 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35525 https://github.com/roehling/postsrsd/commit/077be98d8c8a9847e4ae0c7dc09e747… https://bugs.gentoo.org/793674 -- You are receiving this mail because: You are on the CC list for the bug.

2 days, 3 hours

[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

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.

3 days, 12 hours

[Bug 1083699] New: [Build 148.1] openQA test fails in reboot_icewm

by bugzilla_noreply＠novell.com

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.

6 days, 22 hours

[Bug 1164084] New: Sendmail upstream security bug report

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1164084 Bug ID: 1164084 Summary: Sendmail upstream security bug report Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - Add upstream patch 8.15.2.mci.p0 * If sendmail tried to reuse an SMTP session which had already been closed by the server, then the connection cache could have invalid information about the session. One possible consequence was that STARTTLS was not used even if offered. -- You are receiving this mail because: You are on the CC list for the bug.

6 days, 23 hours

[Bug 1184817] New: Whole system stopped responding and went berserk, first reboot failed

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184817 Bug ID: 1184817 Summary: Whole system stopped responding and went berserk, first reboot failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: teo8976(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I sat at my computer to resume working, woke it up from suspend (I never reboot unless I have to); the previous time I had used everything was working fine. I found it in the following state: - I tried to open a web page in Chrome and it wouldn't load but also wouldn't show any signs of being loading. At first I thought only Chrome was hung - Clicking on application icons of already open applications in the task manager would fail to give focus to them, as if I wasn't even clicking - I could switch focus with alt+tab - in a Terminal, top didn't show any high CPU usage - most applications weren't responding. For example, clicking "get messages" in Thunderbird would do nothing - for a moment I thought the mouse wasn't responding, but it did respond to some events (e.g. selecting text by clicking and dragging; right-click context menu in most applications would show up, but not right-clicking on the task manager) - in a Terminal, I tried to kill some Google Chrome processes ("kill -9 12345" where 12345 was the PID) and either one of the following would happen: (1) the process was still listed, but instead of the full executable path it would read only "[chrome]" and it was listed as "defunct" whatever that means, or (2) nothing at all, that is, the process would keep being listed despite the kill command hadn't given any error - I was unable to launch Firefox and several more instances of nonsensical behavior. I restarted, and the reboot got stuck forever with the spinning icon spinning on top of the very first splash screen (the one with the hardware vendor's logo, i.e. Lenovo). After several minutes waiting I force-powered it down. For a moment I thought OpenSUSE had once more bricked my computer, but after powering it up again, it booted succesfully and everything was working again. This did NOT happen after installing software updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 week

[Bug 1073043] New: Krusader hang when copy or move files

by bugzilla_noreply＠novell.com

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.

1 week

[Bug 1174755] New: virt-install installs openSUSE Tumbleweed aarch64 DVD iso failed.

by bugzilla_noreply＠suse.com

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 week, 1 day

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs August 2021