openSUSE Bugs August 2021

bugs@lists.opensuse.org

1 participants
3128 discussions

[Bug 1176026] New: bond interface should not invent mac address by default
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1176026 Bug ID: 1176026 Summary: bond interface should not invent mac address by default 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since 5.8.4 (unsure about last digit): when setting up a bond if kernel chooses a random mac removing and readding the slave gets back to the used behaviour: obs-arm-1:~ # modprobe bonding 3: enP2p1s0v1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo -enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1182554] New: cannot start greetd.service .... missing PAM module
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1182554 Bug ID: 1182554 Summary: cannot start greetd.service .... missing PAM module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: denis.kondratenko(a)suse.com, mcepl(a)suse.com, opensuse(a)trummer.xyz, stdden(a)opensuse.org Found By: --- Blocker: --- Created attachment 846366 --> https://bugzilla.suse.com/attachment.cgi?id=846366&action=edit journalctl -xb output When trying to replace gdm with greetd following the steps on https://en.opensuse.org/Portal:OpenSUSEway, greetd fails to start and journal shows: �no 22 09:38:10 stitny greetd[2347]: error: PAM 'greetd' service missing When looking around, there is the file /usr/etc/pam.d/greetd with this content: ~@stitny$ cat /usr/etc/pam.d/greetd #%PAM-1.0 auth requisite pam_nologin.so auth include common-auth account include common-account password include common-password session required pam_loginuid.so session optional pam_keyinit.so force revoke session include common-session ~@stitny$ but I have still /etc/pam.d/ as well and there is no greetd file. Which one is used? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1188589] New: libbpf: failed to find valid kernel BTF
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188589 Bug ID: 1188589 Summary: libbpf: failed to find valid kernel BTF 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: mrostecki(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update to the TW snapshot with the kernel 5.13.2-1, I see the following errors when trying to load BPF CO-RE skeletons with libbpf: libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 The full example - I'm trying to load BPF programs which I have in this project: https://github.com/rancher-sandbox/lockc and the full output is: �� sudo ./out/lockcd libbpf: elf: skipping unrecognized data section(9) .rodata.str1.1 libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 libbpf: failed to load object 'lockc_bpf' libbpf: failed to load BPF skeleton 'lockc_bpf': -3 Error: libbpf error Caused by: System error, errno: 3 Most likely, the solution for them would be setting the following kernel parameters to "y": CONFIG_DEBUG_INFO_REDUCED CONFIG_DEBUG_INFO_SPLIT But I'm not entirely sure yet. trying to test that... -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1188949] New: The wired connection stops connecting the next day after installation
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188949 Bug ID: 1188949 Summary: The wired connection stops connecting the next day after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: vladislavmil(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851456 --> http://bugzilla.opensuse.org/attachment.cgi?id=851456&action=edit NetworkManager logs, inxi-Fxz output, video and photo with error demonstration After installation, the wired connection works correctly. The next day, it stops connecting. There is a network connection that lasts indefinitely. Creating new connections does not lead to any result, as does trying to reconnect to an existing connection. It only helps to roll back the system to the backup created immediately after installation. The bug manifests itself on all DE and the next day after installation. During installation, the system configures the wired connection itself and the installation takes place without any errors. The problem manifests itself in openSUSE Leap and Tumbleweed, the wired connection works correctly on other distributions. I tried to install the r8168 driver, and add r8169 to the blacklist, but this does not help. Installing a third-party custom kernel also does not fix the problem. IPv4, IPv6, DNS and the default route disappear from the connection settings. I looked at the Network Manager configs, but there is nothing suspicious there, because of which the problem could manifest itself. -- You are receiving this mail because: You are on the CC list for the bug.

1 45

[Bug 1189993] New: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6)
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189993 Bug ID: 1189993 Summary: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852174 --> https://bugzilla.suse.com/attachment.cgi?id=852174&action=edit dmesg, SysRq-L, perf data, lsblk -f, snapper list My CPU fan had a long high-intensity exercise this morning. The root cause turned out to be a kworker thread doing "btrfs_preempt_reclaim_metadata_space". The offending thread identification is "kworker/u16:11". I've collected some data bits (dmesg, SysRq-L, perf data) during the event. It is unclear to me, however, what triggered this long-running FS maintenance and how I could stop it in case I needed to - i.e. if the laptop ran battery or if I sat in a quiet room where the CPU fan disturbance would be unacceptable. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1189881] New: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189881 Bug ID: 1189881 Summary: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-defaul t not available 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running zypper dup on my Tumbleweed machine, I noticed the following in the logs: (121/203) Installing: kernel-default-5.13.12-2.1.x86_64 ....[done] Additional rpm output: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available It is probably benign, but still a bit confusing/worrisome. What do we want to tell users here (that would be actionable)? And/or is this indicative of some problem with the upgrade as such? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1187510] New: Display crashes on RPI 4B with Gnome/Wayland
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187510 Bug ID: 1187510 Summary: Display crashes on RPI 4B with Gnome/Wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: David(a)WalkerStreet.info QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- The HDMI-connected display on my RPI 4B frequently becomes unresponsive. The system continues to run, however, and using ssh to connect and "sudo systemctl restart display-manager" will restore the display (after logging the session out, of course). These occurrences are accompanied by the following log records. Jun 16 10:14:10 rpi4a.WalkerStreet.info kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:66:crtc-3] flip_done timed out Jun 16 10:14:10 rpi4a.WalkerStreet.info kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:66:crtc-3] flip_done timed out Jun 16 10:14:20 rpi4a.WalkerStreet.info kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:62:plane-3] flip_done timed out Jun 16 10:14:30 rpi4a.WalkerStreet.info kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:153:plane-25] flip_done timed out Any ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1188940] New: bluetooth adapter fails to power on
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188940 Bug ID: 1188940 Summary: bluetooth adapter fails to power on 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hramrach@naga:~> bluetoothctl Agent registered [CHG] Controller 00:E0:3C:87:B8:03 Pairable: yes [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1188889] New: crash is failing with 5.13 kernels
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188889 Bug ID: 1188889 Summary: crash is failing with 5.13 kernels 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: hare(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to run crash on a 5.13 or later kernel dump I get the error message: crash: invalid structure member offset: task_struct_state FILE: task.c LINE: 5916 FUNCTION: task_state() [/usr/bin/crash] error trace: 559027f7b785 => 559027f7b54d => 559027fffe94 => 559027fffe0d This has been fixed by upstream commit d6b4f36d6b22b70fb14e692f36d20910ef5563c1. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1184718] New: systemtap simple helloworld script execution fails in Tumbleweed
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1184718 Bug ID: 1184718 Summary: systemtap simple helloworld script execution fails in Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vasilios.anastasiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848350 --> https://bugzilla.suse.com/attachment.cgi?id=848350&action=edit Related errors Unable to run a simple systemtap helloworld.stp example script (provided with systemtap-docs) in Tumbleweed. It works fine in SLE versions 12sp2-15sp3. Steps to reproduce: - Install systemtap, systemtap-docs, kernel-default-devel - Run: stap /usr/share/doc/packages/systemtap/examples/general/helloworld.stp See attached file for errors. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs August 2021