December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D 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: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1193183] New: inkscape-1.1.1-lp153.87.2 is not working
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193183 Bug ID: 1193183 Summary: inkscape-1.1.1-lp153.87.2 is not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michael.kasimir(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- as reported in openSUSE support mailing list 28 Nov 2021 18:36 https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/… after upgrade from 15.2 to 15.3, the start of inkscape could not be launched. Package version: inkscape-1.1.1-lp153.87.2.x86_64.rpm Terminal .bash run shows the following error message: $ inkscape inkscape: error while loading shared libraries: libinkscape_base.so: cannot open shared object file: No such file or directory As message shows apparently it should have to do with libinkscape_base.so The issue has been verified on a new, updated Leap 15.3 system and inkscape installed via opi from graphics-repository https://download.opensuse.org/repositories/graphics/openSUSE_Leap_15.3/x86_… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 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 1192521] New: gawk unreliable to build
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192521 Bug ID: 1192521 Summary: gawk unreliable to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gawk seems to be quite unreliable to build and fails often (especially on i586 which we still need for the distro bootstrap for all the -32bit stuff, like wine and steam): 2021-10-08 20:09:15 gawk source change succeeded 2m 10s lamb16:7 2021-11-06 17:20:52 gawk source change failed 2m 5s cloud125:3 2021-11-06 23:21:42 gawk new build failed 2m 22s cloud108:2 2021-11-08 10:16:17 gawk new build failed 2m 13s cloud122:3 2021-11-08 11:39:00 gawk new build succeeded 2m 9s lamb72:4 2021-11-08 16:31:33 gawk new build failed 2m 17s cloud130:2 So it became especially bad after the last source change, i.e. the update ti 5.1.1 (sr#928731) The failure happens in the test suite: [ 125s] ============== _iolint ============= [ 125s] --- iolint.ok 2021-05-25 03:27:24.000000000 +0000 [ 125s] +++ _iolint 2021-11-08 16:31:24.843121266 +0000 [ 125s] @@ -25,9 +25,5 @@ [ 125s] 0 [ 125s] gawk: iolint.awk:60: warning: `echo hello' used for input pipe and output pipe [ 125s] hello [ 125s] -0 [ 125s] -0 [ 125s] -gawk: iolint.awk:68: warning: `cksum' used for output file and output pipe [ 125s] -3015617425 6 [ 125s] -0 [ 125s] -0 [ 125s] +gawk: iolint.awk:60: fatal: print to "echo hello" failed: Broken pipe [ 125s] +EXIT CODE: 2 [ 125s] ============== _sigpipe1 ============= [ 125s] --- sigpipe1.ok 2019-08-28 18:43:58.000000000 +0000 [ 125s] +++ _sigpipe1 2021-11-08 16:31:21.007121476 +0000 [ 125s] @@ -1,3 +1,4 @@ [ 125s] system [ 125s] pipe to command [ 125s] -pipe from command [ 125s] +gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe [ 125s] +EXIT CODE: 2 [ 125s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/gawk-5.1.1/test' [ 125s] make[2]: *** [Makefile:2087: check] Error 1 [ 125s] make[1]: *** [Makefile:757: check-recursive] Error 1 [ 125s] make: *** [Makefile:1056: check] Error 2 [ 125s] error: Bad exit status from /var/tmp/rpm-tmp.ELjTon (%check) [ 125s] -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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 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

[Bug 1191514] New: [busybox-static] Warewulf3 requires additional commands
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1191514 Bug ID: 1191514 Summary: [busybox-static] Warewulf3 requires additional commands Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ihno(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kukuk(a)suse.com Found By: Development Blocker: --- Warewulf is a popular HPC deployment tool to set up compute nodes in a cluster. It creates its own initfs using busybox (static). To operate correctly, it requires at least: 1. cttyhack - to get a console for debugging purposes 2. switch_root - to switch to the main system 3. reboot - to smoothly reboot from the debugging console. Command 1. was removed with the commit: | Wed Jul 22 09:24:42 UTC 2020 - Thorsten Kukuk <kukuk(a)suse.com> [...] | - Disable cttyhack, we don't provide the calling tools [...] This is not true, we do have a tool that's calling it. Command 2. was removed with: | Fri Mar 13 20:04:25 UTC 2020 - Thorsten Kukuk <kukuk(a)suse.com> [...] | - Merge config of default, -container and -static to be able to | drop -container variant with no reason given. Command 3. has never been enabled - as far as I can tell. If there are strong objections to (re)adding these commands, I'm fine with creating another (static) flavor of busybox - just for warewulf. -- You are receiving this mail because: You are on the CC list for the bug.

1 7