September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1202330] [Build 20220810] openQA test fails in fanotify10
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202330 https://bugzilla.suse.com/show_bug.cgi?id=1202330#c6 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #6 from Jan Kara <jack(a)suse.com> --- I can see my fix has been merged to upstream LTP repository on Aug 28 as commit 48cfd7a9977e ("syscalls/fanotify10: Make evictable marks test more reliable"). Looking at openQA log it already seems to be using LTP as of commit 14e31797926a which happened after that so it should indeed contain the fix. Hrm... needs more poking... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203162] VUL-0: CVE-2021-3427: deluge: XSS in webui via crafted torrent file
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203162 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202330] New: [Build 20220810] openQA test fails in fanotify10
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202330 Bug ID: 1202330 Summary: [Build 20220810] openQA test fails in fanotify10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2508855/modules/fano tify10/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:538: TFAIL: group 0 (4) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 1 (4) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 2 (4) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 0 (0) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 1 (0) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 2 (0) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 0 (e00) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 1 (e00) with FAN_MARK_MOUNT did not get event fanotify10.c:538: TFAIL: group 2 (e00) with FAN_MARK_MOUNT did not get event fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:340: TFAIL: Unexpected inode mark (mflags=240, mask=8000020 ignored_mask=20) fanotify10.c:538: TFAIL: group 0 (4) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 1 (4) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 2 (4) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 0 (0) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 1 (0) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 2 (0) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 0 (e00) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 1 (e00) with FAN_MARK_FILESYSTEM did not get event fanotify10.c:538: TFAIL: group 2 (e00) with FAN_MARK_FILESYSTEM did not get event Failed. Test took approximately 3.23233270202763 seconds Some test output could not be parsed: 14 lines were ignored. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fanotify10](https://openqa.opensuse.org/tests/2508855/modules/fanotify10/st… ## Test suite description ## Reproducible Fails since (at least) Build [20220810](https://openqa.opensuse.org/tests/2508674) ## Expected result Last good: [20220809](https://openqa.opensuse.org/tests/2507021) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1054029] VUL-0: CVE-2017-12877: ImageMagick: use-after-free in DestroyImage (mat.c)
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

1 0

[Bug 1202707] kernel-firmware-{amdgpu,radeon} update breaks VA-API: Incorrect video output on Radeon RX 6900 (Navi 21/CHIP_SIENNA_CICHLID)
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202707 https://bugzilla.suse.com/show_bug.cgi?id=1202707#c37 --- Comment #37 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks, then I'm going to update the package with the reference to this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201770] VUL-0: CVE-2014-9862: libostree: bundled bsdiff Improper checking of input allows arbitrary write on heap
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1201770 https://bugzilla.suse.com/show_bug.cgi?id=1201770#c11 --- Comment #11 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3094-1: An update that fixes one vulnerability is now available. Category: security (important) Bug References: 1201770 CVE References: CVE-2014-9862 JIRA References: Sources used: openSUSE Leap 15.4 (src): libostree-2021.6-150400.3.3.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): libostree-2021.6-150400.3.3.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): libostree-2021.6-150400.3.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199740] Deja Dup's Google support will break in September 2022 for versions < 43.3
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199740 https://bugzilla.suse.com/show_bug.cgi?id=1199740#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:3097-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1199740 CVE References: JIRA References: Sources used: openSUSE Leap 15.3 (src): deja-dup-40.6-150200.2.7.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): deja-dup-40.6-150200.2.7.1 SUSE Linux Enterprise Module for Packagehub Subpackages 15-SP3 (src): deja-dup-40.6-150200.2.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202707] kernel-firmware-{amdgpu,radeon} update breaks VA-API: Incorrect video output on Radeon RX 6900 (Navi 21/CHIP_SIENNA_CICHLID)
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202707 https://bugzilla.suse.com/show_bug.cgi?id=1202707#c36 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(reiokorn@tutanota | |.com) | --- Comment #36 from Stefan Dirsch <sndirsch(a)suse.com> --- Takashi, I verified that AMD checked in the same file into git as they provided to our reporter for testing in the issue tracker. Same size, same sha256 checksum. So I think we're on the safe side. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202707] kernel-firmware-{amdgpu,radeon} update breaks VA-API: Incorrect video output on Radeon RX 6900 (Navi 21/CHIP_SIENNA_CICHLID)
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202707 https://bugzilla.suse.com/show_bug.cgi?id=1202707#c35 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(reiokorn@tutanota | |.com) --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- There is an update in the upstream firmware tree. Could you check whether it fixes your problem? https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c39 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(teo8976(a)gmail.com | |) --- Comment #39 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to teo teo from comment #38) > > The fact that web browser doesn't open > > That's never happened to me. The browser (which is already open and I've > been using for a while) stops responding (meaning I'm unable to switch > between tabs, and/or close tabs, and/or scroll, and/or etc.), but when I > close it and relaunch it it opens immediately, and usually works for a > while. And the same with other applications. Well, that's what I meant -- the unstable behavior of the web browser (or whatever). > > When the problem happens, and when you unplug the USB Ethernet device (instead of power-off / reset), does the problem persist? > > Yes. And what if you logout and re-login? The problem persists? If it's a kernel problem, it should persist. Also it should persist on the another user, too. In anyway, we need a way to verify the buggy behavior with a more simpler application than web browser or those heavy & complex beast. If you can find some issue with a simple command-line application (just does some network access or anything), it can be used for analyzing better what's going on. Once after we find out a simpler test case, we can take a deeper look at the system level via performance monitoring or tracing. And another thing is to try solving the IRQ 9 problem. If you have no BIOS update available, at least try irqpoll boot option to see whether the error message is gone or not. -- You are receiving this mail because: You are on the CC list for the bug.

1 0