October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203794] New: IdeaPad 5 Flex Touch and trackpad not working with kernel 5.19.10 upgrade
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1203794 Bug ID: 1203794 Summary: IdeaPad 5 Flex Touch and trackpad not working with kernel 5.19.10 upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fstrba(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After update to TW snapshot 20220925 from 20220922, the touch-screen and trackpad stopped working on Lenovo IdeaPad 5 Flex (AMD Ryzen with AMD graphics). Booting into kernel 5.19.8 made all work again. I could not yet investigate in details, because it is my son's computer and I had to guide him over whatsapp messages to boot the previous kernel. Fortunately, the keyboard was still working even in the booted environment. But something makes the both pointer devices (touch and trackpad) not to be working. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1203767] New: Backport AMD ACPI processor idle dummy wait fix
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1203767 Bug ID: 1203767 Summary: Backport AMD ACPI processor idle dummy wait fix Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak <kprateek.nayak(a)amd.com> Suggested-by: Rafael J. Wysocki <rafael.j.wysocki(a)intel.com> Signed-off-by: Dave Hansen <dave.hansen(a)linux.intel.com> Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> Tested-by: K Prateek Nayak <kprateek.nayak(a)amd.com> Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.nayak@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.hansen@intel.com git commit e400ad8b7e6a1b9102123c6240289a811501f7d9 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1203505] New: 5.14.21-150400.24.21 failes to boot with hard lock on MSI GS66
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1203505 Bug ID: 1203505 Summary: 5.14.21-150400.24.21 failes to boot with hard lock on MSI GS66 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: onur(a)delipenguen.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861528 --> https://bugzilla.suse.com/attachment.cgi?id=861528&action=edit hard lock Booting 5.14.21-150400.24.21 causes a hard lock on MSI GS66 notebook with the caps lock led blinking and I am not able to do anything. Hard lock always happens. 5.14.21-150400.24.18 works fine, did not have this issue on any of the previous kernels either. I get the same trace on both normal boot and rescue mode boot. I use i915.force_probe=46a6 as extra kernel parameter, removing that does not help, still hard lock. Attached are the photo of trace on hard lock and dmesg output on successful boot with previous kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1202385] New: kernel: debuginfo for vdso*.so should be in a separate file
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202385 Bug ID: 1202385 Summary: kernel: debuginfo for vdso*.so should be in a separate file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As mentioned here: https://sourceware.org/bugzilla/show_bug.cgi?id=29478 and here: https://bugzilla.redhat.com/show_bug.cgi?id=1970578 debuginfod faces serious troubles when it comes to serving a VDSO debug info that is part of every executable. Thus a suggested fix can be putting the vdso a separate kernel-source-userspace package or so. Doing that, debuginfod won't have to search for the file in a huge kernel-default-debuginfo-5.19.0-1.1.x86_64.rpm file compressed with an even slower bzip2 algorithm. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1202187] New: Kernel warning with Samsung SSD
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202187 Bug ID: 1202187 Summary: Kernel warning with Samsung SSD Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After (I think) the 5.14.21-150400.24.11 update, I've started seeing this nvme0: Identify(0x6), Invalid Field in Command (sct 0x0 / sc 0x2) on startup. Found this reference: https://lore.kernel.org/lkml/20220610120554.ry7w37jbf3g6w3p3@quentin/T/ could it be something recently backported? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1201725] New: [Build 6.199] openQA test fails in rename10: exfat returns EINVAL instead of ENAMETOOLONG
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201725 Bug ID: 1201725 Summary: [Build 6.199] openQA test fails in rename10: exfat returns EINVAL instead of ENAMETOOLONG Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2474113/modules/rena me10/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: chrubis(a)suse.com, petr.vorel(a)suse.com Found By: openQA Blocker: No The LTP rename10 test fails: tst_test.c:1599: TINFO: Testing on exfat tst_test.c:1065: TINFO: Formatting /dev/loop0 with exfat opts='' extra opts='' rename10.c:32: TFAIL: rename(TEMP_FILE, long_path) expected ENAMETOOLONG: EINVAL (22) ## Observation openQA test in scenario opensuse-15.4-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@USBboot_aarch64 fails in [rename10](https://openqa.opensuse.org/tests/2474113/modules/rename10/steps/… ## Test suite description ## Reproducible Fails since (at least) Build [6.178](https://openqa.opensuse.org/tests/2417475) ## Expected result Last good: [6.176](https://openqa.opensuse.org/tests/2416374) (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 22

[Bug 1106751] New: iptables does not work with kernel-default-base
by bugzilla_noreply＠novell.com 23 Dec '22

23 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1106751 Bug ID: 1106751 Summary: iptables does not work with kernel-default-base Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initially reported as https://github.com/kubic-project/automation/pull/474#issuecomment-417329301 Docker (and cri-o) do not work in Kubic VM images as iptables does not work: g47:~ # iptables -L iptables: No chain/target/match by that name. -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 1182976] New: Keyboard with multiple layouts not honoured on login
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182976 Bug ID: 1182976 Summary: Keyboard with multiple layouts not honoured on login Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: geoff(a)streeter.gr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I run a US layout and an APL layout. On reboot (after an update) I only see the US layout System Settings|input devices|Advanced and change the key I use for "Menu". Change it back again and Apply. Now all OK Do this for each user. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203425] New: gvfs-backend-samba not installed, needed for SMB support in gnome files
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203425 Bug ID: 1203425 Summary: gvfs-backend-samba not installed, needed for SMB support in gnome files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: pranav.sharma.ama(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- without the package installed, gnome files will fail with an error saying it can't mount an smb share, forcing the user to install with t-u. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202875] New: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202875 Bug ID: 1202875 Summary: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: michal.vyskocil(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- packagekitd won't start on my MicroOS GNOME Desktop and produces error messages in Gnome Software. NAME="openSUSE Tumbleweed" # VERSION="20220827" packagekitd[28073]: what(): Can't load plugin "txnupd.so": Can't load shared library "/usr/lib64/libdnf/plugins/txnupd.so": /usr/lib64/libdnf/plugins/txnupd.so: undefined symbol: _ZN19TransactionalUpdate11Transaction4initENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE It looks like this commit https://github.com/openSUSE/transactional-update/commit/2a2117d15a87dfbedea… broke the ABI. Not sure why BuildService haven't solved the problem by rebuilding the package. What libtukit.so.4 provides (I run my setup inside distrobox, hence /run/host paths poiting to the "host" - the MicroOS itself) objdump -C -T /run/host/lib64/libtukit.so.4.0.0 | grep 'Transaction::init' 0000000000020010 g DF .text 0000000000000c7f Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >) What txnupd requires objdump -C -T /run/host/lib64/libdnf/plugins/txnupd.so | grep 'Transaction::init' 0000000000000000 DF *UND* 0000000000000000 Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) $ rpm -qf /lib64/libdnf/plugins/txnupd.so /lib64/libtukit.so.4.0.0 libdnf-plugin-txnupd-0.1.3-1.10.x86_64 libtukit4-4.0.1-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3