November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204180] [15.4][autoyast][installation] test fails in installation for transactional server role with error msg "install(4119) [Ruby] modules/Kdump.rb(update_initrd_with):421 Error updating initrd"
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204180 https://bugzilla.suse.com/show_bug.cgi?id=1204180#c14 --- Comment #14 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Ignaz Forster from comment #13) > (In reply to Josef Reidinger from comment #12) > > 2. In previous ages for CAASP product we add that specific call that is > > called always for kdump, even when kdump is not enabled ( see comment#8 for > > code ). I am not sure if it is correct to call it always. > > I think this code is still needed for openSUSE MicroOS / SLE Micro / ALP, > otherwise kdump wouldn't be configured on first boot I guess? But question is if it is correct to call it even when kdump is disabled? So basically yast knows if kdump is configured and if so, then it ensures that kdump rpm package is installed. But we now call that call unconditionally, which is maybe wrong? > > > 3. I am not sure if `transactional-update kdump` handle disabled kdump. We > > need to have it when user configure kdump and then change mind. Is it > > correct to call also `transactional-update kdump` in that case? > > Yes, it checks whether the kdump.service is activated and only runs if that > is the case. However that check is performed in transactional-update itself, > not in /usr/sbin/tu-rebuild-kdump-initrd, the helper script which is called > from YaST directly during installation (where Package.IsTransactionalSystem > doesn't seem to be true from how I understand the code). yes, `IsTransactionalSystem` is true only when "/" is ro, but it is not case during installation, when it is open for modification. It is ro only on running system. To be honest I am not sure if `transactional-update kdump` will work in insts-sys where it runs in chroot and "/" is still rw. Well, I revisit code and recheck again logs from my reproduced attempt and 1. kdump is enabled by default on opensuse leap which quite surprise me 2. so I hoped that kdump inform that such packages I needed and looks like it is ignored by autoyast. So it is something to fix 3. if kdump is not configured then call to rebuild-kdump-initrd is skipped so it is no issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205157] nrpe: %pre needs usrmerge update
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205157 https://bugzilla.suse.com/show_bug.cgi?id=1205157#c1 --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- There is only one correct way: "getent services nrpe". This is the only command which returns an always correct value (at least if no error occours). All the assumptions about where the services are defined will never work if you don't honor the services configuration in /etc/nsswitch.conf. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205160] New: [Build 20221106] openQA test fails in sssd - slapd[29795]: lt_dlopenext failed: (back_hdb.la) file not found
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205160 Bug ID: 1205160 Summary: [Build 20221106] openQA test fails in sssd - slapd[29795]: lt_dlopenext failed: (back_hdb.la) file not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2858248/modules/sssd /steps/28 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: santiago.zarate(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-NET-arm-extra_tests_in_textmode@aarch32 fails in [sssd](https://openqa.opensuse.org/tests/2858248/modules/sssd/steps/28) When running the sssd testsuite, we get in the logs: > ###junit testsuite time="2022-11-07T07:07:29.712" text="Use SSSD with LDAP backend" > + mkdir -p /tmp/ldap-sssdtest > + cp ldap.crt /tmp/ldap-sssdtest.cacrt > + cp ldap.crt /tmp/ldap-sssdtest.crt > + cp ldap.key /tmp/ldap-sssdtest.key > + /usr/sbin/slapd -h ldap:/// -f slapd.conf > + test_abort 'Failed to prepare LDAP server' > + ../junit.sh error -T 'Failed to prepare LDAP server' And when looking at the journal: > Nov 07 07:07:29.750849 susetest slapd[29795]: @(#) $OpenLDAP: slapd 2.6.3 (Sep 26 2022 00:00:00) $ > openldap > Nov 07 07:07:29.760189 susetest slapd[29795]: lt_dlopenext failed: (back_hdb.la) file not found > Nov 07 07:07:29.760443 susetest slapd[29795]: slapd.conf: line 24: <moduleload> handler exited with 1! > Nov 07 07:07:29.760672 susetest slapd[29795]: DIGEST-MD5 common mech free > Nov 07 07:07:29.760873 susetest slapd[29795]: DIGEST-MD5 common mech free > Nov 07 07:07:29.761662 susetest slapd[29795]: slapd stopped. > Nov 07 07:07:29.761891 susetest slapd[29795]: connections_destroy: nothing to destroy. ## Test suite description Maintainer: QE Core Mainly console extratest. ## Reproducible Fails since (at least) Build [20220806](https://openqa.opensuse.org/tests/2503437) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=arm&distri=opensuse&f… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1205042] [TRACKERBUG] Set openssl 3.0.7 as the default openssl in TW
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205042 http://bugzilla.opensuse.org/show_bug.cgi?id=1205042#c11 --- Comment #11 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1205042) was mentioned in https://build.opensuse.org/request/show/1034366 Factory / python-M2Crypto -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185218] GCC 11: exiv2 build fails on i586
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1185218 https://bugzilla.suse.com/show_bug.cgi?id=1185218#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3889-1: An update that solves 15 vulnerabilities, contains one feature and has one errata is now available. Category: security (important) Bug References: 1068871,1142675,1142679,1185002,1185218,1185447,1185913,1186053,1186192,1188645,1188733,1189332,1189333,1189334,1189335,1189338 CVE References: CVE-2017-1000128,CVE-2019-13108,CVE-2019-13111,CVE-2020-19716,CVE-2021-29457,CVE-2021-29463,CVE-2021-29470,CVE-2021-29623,CVE-2021-31291,CVE-2021-32617,CVE-2021-34334,CVE-2021-37620,CVE-2021-37621,CVE-2021-37622,CVE-2021-37623 JIRA References: PED-1393 Sources used: openSUSE Leap 15.4 (src): exiv2-0.27.5-150400.15.4.1, exiv2-0_26-0.26-150400.9.16.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): exiv2-0.27.5-150400.15.4.1, exiv2-0_26-0.26-150400.9.16.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 1198274] New: zypper: cannot trust key
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198274 Bug ID: 1198274 Summary: zypper: cannot trust key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time a repository not signed with openSUSE key is updated zypper asks: Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): regardless of the answer it asks again next time the repository is updated. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1204157] Plank not working properly on Pantheon
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204157 https://bugzilla.suse.com/show_bug.cgi?id=1204157#c3 --- Comment #3 from Dude <le0nard(a)posteo.net> --- Seems to be fixed in 43.0-2 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020262). Is there any way to speed up the process of this version landing in TW? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198618] systemd-boot: openSUSE branding
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198618 https://bugzilla.suse.com/show_bug.cgi?id=1198618#c3 --- Comment #3 from Franck Bui <fbui(a)suse.com> --- (In reply to Ludwig Nussel from comment #1) > the subdirectory on the ESP is also "systemd", should be opensuse probably It should be possible with "--entry-token=" (available since v251). Actually I just did the test with v252 and couldn't find "systemd". By default $machine-id is created. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198618] systemd-boot: openSUSE branding
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198618 https://bugzilla.suse.com/show_bug.cgi?id=1198618#c2 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #2 from Franck Bui <fbui(a)suse.com> --- (In reply to Ludwig Nussel from comment #0) > systemd-boot calls itself "Linux Boot Manager". Maybe it should brand itself > according to /etc/os-release. Upstream issue: > https://github.com/systemd/systemd/issues/17044 This seems to have been addressed by the introduction of the new option "--efi-boot-option-description=", which should be available when v252 will be released (hopefully soon). Note that according to the man page, there is usually no need to change the description "Linux Boot Manager" though. Ludwig are you OK to close this report ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202850] New: Tearing and slow screen rendering after update
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202850 Bug ID: 1202850 Summary: Tearing and slow screen rendering after update 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: X.Org Assignee: gfx-bugs(a)suse.de Reporter: rgb.mldc(a)gmail.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Until a few days ago, the graphics were working without problems in my laptop (system info bellow). After the last update that changed (if I remember right) some mesa libraries, screen rendering started to go in "jumps" with a lot of tearing and rendering artifacts. 3D applications are now slow. For example, until last week supertuxkart worked without problems, but now it's impossible to use. Many desktop effects are not working anymore. For example, transparency when dragging windows is not working or even available on Plasma desktop effect settings, but expos�� effect, highlighting panels and blurring on log-out still work (a few checkboxes where neither checked nor unchecked, they showed three dots instead). Everything worked without problems before the update. System information: TUXEDO-Book-BC1507. Graphics (as reported by YaST2 hardware information): intel CoffeeLake-H GT2 (UHD Graphics 630). Copied from KInfoCenter: Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.18-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i5-8300H CPU @ 2.30GHz Memory: 15.4 GiB of RAM Graphics Processor: llvmpipe The puzzling bit is "llvmpipe". I cannot find anymore an option to set the graphic motor under Plasma's system settings �� Screen �� Compositor. Bellow the output of ~> sudo lspci -v -s 00:02.0 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device 8555 Flags: bus master, fast devsel, latency 0, IRQ 128 Memory at 8d000000 (64-bit, non-prefetchable) [size=16M] Memory at 90000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915 -- You are receiving this mail because: You are on the CC list for the bug.

1 21