February 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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 1191975] New: Fwupd assertion fails, causing coredump
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191975 Bug ID: 1191975 Summary: Fwupd assertion fails, causing coredump Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rawat.arnav(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The error at the end makes no difference, the coredump still occurs when tpm2-0-tss and tpm2.0-abrmd are instaled. I don't know what could cause these asserts to fail. Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Oct 22 19:12:12 linux systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1192066] New: fwupd.service failes to start
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192066 Bug ID: 1192066 Summary: fwupd.service failes to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: patric.schramm(a)rub.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed fwup today but i cannot start the system via systemctl start. Error log from systemd: Okt 27 11:00:03 localhost.localdomain systemd[1]: Starting Firmware update daemon... �� Subject: A start job for unit fwupd.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit fwupd.service has begun execution. �� The job identifier is 4816. Okt 27 11:00:03 localhost.localdomain systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit fwupd.service has exited. �� The process' exit code is 'dumped' and its exit status is 11. Okt 27 11:00:03 localhost.localdomain systemd[1]: fwupd.service: Failed with result 'core-dump'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit fwupd.service has entered the 'failed' state with result 'core-dump'. Okt 27 11:00:03 localhost.localdomain systemd[1]: Failed to start Firmware update daemon. �� Subject: A start job for unit fwupd.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit fwupd.service has finished with a failure. �� The job identifier is 4816 and the job result is failed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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

[Bug 1194202] New: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header)
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194202 Bug ID: 1194202 Summary: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header) 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: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- PE images have a timestamp in the header: https://blog.beuc.net/posts/Practical_basics_of_reproducible_builds_2/ Debian has some patches to use SOURCE_DATE_EPOCH instead of the current time: https://salsa.debian.org/mingw-w64-team/binutils-mingw-w64/-/blob/master/de… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 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: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1168405] New: adjust issue handling to new agetty
by bugzilla_noreply＠novell.com 20 Dec '22

20 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1168405 Bug ID: 1168405 Summary: adjust issue handling to new agetty 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- agetty from util-linux 2.35 (not yet packaged) supports reading issue files from /run and /usr in the following way: if /etc/issue exists: read /etc/issue and /etc/issue.d else if /run/issue exists or /run/issue.d has any files read those else read /usr/lib/issue read /usr/lib/issue.d Moreover, the \4 and \6 escape codes use the first configured interface to print the IP address. That means for the most useful default case we don't need to run the extra code of issue generator to enumerate network interfaces and merge issue files anymore. We can rely on agetty built-in features only. Those who need the extra features to print ssh keys or custom computed stuff could still install issue-generator. So I propose the following change: - don't hard require issue-generator in openSUSE-release - don't ship /etc/issue - ship /usr/lib/issue.d/10-openSUSE.issue with the following content: Welcome to \S{PRETTY_NAME} \S{VERSION_ID} - Kernel \r (\l). \4 \6 -- You are receiving this mail because: You are on the CC list for the bug.

2 5