openSUSE Bugs September 2021

bugs@lists.opensuse.org

1 participants
3066 discussions

[Bug 1188949] New: The wired connection stops connecting the next day after installation
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

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 35

[Bug 1114673] New: New UI for firewalld: interface not assigned to the right zone when changed to public in first run
by bugzilla_noreply＠novell.com 05 Dec '22

05 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1114673 Bug ID: 1114673 Summary: New UI for firewalld: interface not assigned to the right zone when changed to public in first run Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Interface is not assigned to the right zone after following steps: - Open new UI for firewalld: yast2 firewall - Assign interface to different zone (for example public) - In Zones, set different zone (for example trusted) as default. - Accept - Check with firewall-cmd interface assignation: firewall-cmd --list-interfaces --zone=public | grep ens4 (is not there) but firewall-cmd --list-interfaces --zone=trusted | grep ens4 (it succeeds and it is pointing to the default zone not the one that was assigned) (same result also after trying a firewall-cmd --reload) Assignation works in general, but in this combination and just when the user enters first to this screen and set previous steps, does not work (perhaps some wrong initialization). Expected result: Point to the interface that is assigned in the UI (in the example, to public) -- You are receiving this mail because: You are on the CC list for the bug.

2 30

[Bug 1188115] New: Backintime: no snapshots possible anymore after (15.2->15.3) upgrade to 1.21
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188115 Bug ID: 1188115 Summary: Backintime: no snapshots possible anymore after (15.2->15.3) upgrade to 1.21 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michaelof(a)rocketmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Backintime seem to process taking a snapshot, but stops at final step(s). Starting situation: zypper dup Leap from 15.2 to 15.3. After reboot, performed a zypper ref && zypper up, all pkgs current now. Made an initial Clonezilla image, to be sure. Reproducible: Wanted to make a first backintime snapshot, does NOT work Error on command line is: INFO: Remove leftover 'new_snapshot' folder from last run QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' INFO: Call rsync to take the snapshot Traceback (most recent call last): File "/usr/share/backintime/common/backintime.py", line 1165, in <module> startApp() File "/usr/share/backintime/common/backintime.py", line 517, in startApp args.func(args) File "/usr/share/backintime/common/backintime.py", line 739, in backup ret = takeSnapshot(cfg, force) File "/usr/share/backintime/common/backintime.py", line 94, in takeSnapshot ret = snapshots.Snapshots(cfg).backup(force) File "/usr/share/backintime/common/snapshots.py", line 692, in backup ret_val, ret_error = self.takeSnapshot(sid, now, include_folders) File "/usr/share/backintime/common/snapshots.py", line 1036, in takeSnapshot proc.run() File "/usr/share/backintime/common/tools.py", line 1981, in run self.callback(line, self.user_data) File "/usr/share/backintime/common/snapshots.py", line 809, in rsyncCallback self.snapshotLog.append('[C] ' + line[12:], 2) File "/usr/share/backintime/common/snapshotlog.py", line 195, in append self.logFile.write(msg + '\n') File "/usr/share/backintime/common/tools.py", line 1513, in handler self.callback() File "/usr/share/backintime/common/snapshotlog.py", line 203, in flush self.logFile.flush() RuntimeError: reentrant call inside <_io.BufferedWriter name='/root/.local/share/backintime/takesnapshot_.log'> -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1024727] New: Cannot login to Bugzilla using Bugzilla "login" button
by bugzilla_noreply＠novell.com 04 Dec '22

