October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204150] New: kernel 6.0.0 and nvidia gfxg06 kmp default k5.18.5 => CUDA and OpenCL not running
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204150 Bug ID: 1204150 Summary: kernel 6.0.0 and nvidia gfxg06 kmp default k5.18.5 => CUDA and OpenCL not running Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update of the kernel to 6.0.0, Nvidia CUDA and OpenCL are not running -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203442] Missing Dependencies for dnf and dnf-utils
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203442 http://bugzilla.opensuse.org/show_bug.cgi?id=1203442#c16 --- Comment #16 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- PING. I believe we need to: * revoke SR#1008221 * copy the patchinfo as submitted so this is an optional update * push the incident out * override the qam results on the maintenance release request as there is no original package to install The packages are in the SUSE:SLE-15-SP4:GA tree but not shipped in any product. Therefore they can be included in PackageHub. I think the internal team that set up packagehub for SLE 15 SP4 should check their scripts to avoid dropping packages that are not actually shipped in any product. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202733] New: Open-vm-tools 12.1.0 has been released - please rebase
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1202733 Bug ID: 1202733 Summary: Open-vm-tools 12.1.0 has been released - please rebase 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: jwolfe(a)vmware.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- open-vm-tools 12.1.0 was released on Aug. 23, 2022. This release contains several fixes including: - fix for CVE-2022-31676 - a local privilege escalation vulnerability. - a number of Coverity reported issues have been addressed. - https://github.com/vmware/open-vm-tools/pull/588 - https://github.com/vmware/open-vm-tools/pull/387 For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.1.0 Release Notes are available at: https://github.com/vmware/open-vm-tools/blob/stable-12.1.0/ReleaseNotes.md The granular changes that have gone into the 12.1.0 release are in the ChangeLog at https://github.com/vmware/open-vm-tools/blob/stable-12.1.0/open-vm-tools/Ch… Please rebase open-vm-tools version 12.1.0 in supported releases for x86_64/amd64 and aarch64/ARM64 architectures as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1204148] New: windows:mingw:win{32|64}/mingw{32|64}-cross-binutils-debuginfo: file name clash
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204148 Bug ID: 1204148 Summary: windows:mingw:win{32|64}/mingw{32|64}-cross-binutils-d ebuginfo: file name clash Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- How to reproduce: $ sudo zypper install mingw32-cross-binutils-debuginfo $ sudo zypper install mingw64-cross-binutils-debuginfo ... File /usr/lib/debug/.build-id/2b/668001676ab0e2703f891f1ddc6e91b7375bbc from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) File /usr/lib/debug/.build-id/2b/668001676ab0e2703f891f1ddc6e91b7375bbc.debug from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) File /usr/lib/debug/.build-id/79/f2e8312e050c37e1f382b9d906e93814ce9705 from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) File /usr/lib/debug/.build-id/79/f2e8312e050c37e1f382b9d906e93814ce9705.debug from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) File /usr/lib/debug/.build-id/b1/8fdc7c833f4fe949170d7b6b90f007399edc3d from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) File /usr/lib/debug/.build-id/b1/8fdc7c833f4fe949170d7b6b90f007399edc3d.debug from install of mingw64-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (windows:mingw:win64) conflicts with file from package mingw32-cross-binutils-debuginfo-2.39-lp153.13.2.x86_64 (@System) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203762] New: gnome-terminal does not accept "--profile" option at commandline
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203762 Bug ID: 1203762 Summary: gnome-terminal does not accept "--profile" option at commandline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: berthold-opensuse(a)xn--hllmanns-n4a.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have several profiles defined for my gnome-terminal. With snapshot 20220921 came gnome-terminal 3.46.1, and with this version the --profile option failed to work. I still can open a new tab using the menue, but trying to open a tab with a specific profile fails: > LANG=C gnome-terminal --profile devel # TerminalSettingsList* terminal_settings_list_new(GSettingsBackend*, GSettingsSchemaSource*, const char*, const char*, const char*, TerminalSettingsListFlags): assertion 'schema_source != nullptr' failed # char** terminal_settings_list_dupv_children(TerminalSettingsList*): assertion 'TERMINAL_IS_SETTINGS_LIST (list)' failed # g_strv_length: assertion 'str_array != NULL' failed # Profile 'devel' specified but not found. Attempting to fall back to the default profile. # TerminalSettingsList* terminal_settings_list_new(GSettingsBackend*, GSettingsSchemaSource*, const char*, const char*, const char*, TerminalSettingsListFlags): assertion 'schema_source != nullptr' failed # char* terminal_settings_list_dup_default_child(TerminalSettingsList*): assertion 'TERMINAL_IS_SETTINGS_LIST (list)' failed # char** terminal_settings_list_dupv_children(TerminalSettingsList*): assertion 'TERMINAL_IS_SETTINGS_LIST (list)' failed # g_strv_length: assertion 'str_array != NULL' failed # Failed to parse arguments: No profile with UUID or name "(null)" exists > sudo rpm -qif $(which gnome-terminal) [sudo] Passwort f�r root: Name : gnome-terminal Version : 3.46.1 Release : 1.1 Architecture: x86_64 Install Date: Do 22 Sep 2022 19:46:18 CEST Group : System/X11/Terminals Size : 868326 License : GPL-3.0-or-later AND LGPL-2.1-or-later Signature : RSA/SHA256, Mi 21 Sep 2022 19:22:13 CEST, Key ID b88b2fd43dbdc284 Source RPM : gnome-terminal-3.46.1-1.1.src.rpm Build Date : Mi 21 Sep 2022 19:21:02 CEST Build Host : cloud106 Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://wiki.gnome.org/Apps/Terminal Summary : GNOME Terminal Description : This package provides the GNOME terminal emulator application. Distribution: openSUSE Tumbleweed I cannto think why it should matter, but I am using fvwm2 as window mnager. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1204082] guests with qemu 7.1.0 hang when using iothread and aio=io_uring
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204082 http://bugzilla.opensuse.org/show_bug.cgi?id=1204082#c12 --- Comment #12 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1204082) was mentioned in https://build.opensuse.org/request/show/1008827 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204001] qemu-linux-user 7.1 regression with glibc 2.36
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204001 http://bugzilla.opensuse.org/show_bug.cgi?id=1204001#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1204001) was mentioned in https://build.opensuse.org/request/show/1008827 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203995] File conflict between qemu and qemu-guest-agent: /usr/share/doc/packages/qemu/interop/qemu-ga.html
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203995 http://bugzilla.opensuse.org/show_bug.cgi?id=1203995#c8 --- Comment #8 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1203995) was mentioned in https://build.opensuse.org/request/show/1008827 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186256] qemu-linux-user: hardcoded binfmt handler doesn't play well with containers
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1186256 http://bugzilla.opensuse.org/show_bug.cgi?id=1186256#c25 --- Comment #25 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1186256) was mentioned in https://build.opensuse.org/request/show/1008827 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143725] New: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output)
by bugzilla_noreply＠novell.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1143725 Bug ID: 1143725 Summary: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Context: I want to run an ARM64 (aarch64) container on an x86 host. This is possible using qemu Linux user emulation and Linux binfmt. It is supposed to work like this: //Fetching an ARM container on x86 (long story) $ skopeo --override-arch arm64 copy docker://opensuse/leap docker-daemon:opensuse-arm64/leap:latest //Install qemu Linux user, and setup binfmt for aarch64 # zypper install qemu-linux-user $ cp /usr/bin/qemu-aarch64-binfmt . # echo -1 > /proc/sys/fs/binfmt_misc/qemu-aarch64 # echo ':qemu-aarch64:M:0:\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64-binfmt:POCF' > /proc/sys/fs/binfmt_misc/register //Build our container $ cat << EOF > Dockerfile FROM opensuse-arm64/leap COPY qemu-aarch64-binfmt /usr/bin/qemu-aarch64-binfmt EOF docker build -t qemu-leap . //Now I should be able to run the ARM container, like this: # docker run -it qemu-leap-aarch64-binfmt /bin/sh But, basically, nothing happens. No output at all, and I'm definitely not inside an ARM container. Actually, it appears the container exited: $ docker ps --all CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ea2252caf90a qemu-leap "/bin/sh" 4 seconds ago Exited (255) 3 seconds ago relaxed_goodall Now, if I, instead of qemu-aarch64-binfmt, use a qemu-aarch64-static binary copied from a Debian unstable box I have in my home network, i.e., this one: # ./qemu-aarch64-static -version qemu-aarch64 version 3.1.0 (Debian 1:3.1+dfsg-8) Things work! In fact: $ docker run -it --rm qemu-leap uname -a Linux bf12752f6a51 5.1.16-1-default #1 SMP Wed Jul 3 12:37:47 UTC 2019 (2af8a22) aarch64 aarch64 aarch64 GNU/Linux Note the *aarch64*. Of course, we need to change the aarch64 interpreter file too, in /proc/sys/fs/binfmt So, basically, it looks like the procedure is correct, or at least can work. But our qemu-linux-user packages contain binaries that are not adequate for being used for this use case. Things/differences to check: - QEMU version (the debian stolen from Debian, that makes things works is from QEMU 3.1.0, while we ship 4.0.0 - our patch queue - our configuration and compile options -- You are receiving this mail because: You are on the CC list for the bug.

2 10