May 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199210] New: Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 incompatibility
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199210 Bug ID: 1199210 Summary: Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 incompatibility Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: jphands(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- About 21 days ago, I reported a bug ( https://bugzilla.mozilla.org/show_bug.cgi?id=1764436 ) to the FireFox team, after a Tumbleweed update caused FireFox to stop playing some video content. Other browsers like Brave or Opera worked just fine, leading me to suspect Firefox. I worked with the FF team to run various tests and their eventual resolution is "wontfix" because the problem actually seems to be some packaging issue with FFMPEG and OPeH264...perhaps a version mismatch. One of the FF developers said "To fix the problem, you need to install the exact same version of https://software.opensuse.org/package/libopenh264-6 that was used to build OpenSuse's ffmpeg-5." The mozilla bug link above gives the full story. I have been unable to get Firefox to play video content, no matter what combination of FFMPEG and Openh264 I've tried, but this area isn't my strength. The FF people recommended that I open a bug with Tumbleweed, and perhaps together, the bug can be resolved. I'm available for any testing or experiments...just let me know. ==========================MACHINE INFO========================================== Operating System: openSUSE Tumbleweed 20220503 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 24 � AMD Ryzen 9 3900X 12-Core Processor Memory: 47.0 GiB of RAM Graphics Processor: AMD DIMGREY_CAVEFISH -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1196618] New: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1196618 Bug ID: 1196618 Summary: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2218590/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: openQA Blocker: Yes Leap 15.4: https://openqa.opensuse.org/tests/2218590#step/journal_check/10 Tumbleweed: https://openqa.opensuse.org/tests/2218201#step/journal_check/10 This does not always happen, e.g.: https://openqa.opensuse.org/tests/2192626 ## Observation openQA test in scenario opensuse-15.4-JeOS-for-RPi-aarch64-jeos@RPi4 fails in [journal_check](https://openqa.opensuse.org/tests/2218590/modules/journal_ch… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [5.1](https://openqa.opensuse.org/tests/2076851) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1197256] New: VUL-0: CVE-2021-23556: guake: possible command injection through dbus interface
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197256 Bug ID: 1197256 Summary: VUL-0: CVE-2021-23556: guake: possible command injection through dbus interface Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/326571/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: badshah400(a)gmail.com Reporter: thomas.leroy(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-23556 The package guake before 3.8.5 are vulnerable to Exposed Dangerous Method or Function due to the exposure of execute_command and execute_command_by_uuid methods via the d-bus interface, which makes it possible for a malicious user to run an arbitrary command via the d-bus method. **Note:** Exploitation requires the user to have installed another malicious program that will be able to send dbus signals or run terminal commands. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-23556 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23556 https://github.com/Guake/guake/pull/2017/commits/e3d671120bfe7ba28f50e256cc… https://github.com/Guake/guake/releases https://github.com/Guake/guake/pull/2017 https://github.com/Guake/guake/issues/1796 https://snyk.io/vuln/SNYK-PYTHON-GUAKE-2386334 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1191924] New: kernel-source.git/README outdated
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1191924 Bug ID: 1191924 Summary: kernel-source.git/README outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a section "Before You Commit -- Things To Check" in kernel-source.git/README, it will likely not work out of the box. According to rpm/kernel-binary.spec.in, at least three more packages beside the obvious gcc/make/patch need to be installed: BuildRequires: libopenssl-devel BuildRequires: libelf-devel BuildRequires: dwarves >= 1.21 Furthermore rapidquilt is not mentioned. It is not strictly required, but one can hardly live without it. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1184490] New: mame creates a cfg directory in PWD instead of ~/.mame and ignoring ~/.mame/cfg
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1184490 Bug ID: 1184490 Summary: mame creates a cfg directory in PWD instead of ~/.mame and ignoring ~/.mame/cfg Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ilya(a)ilya.pp.ua QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating mame to 0.226, mame started ignoring the configuration directory ~/.mame/cfg/ and started creating it in PWD, i.e. the directory where mame runs from (~/ if you run mame via the menu). In 0.229 nothing has changed. In 0.211 it was no problem. To reproduce, just run "cd /tmp && mame", wait for mame to load the interface, then press Esc to quit mame, and then check /tmp "ls -lah /tmp | grep cfg". -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1047218] New: trackerbug: packages do not build reproducibly from including build time
by bugzilla_noreply＠novell.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1047218 Bug ID: 1047218 Summary: trackerbug: packages do not build reproducibly from including build time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: SUSE Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://reproducible-builds.org/specs/source-date-epoch/ When packages include the current time of build it results in binaries that differ on every build and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 30

[Bug 1131931] New: OCFS2: Defragmentation error: No space left on device
by bugzilla_noreply＠novell.com 07 Apr '23

07 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1131931 Bug ID: 1131931 Summary: OCFS2: Defragmentation error: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: weikai.wang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 802412 --> http://bugzilla.suse.com/attachment.cgi?id=802412&action=edit this script is used to generate disk framentation when I used the defragfs.ocfs2 to clean up disk fragmentation that generated by the attached shell script. you could execute the scrip by command "./defragfs_test.sh -d DEVICE -m MOUNT_POINT -n CLUSTER_NAME -s pcmk -o /tmp" You should use the device on your cluster replace DEVICE, use the same way replace MOUNT_POINT and CLUSTER_NAME. Then use the command defragfs.ocfs2 MOUNT_POINT. And if no accident, you will see some message like this: “ defragfs.ocfs2 1.8.5 [1/201]/mnt/ocfs2/tmp_file:Success [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd1" - No space left on device [2/201]/mnt/ocfs2/test_from_dd1:Failed [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd2" - No space left on device [3/201]/mnt/ocfs2/test_from_dd2:Failed [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd3" - No space left on device ” but if you execute defragfs.ocfs2 MOUNT_POINT again, the error message will not show again. and all the defragmentation will pass. please make sure your device's capacity is more tha 1G. Some times this error can make mount, unmount, and mkfs crushed. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1199184] New: switch Tumbleweed to a 4096bit RSA signing key
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1199184 Bug ID: 1199184 Summary: switch Tumbleweed to a 4096bit RSA signing key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dimstar(a)opensuse.org Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com Found By: --- Blocker: --- We currently still use a 2048 bit key for signing. It would be better to switch to a 4096 RSA key. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1182998] New: libcontainers-common seems to miss prerequires
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1182998 Bug ID: 1182998 Summary: libcontainers-common seems to miss prerequires Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are several errors during initial installation of libcontainers-common. As result, the configuration is broken and podman not correct working: # 2021-03-04 05:56:10 libcontainers-common-20210112-2.1.noarch.rpm installed ok # Additional rpm output: # /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found # /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found # 2021-03-04 05:56:10|install|libcontainers-common|20210112-2.1|noarch||openSUSE-MicroOS-20210302-0|867c95e8e8cd2e09046dc327b743e9134c6072146f59c6f3b357b0e92420b494| # 2021-03-04 05:56:10 openssh-8.4p1-4.1.x86_64.rpm installed ok # Additional rpm output: # find: '/etc/init.d/rc[35].d': No such file or directory # -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1155207] New: systemctl command line completion is very slow
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1155207 Bug ID: 1155207 Summary: systemctl command line completion is very slow Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- systemctl command line completion is very slow Suppose I type: systemctl status smart[tab][tab] and I get nothing. One second, two seconds... so I insist and hit tab several times, and after several seconds I get (one line per second): Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart and then I can type "d" and enter. Why is it that slow? It is an M2 disk. ie, SSD technology. It responds instantly when completing a normal command: Isengard:~ # smart smart_agetty smartctl smartd Isengard:~ # smart And that system is not busy at all, load 0.20. I can replicate the issue on other machines, and has been so probably for a year or so. Google "systemctl completion slow" finds reports on other distributions and several media. <https://bugzilla.redhat.com/show_bug.cgi?id=1491668> <https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1471723> and: <https://github.com/systemd/systemd/issues/7185> -- You are receiving this mail because: You are on the CC list for the bug.

2 2