04 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1024727 Bug ID: 1024727 Summary: Cannot login to Bugzilla using Bugzilla "login" button Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qantas94heavy(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 713674 --> http://bugzilla.opensuse.org/attachment.cgi?id=713674&action=edit Unprocessed PHP file I attempted to login to Bugzilla by clicking the "Login" button on the Bugzilla home page, which took me to the following URL: https://login.microfocus.com/nidp/idff/sso?id=132&sid=5&option=credential&s… Instead of receiving the page as usual, it appears to load some scripts from the following URL: https://www.suse.com/common/inc/include.php?file=headers/hdr_head.html The PHP file there appears to be unprocessed, which is most likely causing the issue here. I was only able to login by going through the openSUSE wiki then going back to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1190434] New: crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 03 Dec '22

03 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1190434 Bug ID: 1190434 Summary: crash is unable to find debuginfo of usrmerged kernel 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmair(a)suse.com, ptesarik(a)suse.com Found By: --- Blocker: --- With a usrmerged kernel, vmlinux(.xz) is in the modules directory for the kernel: /usr/lib/modules/5.14.1-1-default/vmlinux.xz This means the debug info ends up here: /usr/lib/debug/usr/lib/modules/5.14.1-1-default/vmlinux.debug Crash only looks at the old location though, and fails: please wait... (uncompressing /usr/lib/modules/5.14.1-1-default/vmlinux.xz) readmem: read_diskdump() NOTE: gnu_debuglink file: vmlinux.debug crc32: f73ed3b0 /usr/lib/modules/5.14.1-1-default//vmlinux.debug: not readable/found /usr/lib/modules/5.14.1-1-default//.debug/vmlinux.debug: not readable/found /usr/lib/debug/boot/vmlinux.debug: not readable/found crash: /var/tmp/vmlinux.xz_DZPxr5: no debugging data available crash: vmlinux.debug: debuginfo file not found crash: either install the appropriate kernel debuginfo package, or copy vmlinux.debug to this machine -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1183568] New: └─kmod-static-nodes.service @4.168s +10.122s makes init unduly long
by bugzilla_noreply＠suse.com 02 Dec '22

02 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183568 Bug ID: 1183568 Summary: ��kmod-static-nodes.service @4.168s +10.122s makes init unduly long Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Original summary: ��kmod-static-nodes.service @4.168s +10.122s makes init unduly long Same PC also has another 15.3 and TW and 15.2. TW takes under 4s to reach multi-user. 15.2 takes much less than the two 15.3s, but much more than TW, to same target. kmod-static-nodes seems the biggest delay in the 15.3s. Every installation except one 15.3 is on SATA SSD in UEFI. The odd one is on NVME except for /boot on SATA, and it has its own unshared ESP there. All are being booted from TW's custom.cfg. Following is from the 15.3 on SATA: # inxi -SMdy System: Host: asa88 Kernel: 5.3.18-51-default x86_64 bits: 64 Console: tty 3 Distro: openSUSE Leap 15.3 Beta Machine: Type: Desktop Mobo: ASUSTeK model: A88X-PRO v: Rev X.0x serial: 140323952800121 UEFI: American Megatrends v: 2603 date: 03/10/2016 Drives: Local Storage: total: 715.41 GiB used: 728.23 GiB (101.8%) ID-1: /dev/nvme0n1 vendor: TeamGroup model: TM8FP6256G size: 238.47 GiB ID-2: /dev/sda model: T-FORCE 512GB size: 476.94 GiB Message: No Optical or Floppy data was found. # systemd-analyze blame | head -n22 10.566s systemd-udev-trigger.service 10.385s systemd-modules-load.service 10.383s systemd-remount-fs.service 10.379s systemd-journald.service 10.190s dev-disk-by\x2dlabel-tvgp02swap.swap 10.161s modprobe(a)drm.service 10.144s dev-hugepages.mount 10.144s dev-mqueue.mount 10.143s sys-kernel-debug.mount 10.142s sys-kernel-tracing.mount 10.131s modprobe(a)fuse.service 10.125s modprobe(a)configfs.service 10.122s kmod-static-nodes.service 3.967s initrd-switch-root.service 2.183s systemd-random-seed.service 2.076s kbdsettings.service 1.699s wicked.service 1.188s dracut-initqueue.service 584ms systemd-logind.service 509ms systemd-udevd.service 301ms initrd-parse-etc.service 269ms user(a)0.service # systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. ��multi-user.target @16.889s ��sshd.service @16.827s +60ms ��network.target @16.826s ��wicked.service @15.124s +1.699s ��wickedd-nanny.service @15.059s +63ms ��wickedd.service @14.982s +75ms ��wickedd-auto4.service @14.853s +127ms ��dbus.service @14.791s ��basic.target @14.787s ��sockets.target @14.787s ��dbus.socket @14.786s ��sysinit.target @14.781s ��systemd-udevd.service @14.271s +509ms ��systemd-tmpfiles-setup-dev.service @14.225s +29ms ��kmod-static-nodes.service @3.821s +10.122s ��systemd-journald.socket ��system.slice ��-.slice -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[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 30 Nov '22

30 Nov '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 22

[Bug 1047225] New: LUKS password doesn't show up when booting with nomodeset
by bugzilla_noreply＠novell.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Bug ID: 1047225 Summary: LUKS password doesn't show up when booting with nomodeset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Install a TW system with the standard procedure for LVM+encrpption as suggested by installer on KVM. It works fine with the graphical LUKS password. But when you boot with nomodeset boot option, the boot process hangs without asking the LUKS password. This didn't happen on openSUSE Leap 42.2 / 42.3. And when I upgrade only plymouth packages on the Leap system, it starts showing the same problem. So, it's a regression in the recent plymouth package. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1190256] New: Keyboard not working on ASUS Zenbook 14 UM425UA
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 Bug ID: 1190256 Summary: Keyboard not working on ASUS Zenbook 14 UM425UA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mkrapp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new ASUS Zenbook 14 UM524UA. Unfortunately keyboard is not at all working in latest Tumbleweed with kernel 5.14.0-1-default. I: Bus=0018 Vendor=04f3 Product=3134 Version=0100 N: Name="ASUE140A:00 04F3:3134 Keyboard" P: Phys=i2c-ASUE140A:00 S: Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input8 U: Uniq= H: Handlers=sysrq kbd leds event5 B: PROP=0 B: EV=120013 B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe B: MSC=10 B: LED=1f It's recognized during boot: > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input3 > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input4 > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Keyboard as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input5 > Aug 31 20:00:01 localhost kernel: hid-generic 0018:04F3:3134.0001: input,hidraw0: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00 but not working at all. no events created when pressing/releasing keys. The touchpad works fine, albeit I didn't try to get the extra function working (numpad on touchpad) yet. I'll attach hwinfo and journal in a minute. Any idea how I can get the keyboard working? -- You are receiving this mail because: You are on the CC list for the bug.

1 60

[Bug 1142545] New: mod_auth_kerb segmentation fault when using basic authentication
by bugzilla_noreply＠novell.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1142545 Bug ID: 1142545 Summary: mod_auth_kerb segmentation fault when using basic authentication Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: nocera(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 811365 --> http://bugzilla.opensuse.org/attachment.cgi?id=811365&action=edit mod_auth_kerb.c patch A segmentation fault is triggered in function authenticate_user_krb5pwd() when credentials are supplied using basic authentication. A description of the bug and patch (attached to this report) is described at: https://sourceforge.net/p/modauthkerb/bugs/61/ Since mod_auth_kerb is not being actively developed, it would be convenient if the patch was applied through the openSUSE build. The source RPM already includes numerous patches to the mod_auth_kerb source. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs September 2021