February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207772] New: mozilla-openh264 doesn't work with Fish default shell
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207772 Bug ID: 1207772 Summary: mozilla-openh264 doesn't work with Fish default shell Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running mozilla-openh264-2.3.1-2.sle150400.1.x86_64 from http://codecs.opensuse.org/openh264/openSUSE_Leap I see that /etc/profile.d/gmpopenh264.sh is not triggered for me, since my default shell is Fish -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 1208510] New: podman/quadlet generating services with wrong podman binary path
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208510 Bug ID: 1208510 Summary: podman/quadlet generating services with wrong podman binary path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: danish.prakash(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reported by bburky: I wanted to test out the new quadlet features so I installed podman-4.4.1-2.1.aarch64 from devel:microos openSUSE_Factory_ARM. I'm seeing the same symptoms as this bug report: Quadlet generating services with wrong podman path https://github.com/containers/podman/issues/17359 When using a *.container file, the quadlet/podman-system-generator generated systemd unit uses /usr/local/bin/podman instead of /usr/bin/podman. The suggested fix (as was applied to Archlinux) seems to be setting PREFIX when calling make. Also, the quadlet feature appears to unconditionally use the crun runtime instead of the default runtime (currently runc), so it may need to be installed too if this feature is used. (Not sure if this is an upstream bug or intentional.) https://github.com/containers/podman/blob/bac20d1917622fa45130427c78231e252… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 1205588] New: Page Fault when booting with PE NX-compatibility DLL Characteristic flag
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205588 Bug ID: 1205588 Summary: Page Fault when booting with PE NX-compatibility DLL Characteristic flag Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am trying the "Page Fault when booting with PE NX-compatibility DLL Characteristic flag" support in openSUSE TW: When PcdDxeNxMemoryProtectionPolicy be set to 0x4 (protect EfiLoaderData) in OVMF, openSUSE TW can not boot. We got a Page Fault: Loading Linux 6.1.0-rc5-default+.old ... Loading initial ramdisk ... !!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!! ExceptionData - 0000000000000011 I:1 R:0 U:0 W:0 P:1 PK:0 SS:0 SGX:0 RIP - 0000000076A6F390, CS - 0000000000000038, RFLAGS - 0000000000210206 RAX - 000000007DA98DF8, RCX - 0000000076A6F390, RDX - 000000007DED3000 RBX - 0000000076A6F000, RSP - 000000007FF0D5A8, RBP - 000000007DED3000 RSI - 000000007F9EE018, RDI - 000000007E7A9718 R8 - 0000000076A6F000, R9 - 0000000000000190, R10 - 000000007FF1D658 R11 - 0000000000000004, R12 - 0000000000000190, R13 - 000000007DA98E00 R14 - 000000007DA936B4, R15 - 000000007BF0CBD5 DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030 GS - 0000000000000030, SS - 0000000000000030 CR0 - 0000000080010033, CR2 - 0000000076A6F390, CR3 - 000000007FC01000 CR4 - 0000000000000668, CR8 - 0000000000000000 DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000 DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400 GDTR - 000000007F9DE000 0000000000000047, LDTR - 0000000000000000 IDTR - 000000007F2E9018 0000000000000FFF, TR - 0000000000000000 FXSAVE_STATE - 000000007FF0D200 !!!! Find image based on IP(0x7BF0BAB5) (No PDB) (ImageBase=000000007BDEB7A0, EntryPoint=000000007C92A0AF) !!!! The same EFI_STUB kernel can direct boot by EFI boot manager with the following boot entry: echo " root=UUID=6ffd1fb1-ddac-4105-a25a-20a602c93e7d showopts console=ttyS0,115200n8 console=tty0 earlyprintk=tty0 debug loglevel=9 efi=debug nomodeset initrd=\EFI\opensuse\initrd-6.1.0-rc5-default+" | \ iconv -f ascii -t ucs2 | efibootmgr -v -cL "vmlinuz-6.1.0-rc5-default+.efi (EFISTUB)" -d /dev/vda -p 1 -l '\EFI\opensuse\vmlinuz-6.1.0-rc5-default+.efi' --append-binary-args - Looks that the Page Fault is in grub2. The grub2 rpm is grub2-x86_64-efi-2.06-31.1.noarch. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1206349] New: guake no longer works in 15.4
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206349 Bug ID: 1206349 Summary: guake no longer works in 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After fresh install of 15.4 the guake program no longer works: $ /usr/bin/guake Guake not running, starting it Loading Gnome schema from: /usr/share/glib-2.0/schemas Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 177, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 363, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.guake3.RemoteControl': no such name During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/guake/main.py", line 451, in main remote_object = bus.get_object(DBUS_NAME, DBUS_PATH) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 243, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python3.6/site-packages/dbus/proxies.py", line 250, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 182, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 280, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.guake3.RemoteControl was not provided by any .service files During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/guake/__init__.py", line 28, in guake_version import importlib.metadata as importlib_metadata ModuleNotFoundError: No module named 'importlib.metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/guake", line 10, in <module> sys.exit(exec_main()) File "/usr/lib/python3.6/site-packages/guake/main.py", line 616, in exec_main if not main(): File "/usr/lib/python3.6/site-packages/guake/main.py", line 467, in main instance = Guake() File "/usr/lib/python3.6/site-packages/guake/guake_app.py", line 123, in __init__ or self.settings.general.get_string("schema-version") != guake_version() File "/usr/lib/python3.6/site-packages/guake/__init__.py", line 30, in guake_version import importlib_metadata ModuleNotFoundError: No module named 'importlib_metadata' -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 1208665] New: restic does not print information when doing backups
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208665 Bug ID: 1208665 Summary: restic does not print information when doing backups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ada.lovelace(a)gmx.de Found By: Community User Blocker: --- When doing backups on s390x, restic only prompts for password, but does not print any more information, regardless of the verbosity. The backup seems to work though. This has been evaluated with restic-0.15.1-0.s390x.rpm. On x86_64, there is quite some additional information by default. The following commands can be used to reproduce: > restic init --repo /tmp/testrepo enter password for new repository: enter password again: created restic repository 49ad167248 at /tmp/testrepo Please note that knowledge of your password is required to access the repository. Losing your password means that your data is irrecoverably lost. > restic -r /tmp/testrepo backup ~/ enter password for repository: > echo $? 0 For those who do not have s390x available, you can reproduce on your local PC like this: zypper in qemu-s390x osc co openSUSE:Factory:zSystems restic cd openSUSE:Factory:zSystems/restic osc build --vm-type qemu --vm-memory=8192 standard s390x osc chroot --vm-type qemu --vm-memory=8192 --noinit standard s390x You will find the package at the usual places. It can be unpacked with rpm2cpio and cpio -id if you want to retrieve the binary. -- You are receiving this mail because: You are on the CC list for the bug.

1 5