openSUSE Bugs May 2022

bugs@lists.opensuse.org

2 participants
2447 discussions

[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 1195391] New: identify and declare bash dependencies explicitly
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1195391 Bug ID: 1195391 Summary: identify and declare bash dependencies explicitly 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a lot of fear that the openSUSE and SUSE distributions are, due to historic reason alone always assuming that /bin/sh is a symlink to bash, so that scripts executed with /bin/sh are actually only executable with bash. in order to explore that dependency, we need to figure out how many scripts actually use bash specifics when being invoked for /bin/sh and then fix these to declare the bash dependency if they have it. this bug is a tracker issue for fixes related to that. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1198669] New: Unable to fully read some files with ntfs3
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198669 Bug ID: 1198669 Summary: Unable to fully read some files with ntfs3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: linus.kardell(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm trying out the ntfs3 kernel driver on OpenSUSE Tumbleweed, but I'm unable to read some files. I also posted about this here: https://reddit.com/r/openSUSE/comments/u693vm/no_such_file_or_directory_whe… , and at https://bugzilla.kernel.org/show_bug.cgi?id=215864 The files that it happens to are a few GiB in size. It doesn't fail immediately, rather when I read it with dd status=progress the first time it reads a bit into the file (a few MiB or over a hundred MiB, depending on the files, but it seems to always be the same distance for the same file), and then throws "No such file or directory". On subsequent reads, it gets through the whole file. Only, it doesn't really, because the resulting content is wrong. It's the correct length, but past a certain point the it's all zeroes. So it never truly reads the whole file, but only sometimes throws an error (when it's not in disk cache?). The same file always comes out correct with ntfs-3g. Also, not sure if related, but after I've mounted and unmounted a few times with ntf3 and ntfs-3g, ntfs3 starts throwing errors saying: "mount: /windows/d: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error." and refuses to mount it unless I add -o ro. ntfs-3g still mounts it, and ntfs3 mounts it after rebooting. The filesystem has compression enabled, in case that matters (though the files should be incompressible, as they're gzipped). I tried running chkdsk from Windows, but that did not change anything. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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 1195445] New: apache2-mod_auth_kerb-5.4 broken after krb5 update
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195445 Bug ID: 1195445 Summary: apache2-mod_auth_kerb-5.4 broken after krb5 update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: opensuse(a)htl-steyr.ac.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Updating the system with zypper causes the package krb5 to be updated from krb5-1.16.3-3.24.1.x86_64 to krb5-1.19.2-150300.8.3.2.x86_64 apache now fails to start if module auth_kerb is active with: Cannot load /usr/lib64/apache2/mod_auth_kerb.so into server: /usr/lib64/apache2/mod_auth_kerb.so: undefined symbol: krb5_rc_dfl_init krb5_rc_dfl_init is not defined in /usr/lib64/libkrb5.so.3.3 after updating to krb5-1.19.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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

[Bug 1199970] New: reaim-io-disk ext4 regression in 5.18 in mballoc
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1199970 Bug ID: 1199970 Summary: reaim-io-disk ext4 regression in 5.18 in mballoc 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: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Marvin has bisected a small (5%) performance regression in ext4 due to commit 077d0c2c78df ("ext4: make mb_optimize_scan performance mount option work with extents"). The bisection result looks like: good-27b38686 bad-077d0c2c Hmean disk-1 537.83 529.10 Hmean disk-5 3433.28 3431.71 ... Hmean disk-25 16999.09 16290.18 * -3.67%* Hmean disk-29 19162.99 18385.46 * -4.73%* Hmean disk-33 21859.13 20793.95 * -4.54%* The regression was reported on laurel1. Likely the overhead of mballoc has somewhat increased due to rbtree searching of best group to use. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1199618] New: [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199618 Bug ID: 1199618 Summary: [Build 20220516] openQA test fails in fanotify16 (LTP) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2353240/modules/fano tify16/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD24G fails in [fanotify16](https://openqa.opensuse.org/tests/2353240/modules/fanotify16/st… Error log: fanotify.h:336: TBROK: fanotify_mark (3, FAN_MARK_ADD, ..., AT_FDCWD, ".") failed: EXDEV (18) Test process returned unkown none zero value (2). Test took approximately 0.581575272008195 seconds Some test output could not be parsed: 9 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20220302](https://openqa.opensuse.org/tests/2224057) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs May 2022