November 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1176033] touchpad don't work on Lenovo IdeaPad 3 (LNV81WE00)
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1176033 https://bugzilla.suse.com/show_bug.cgi?id=1176033#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Hrm. If you pass both i8042.nopnp=1 and pci=nocrs, does it work reliably? If it works, could you give the hwinfo and the dmesg output from the working state? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178401] New: errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default"
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178401 Bug ID: 1178401 Summary: errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-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: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation Originally reported in https://github.com/openSUSE/open-build-service/issues/10341#issue-728442525 the OBS build logs are full of errors and warnings which the OBS maintainers designated as issues coming from kernel and/or coming from initrd, e.g.: ``` [ 22s] Booting from ROM..c[?7l[2J[ 2.619073] dracut-pre-udev[229]: modprobe: FATAL: Module kqemu not found in directory /lib/modules/5.8.15-1-default [ 22s] [ 2.632643] dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default [ 22s] [ 2.636965] dracut-pre-udev[232]: modprobe: FATAL: Module ext3 not found in directory /lib/modules/5.8.15-1-default [ 23s] [ 3.394114] dracut-pre-udev[245]: modprobe: FATAL: Module nf_conntrack_ipv6 not found in directory /lib/modules/5.8.15-1-default [ 23s] [ 3.492219] dracut-pre-udev[256]: modprobe: FATAL: Module ibmvscsi not found in directory /lib/modules/5.8.15-1-default [ 23s] [ 3.525927] dracut-pre-udev[259]: modprobe: FATAL: Module ibmveth not found in directory /lib/modules/5.8.15-1-default … [ 30s] /sbin/unix2_chkpwd: setting to root:shadow 4755 (wrong owner/group root:root) [ 30s] /sbin/unix_chkpwd: setting to root:shadow 4755 (wrong owner/group root:root) [ 30s] /usr/bin/mount: setting to root:root 4755 (wrong permissions 0755) [ 30s] /usr/bin/su: setting to root:root 4755 (wrong permissions 0755) [ 30s] /usr/bin/umount: setting to root:root 4755 (wrong permissions 0755) … [ 34s] /usr/bin/mount: setting to root:root 4755 (wrong permissions 0755) [ 34s] /usr/bin/umount: setting to root:root 4755 (wrong permissions 0755) [ 34s] /usr/bin/wall: setting to root:tty 2755 (wrong permissions 0755) [ 34s] /usr/bin/write: setting to root:tty 2755 (wrong permissions 0755) [ 34s] /usr/bin/su: setting to root:root 4755 (wrong permissions 0755) [ 34s] grep: /etc/default/su: No such file or directory … [ 34s] /usr/bin/udevadm: error while loading shared libraries: libsystemd-shared-246.so: cannot open shared object file: No such file or directory … [ 34s] /var/tmp/rpm-tmp.FNx2gQ: line 19: pam-config: command not found … [ 34s] /usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping … [ 34s] chown: cannot access '/home/dockremap/.config': No such file or directory … [ 53s] RTNETLINK answers: File exists [ 53s] RTNETLINK answers: File exists ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/cu… shows the same ## Expected result Only errors in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1178299] torbrowser-laucher fails update
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178299 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178389] Package Management - Use of versions tab with retracted packages not particularly intuitive.
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178389 https://bugzilla.suse.com/show_bug.cgi?id=1178389#c9 --- Comment #9 from Stefan Hundhammer <shundhammer(a)suse.com> --- For sure this behaviour is surprising, I'll grant you that. Normally, selecting a version in the "Versions" tab does two things: It selects the version AND it changes the package status to "update" (which translates to "remove the previously installed version, but keep the package's configuration files, and install that newly selected version"). In the case of retracted packages, however, the "best" version (the best non-retracted version) is preselected by libzypp; technically, it means the "candidate" is set to that version, meaning that if any version of that package is installed or updated, it's that candidate version that you'll get. And here is the catch: The Qt package selector does not automatically also mark the package for update - for the reasons described above. So the usual automatic doing the two things simultaneously is not triggered; you have to tell the Qt package selector to initiate the update if that's what you want. I can understand that this might be surprising here; it works differently than normally. But this is a very exceptional case. Of course, we had warned the inventors of that entire "retracted" concept that it would lead to confusion and problems as soon as it would hit the users, but we were overruled. We tried a best effort approach to minimize the impact on users, but some fallout remains, as you realized. We also don't want to completely overengineer this with fancy workflows and additional confirmation dialogs; the expectation was that this would hopefully never be necessary to be used. Of course, this was an entirely wrong premise: As soon as a new feature is there, for sure somebody will jump at it. For the live of me I cannot imagine how a Java timezone database can possibly be harmful enough to warrant misusing this doomsday feature for it, as happened in this case. :-(( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176285] netconfig: /usr/lib/chrony/helper now in libexec
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1176285 https://bugzilla.suse.com/show_bug.cgi?id=1176285#c7 --- Comment #7 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3129-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1159566,1173391,1176285,1176325 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): sysconfig-0.85.6-3.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173422] systemd can't be rebuild with current linux-glibc-devel
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1173422 https://bugzilla.suse.com/show_bug.cgi?id=1173422#c16 --- Comment #16 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3138-1: An update that has 7 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1104902,1154935,1165502,1167471,1173422,1176513,1176800 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): systemd-234-24.61.1 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): systemd-234-24.61.1 SUSE Linux Enterprise Installer 15-SP1 (src): systemd-234-24.61.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165502] systemd warnings: Failed to create session: Start job for unit user-0.slice failed with 'canceled'
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1165502 https://bugzilla.suse.com/show_bug.cgi?id=1165502#c50 --- Comment #50 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3138-1: An update that has 7 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1104902,1154935,1165502,1167471,1173422,1176513,1176800 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): systemd-234-24.61.1 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): systemd-234-24.61.1 SUSE Linux Enterprise Installer 15-SP1 (src): systemd-234-24.61.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176244] Recent upgrade broke bcache support - dracut does not use /usr/libexec/dracut/modules.d
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1176244 https://bugzilla.suse.com/show_bug.cgi?id=1176244#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3137-1: An update that has two recommended fixes and contains one feature can now be installed. Category: recommended (moderate) Bug References: 1174075,1176244 CVE References: JIRA References: SLE-9807 Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): bcache-tools-1.1-3.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174075] Changing %{_libexecdir} breaks some packages which are misusing the macro
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1174075 https://bugzilla.suse.com/show_bug.cgi?id=1174075#c47 --- Comment #47 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3137-1: An update that has two recommended fixes and contains one feature can now be installed. Category: recommended (moderate) Bug References: 1174075,1176244 CVE References: JIRA References: SLE-9807 Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): bcache-tools-1.1-3.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156497] [Build 20191111] openQA test fails in tumbleweed (soft lockup in handle_external_interrupt_irqoff)
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1156497 https://bugzilla.suse.com/show_bug.cgi?id=1156497#c23 --- Comment #23 from Dan Čermák <dcermak(a)suse.com> --- (In reply to Oliver Kurz from comment #22) > Interesting. Could you share a little bit more details where the changes > have been applied? The changes were applied here: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10805 This just changes the amount of RAM and CPU cores available to the vagrant boxes in the SUT. > > > So my guess is that probably the openQA worker VM has maybe less cores > > hm, do you mean the qemu VM that is started as the SUT? yes > > In the latest test run of the initially mentioned test scenario in the > autoinst-log.txt file one can find the qemu command line: > > ``` > > /usr/bin/qemu-system-x86_64 -only-migratable -chardev > ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 > -soundhw hda -global isa-fdc.driveA= -m 1536 -cpu host -netdev > user,id=qanet0 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -boot > order=c -device usb-ehci -device usb-tablet -smp 1 -enable-kvm … > ``` > > see the parameters "-m 1536" meaning 1.5GB of RAM and "-smp 1" meaning a > single CPU core. Both parameters can be configured with test parameters, > e.g. `QEMURAM=2048` and `QEMUCPUS=2`, see > https://github.com/os-autoinst/os-autoinst/blob/master/doc/backend_vars. > asciidoc for details So it is as I guessed: if you launch the box with more cores and more RAM than the SUT has, then the CPU locks up when kvm is nested inside kvm. If I'd guess further, then it would be something along the lines of the CPU scheduler not really being build for the situation that the inner KVM VM has more cores than the outer one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0