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

[Bug 1206745] New: Unnecessary log entries for rtkit
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206745 Bug ID: 1206745 Summary: Unnecessary log entries for rtkit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jimoe(a)sma-inc.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed 20221222 The system log has many entries (generally tens per day, grouped in bunches of 5 - 30) like this: 2022-12-29T06:30:59-0700 sma-station14l rtkit-daemon[7852]: Supervising 0 threads of 0 processes of 0 users. Is this really necessary? It is merely saying it has nothing to do. -- 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 1207730] New: vncserver requires dbus-1-x11
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207730 Bug ID: 1207730 Summary: vncserver requires dbus-1-x11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: christian.smietana(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- VNC connection using the vncserver script included in xorg-x11-Xvnc works only when dbus-1-x11 is installed. Otherwise the vnc client shows only a black screen. Steps to reproduce: 1. Make a minimal installation of OpenSUSE. In the installer, select the following components: patterns: only "X Window system" additional packages: xorg-x11-essentials, xorg-x11-Xvnc, icewm recommended packages: off Make sure that dbus-1-x11 isn't installed. 2. Start the system, open xterm, run "vncserver". Try to connect via VNC client. -> connection is possible, but only a black screen shows up. 3. Stop vncserver (run "vncserver -kill :1"). Install "dbus-1-x11". 4. Start vncserver, connect again via VNC client: -> works -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1200441] New: go1.19 release tracking
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1200441 Bug ID: 1200441 Summary: go1.19 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.19 (expected August 2022) is a major release of Go. Minor releases of go1.19.x will be provided through August 2023. This issue tracks go1.19.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1205667] New: VUL-0: CVE-2021-44758: heimdal -- security update
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205667 Bug ID: 1205667 Summary: VUL-0: CVE-2021-44758: heimdal -- security update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/348699/ 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: --- openSUSE:Backports and openSUSE:Factory only. CVE-2021-44758 Several vulnerabilities were discovered in Heimdal, an implementation of Kerberos 5 that aims to be compatible with MIT Kerberos. CVE-2021-3671 Joseph Sutton discovered that the Heimdal KDC does not validate that the server name in the TGS-REQ is present before dereferencing, which may result in denial of service. CVE-2021-44758 It was discovered that Heimdal is prone to a NULL dereference in acceptors where an initial SPNEGO token that has no acceptable mechanisms, which may result in denial of service for a server application that uses SPNEGO. CVE-2022-3437 Several buffer overflow flaws and non-constant time leaks were discovered when using 1DES, 3DES or RC4 (arcfour). CVE-2022-41916 An out-of-bounds memory access was discovered when Heimdal normalizes Unicode, which may result in denial of service. CVE-2022-42898 It was discovered that integer overflows in PAC parsing may result in denial of service for Heimdal KDCs or possibly Heimdal servers. CVE-2022-44640 It was discovered that the Heimdal's ASN.1 compiler generates code that allows specially crafted DER encodings to invoke an invalid free on the decoded structure upon decode error, which may result in remote code execution in the Heimdal KDC. For the stable distribution (bullseye), these problems have been fixed in version 7.7.0+dfsg-2+deb11u2. We recommend that you upgrade your heimdal packages. For the detailed security status of heimdal please refer to its security tracker page at: https://security-tracker.debian.org/tracker/heimdal References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44758 https://security-tracker.debian.org/tracker/DSA-5287-1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996586 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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

[Bug 1207419] New: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207419 Bug ID: 1207419 Summary: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: fvogt(a)suse.com Reporter: aherzig(a)suse.com QA Contact: jsrain(a)suse.com CC: vmoutoussamy(a)suse.com Found By: Development Blocker: --- The dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package, to be addressed. spec file requires wicked and needs adaptation to also work with networkmanager if it is installed (and not wicked), configurable or detected on run-time -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1159528] New: keybase client package is extremely outdated, plus lacks all gui elements
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1159528 Bug ID: 1159528 Summary: keybase client package is extremely outdated, plus lacks all gui elements Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the keybase package that comes packaged in openSUSE Leap 15.1 is outdated... to the ponit of being a prehistoric artefact: bundled comes version 2.11 - current from keybase.io is 5.1.1.... also, it lacks all gui elements - probably because it is such an old version. please update to the latest version. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1126900] New: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system.
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1126900 Bug ID: 1126900 Summary: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From a health-checker run: Clearing GRUB flag + grub2-editenv - set health_checker_flag=0 grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Starting health check -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1194160] New: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic"
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194160 Bug ID: 1194160 Summary: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Upgrading from Leap 15.2 to 15.3 via "zypper dup" showed this error message: (4328/5706) Installing: texlive-tex-gyre-fonts-2017.134.2.004svn18651-5.18.noarch .....[done] Additional rpm output: Unknown Type 1 weight "BoldItalic" Couldn't determine weight for qcsbi.pfb -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1204746] New: texlive-scheme-medium missing english documentation for fancyhdr
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204746 Bug ID: 1204746 Summary: texlive-scheme-medium missing english documentation for fancyhdr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lukasstraub2(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing texlive-scheme-medium, it includes documentation, but for example for fancyhdr only the italian docs are included, not the english ones. i.e. only texlive-fancyhdr-it is installed, not texlive-fancyhdr-doc. I suspect this is not the only package that has this problem. I expect at least english documentation to be installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1208289] New: [distrobox] cannot enter a container
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208289 Bug ID: 1208289 Summary: [distrobox] cannot enter a container Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just run (distrobox is 1.4.2.1 from TW): $ distrobox create paperino $ distrobox enter paperino and in the podman logs I found this piece of wisdom: Resolving package dependencies... Problem: the to be installed util-linux-systemd-2.38.1-6.1.x86_64 requires 'which', but this requirement cannot be provided not installable providers: which-2.21-5.7.i586[repo-oss] which-2.21-5.7.x86_64[repo-oss] Solution 1: deinstallation of busybox-which-1.36.0-26.1.noarch Solution 2: do not install util-linux-systemd-2.38.1-6.1.x86_64 Solution 3: break util-linux-systemd-2.38.1-6.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Error: An error occurred Obviously entering errored in ��Installing basic packages��. -- You are receiving this mail because: You are on the CC list for the bug.

1 5