June 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185077] New: Screen locker is broken and unlocking is not possible anymore
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1185077 Bug ID: 1185077 Summary: Screen locker is broken and unlocking is not possible anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The screen locker is broken and unlocking is not possible anymore. in order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in and execute the command: loginctl unlock-session 2 Afterwards switch back to the running session (Ctrl+Alt+F2) cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20210418" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20210418" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20210418" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo" uname -a Linux my-opensuse 5.11.15-1-default #1 SMP Fri Apr 16 16:47:34 UTC 2021 (64fb5bf) x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep ksc kscreen5-5.21.4-1.1.x86_64 kscreen5-lang-5.21.4-1.1.noarch libkscreen2-plugin-5.21.4-1.1.x86_64 kscreenlocker-lang-5.21.4-1.2.noarch kscreenlocker-5.21.4-1.2.x86_64 kscreen5-plasmoid-5.21.4-1.1.x86_64 kdeinit5 --version Qt: 5.15.2 KDE: 5.81.0 lscpu | grep Model Model: 142 Model name: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics 640 (rev 06) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[opensuse-bugs] [Bug 1178989] New: Multiboot and multiboot2 is supported with Grub2?
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1178989 Bug ID: 1178989 Summary: Multiboot and multiboot2 is supported with Grub2? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi OpenSUSE team, One question: Multiboot and multiboot2 is supported with Grub2? Example: menuentry 'Boot OS from multiboot2' { insmod part_gpt insmod ext2 echo 'Loading OS ...' multiboot2 /boot/os.bin module2 /boot/kernel4os-part1 xxxxxx $(os1 bootargs) module2 /boot/kernel4os-part2 yyyyyy $(os2 bootargs) } Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1175310] New: [Build 20200814] sshd segfault detected
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1175310 Bug ID: 1175310 Summary: [Build 20200814] sshd segfault detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I observed issue with sshd process. [ 8843.662719] show_signal_msg: 17 callbacks suppressed [ 8843.662721] sshd[4304]: segfault at 2f8 ip 0000559d32402543 sp 00007ffcdba998d0 error 4 in sshd[559d323c0000+74000] [ 8843.662726] Code: 1f 84 00 00 00 00 00 48 85 ff 0f 84 d7 00 00 00 41 54 55 48 89 fd 48 83 ec 08 48 8b 87 20 01 00 00 48 85 c0 0f 84 95 00 00 00 <8b> 40 18 a8 02 75 46 a8 04 0f 85 8e 00 00 00 48 8b 7d 08 e8 15 f0 ... [62657.009387] perf: interrupt took too long (4995 > 4990), lowering kernel.perf_event_max_sample_rate to 40000 [82262.104123] sshd[19593]: segfault at 418 ip 000055bb76f51543 sp 00007ffc0097d0e0 error 4 in sshd[55bb76f0f000+74000] [82262.104157] Code: 1f 84 00 00 00 00 00 48 85 ff 0f 84 d7 00 00 00 41 54 55 48 89 fd 48 83 ec 08 48 8b 87 20 01 00 00 48 85 c0 0f 84 95 00 00 00 <8b> 40 18 a8 02 75 46 a8 04 0f 85 8e 00 00 00 48 8b 7d 08 e8 15 f0 # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20200814" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200814" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20200814" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" # uname -a Linux os1 5.7.12-1.g9c98feb-default #1 SMP Sat Aug 1 06:18:58 UTC 2020 (9c98feb) x86_64 x86_64 x86_64 GNU/Linux # zypper ls # | Alias | Name | Enabled | GPG Check | Refresh | Type ---+--------------------------------------+--------------------------------------------+---------+-----------+---------+------- 1 | Emulators | Emulators (openSUSE_Tumbleweed) | Yes | (r ) Yes | No | rpm-md 2 | Emulators_Wine | Wine (openSUSE_Tumbleweed) | Yes | (r ) Yes | Yes | rpm-md 3 | Google-Chrome | Google-Chrome | Yes | (r ) Yes | No | NONE 4 | dvd | dvd | Yes | (r ) Yes | Yes | NONE 5 | games | games | Yes | (r ) Yes | No | NONE 6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | rpm-md 7 | home_tiwai_kernel_5.7 | Kernel builds for branch stable (standard) | Yes | (r ) Yes | No | rpm-md 8 | https-download.opensuse.org-412f9ba1 | openSUSE:Factory | Yes | (r ) Yes | Yes | rpm-md 9 | https-download.opensuse.org-49569944 | utilities | Yes | (r ) Yes | Yes | rpm-md 10 | https-download.opensuse.org-589e1d6c | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes | rpm-md 11 | https-download.opensuse.org-7bdb3480 | https-download.opensuse.org-7bdb3480 | Yes | (r ) Yes | Yes | rpm-md 12 | https-download.opensuse.org-ff31ee0b | home:Dead_Mozay | Yes | (r ) Yes | Yes | rpm-md 13 | https-download.opensuse.org-ff3ec87b | devel:languages:go | Yes | (r ) Yes | Yes | rpm-md 14 | mozilla | mozilla | Yes | (r ) Yes | Yes | NONE 15 | openSUSE-20200810-0 | openSUSE-20200810-0 | No | ---- | ---- | rpm-md 16 | packman | packman | Yes | (r ) Yes | Yes | NONE 17 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | NONE 18 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | NONE 19 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | NONE 20 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | NONE 21 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | NONE 22 | snappy | snappy | Yes | (r ) Yes | Yes | NONE 23 | sublime-text | Sublime Text - x86_64 - Stable | Yes | (r ) Yes | Yes | NONE 24 | vscode | vscode | Yes | (r ) Yes | No | NONE # rpm -qa | grep ssh libssh-config-0.9.4-1.3.x86_64 libssh4-0.9.4-1.3.x86_64 libssh2-1-1.9.0-2.4.x86_64 sshfs-3.7.0-1.2.x86_64 ksshaskpass5-5.19.4-1.1.x86_64 ksshaskpass5-lang-5.19.4-1.1.noarch openssh-8.3p1-1.2.x86_64 openssh-helpers-8.3p1-1.2.x86_64 openssh-askpass-gnome-8.3p1-1.1.x86_64 libssh4-32bit-0.9.4-1.3.x86_64 sshpass-1.06-1.11.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1174564] New: vim-small has no /usr/bin/vi link
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1174564 Bug ID: 1174564 Summary: vim-small has no /usr/bin/vi link 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The vim-small package does not provide /usr/bin/vi -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1183247] New: starting lxc container failes with GDBus.Error:org.freedesktop.machine1.NoMachineForPID: PID 4370 does not belong to any known machine
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183247 Bug ID: 1183247 Summary: starting lxc container failes with GDBus.Error:org.freedesktop.machine1.NoMachineForPID: PID 4370 does not belong to any known machine Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: stefan.eisenwiener(a)eisenwiener.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846959 --> http://bugzilla.opensuse.org/attachment.cgi?id=846959&action=edit reduced log with descriped error after Tumbleweed update to 20210307 starting an lxc container failes with GDBus.Error:org.freedesktop.machine1.NoMachineForPID: PID 4370 does not belong to any known machine. -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1172519] New: create_dirs_from_rpmdb needs rpm cookie
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172519 Bug ID: 1172519 Summary: create_dirs_from_rpmdb needs rpm cookie 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- create_dirs_from_rpmdb relies on rpmdbCookie() which is not available on 15. We need some alternate method (or a backport in rpm) on 15 to avoid walking the whole rpmdb on each boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 1173574] New: fwupd Initialize default tcti. ErrorCode (0x000a000a)
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 Bug ID: 1173574 Summary: fwupd Initialize default tcti. ErrorCode (0x000a000a) 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: emiliano.langella(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I noticed the following fwupd errors: # journalctl -u fwupd.service -b -- Logs begin at Thu 2020-04-23 11:28:04 CEST, end at Wed 2020-07-01 09:54:57 CEST. -- Jul 01 09:52:40 kitt systemd[1]: Starting Firmware update daemon... Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: 07:52:43:0646 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initialize> Jul 01 09:52:43 kitt systemd[1]: Started Firmware update daemon. # fwupdate -i failed: Error opening file /sys/firmware/efi/efivars/fwupd-34578c72-11dc-4378-bc7f-b643866f598c-0-0abba7dc-e516-4167-bbf5-4d9d1c739416: No such file or directory Laptop: Dell Precision 5520 Tumbleweed: 20200628 # fwupdmgr --version client version: 1.4.2 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.4.2 Let me know if you need any additional info. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8