February 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1187701] New: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187701 Bug ID: 1187701 Summary: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: matt(a)traverse.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 850544 --> http://bugzilla.opensuse.org/attachment.cgi?id=850544&action=edit Failed boot on kernel 5.3.18-59.5-default Hello, After Leap 15.3 appliance images were updated recently, I have found the newer versions no longer boot on Ten64. Working image build: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.94.raw.xz / kernel 5.3.18-57-default Not working: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.106.raw.xz / kernel 5.3.18-59.5-default If I upgrade the kernel inside Build9.94 with 'zypper up', the same issue occurs. If I then choose the previous snapshot from GRUB the system can once again be booted with 5.3.18-57. Boot fails due to this, during initramfs/dracut: [ 6.227357] Internal error: synchronous external abort: 96000210 [#1] SMP [ 6.232443] mmc0: SDHCI controller on 2140000.esdhc [2140000.esdhc] using ADMA 64-bit [ 6.234152] Modules linked in: nvme nvme_core dwc3 sdhci_of_esdhc(+) sdhci_pltfm sdhci t10_pi mmc_core ulpi udc_core rtc_fsl_ftm_alarm i2c_imx gpio_keys sg scsi_mod [ 6.256675] Supported: Yes [ 6.259380] CPU: 6 PID: 7 Comm: kworker/u16:0 Not tainted 5.3.18-59.5-default #1 SLE15-SP3 [ 6.267643] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-gb47b96d4 06/25/2021 [ 6.275581] Workqueue: nvme-reset-wq nvme_reset_work [nvme] [ 6.275587] pstate: a0000005 (NzCv daif -PAN -UAO) [ 6.275594] pc : nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275600] lr : nvme_reset_work+0x164/0x12f8 [nvme] [ OK 6.275601] sp : ffff8000100a3c80 m] Reached targe[ 6.275603] x29: ffff8000100a3c80 x28: ffff0732958af0c0 t Basic[ 6.275606] x27: ffff0732958af0c0 x26: ffff0732954412c0 System. [ 6.275609] x25: ffff073295441300 x24: ffff073295441710 [ 6.275611] x23: ffff0732958af000 x22: ffff073295441000 [ 6.275614] x21: ffffb9bd5bd89000 x20: ffff073295440f10 [ 6.275617] x19: ffff073295441000 x18: ffffffffffffffff [ 6.275620] x17: 0000000000000000 x16: ffffb9bd5a7a35a0 [ 6.275622] x15: ffffb9bd5bd89908 x14: 0000000000000040 [ 6.275625] x13: 0000000000000228 x12: 0000000000000000 [ 6.275628] x11: 0000000000000000 x10: 0000000000001a50 [ 6.275630] x9 : ffff8000100a3d10 x8 : 000000000000007d [ 6.275633] x7 : 0000000000000006 x6 : 0000000000010000 [ 6.275635] x5 : 0000000000000000 x4 : 0000000000000000 [ 6.275638] x3 : 0000000080000000 x2 : 0000000000000000 [ 6.275641] x1 : ffffffffffffffff x0 : ffff8000105b201c [ 6.275644] Call trace: [ 6.275651] nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275659] process_one_work+0x200/0x458 [ 6.275662] worker_thread+0x144/0x4f0 [ 6.275666] kthread+0x130/0x138 [ 6.275670] ret_from_fork+0x10/0x18 [ 6.275675] Code: aa1c03e0 940005af f9414ac0 91007000 (b9400000) [ 6.275678] ---[ end trace c33296e2e9bf08c4 ]--- I have confirmed this issue with multiple Ten64 units and different SSD models, so it does not appear to be hardware related -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1195471] New: YaST software management crashes on startup
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195471 Bug ID: 1195471 Summary: YaST software management crashes on startup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: freddy(a)abrahamsson.xyz QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## System info Distro: OpenSUSE Tumbleweed Version: 20220201 System Ruby version:ruby 3.0.3p157 ## Description The software management module in YaST2 crashes during startup with the following message. > Internal error. Please report a bug report with logs. > Run save_y2logs to get complete logs. > > Caller: /usr/lib64/ruby/vendor_ruby/3.0.0/yast/yast.rb:186:in `import_pure' > > Details: undefined method `message' for nil:NilClass ## Steps to reproduce 1. Open YaST2 2. Click "Software management" ## Expected behaviour YaST2 module starting. ## Relevant logs The following log entry occurs in y2log. > 2022-02-03 02:48:55 <3> milou(21556) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):26 cannot require yast:cannot load such file -- solv > Did you mean? resolv at <internal:/usr/lib64/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require' > 2022-02-03 02:48:55 <3> milou(21556) [Ruby] yast/wfm.rb(handle_exception):272 Client /usr/share/YaST2/clients/sw_single.rb failed with 'undefined method `message' for nil:NilClass' (NoMethodError). > Backtrace: > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/yast.rb:186:in `import_pure' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/yast.rb:186:in `import' > /usr/share/YaST2/clients/sw_single.rb:517:in `StartSWSingle' > /usr/share/YaST2/clients/sw_single.rb:80:in `main' > /usr/share/YaST2/clients/sw_single.rb:806:in `<top (required)>' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/wfm.rb:347:in `eval' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/wfm.rb:347:in `run_client' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/wfm.rb:207:in `call_builtin' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/wfm.rb:207:in `call_builtin_wrapper' > /usr/lib64/ruby/vendor_ruby/3.0.0/yast/wfm.rb:196:in `CallFunction' > /usr/lib/YaST2/bin/y2start:60:in `<main>' -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1051056] KDE splash screen and Desktop have wrong color for ppc64 (BE)
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1051056 https://bugzilla.suse.com/show_bug.cgi?id=1051056#c37 --- Comment #37 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: RAID5 https://openqa.opensuse.org/tests/2170970 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193989] 'nvme show-regs -H /dev/nvme0n1' hangs in openQA
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193989 https://bugzilla.suse.com/show_bug.cgi?id=1193989#c3 --- Comment #3 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: nvme https://openqa.opensuse.org/tests/2173419 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192829] mediacheck is not started on Rescue CD
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1192829 https://bugzilla.suse.com/show_bug.cgi?id=1192829#c5 --- Comment #5 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: mediacheck https://openqa.opensuse.org/tests/2167280 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192140] [Build 20211027] openQA test fails in cifs
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1192140 https://bugzilla.suse.com/show_bug.cgi?id=1192140#c19 --- Comment #19 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_filesystem https://openqa.opensuse.org/tests/2126618 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194068] New: DHCP: LDAP- Support not working
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194068 Bug ID: 1194068 Summary: DHCP: LDAP- Support 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: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: obel1x(a)web.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 389 dirsrv was set up new and empty as described in https://doc.opensuse.org/documentation/leap/security/single-html/book-secur… Instance is up and running. Configured yast2 "Ldap & Kerberos client" to connect. After that, opening DHCP- Server (having patterns-server-dhcp_dns_server installed) and selecting to "Use LDAP" hangs yast completely unresponsive, task needs to be killed by "kill -9". Error in y2log: 2021-12-22 17:28:28 <1> obel1x(32695) [Pkg] Package.cc(IsAvailable):554 Tag yast2-ldap-server is not available to install 2021-12-22 17:28:28 <3> obel1x(32695) [Perl] modules/LdapServerAccess.pm(LdapServerAccess::InstallLdapServer):60 Package yast2-ldap-server is not available 2021-12-22 17:28:28 <3> obel1x(32695) [Perl] modules/LdapServerAccess.pm(LdapServerAccess::AddLdapSchemas):88 Cannot install yast2-ldap-server, not checking LDAP schemas 2021-12-22 17:28:34 <1> obel1x(32695) [Perl] modules/DhcpServer.pm(DhcpServer::LdapPrepareToWrite):2676 No DHCP configuration defaults found in LDAP, creating it 2021-12-22 17:28:34 <1> obel1x(32695) [Perl] modules/DhcpServer.pm(DhcpServer::LdapPrepareToWrite):2685 Adding DHCP configuration defaults: cn=defaultDHCP,ou=ldapconfig,dc=obel1x,dc=de 2021-12-22 17:28:34 <3> obel1x(32695) [agent-ldap] LdapAgent.cc(debug_exception):505 ldap error while adding cn=defaultDHCP,ou=ldapconfig,dc=obel1x,dc=de (65): Object class violation 2021-12-22 17:28:34 <3> obel1x(32695) [agent-ldap] LdapAgent.cc(debug_exception):507 additional info: unknown object class "suseDhcpConfiguration" 2021-12-22 17:28:34 <3> obel1x(32695) [Ruby] yast/yast.rb(call_yast_function):204 Error occurred while creating cn=defaultDHCP,ou=ldapconfig,dc=obel1x,dc=de. 2021-12-22 17:28:36 <3> obel1x(32695) [Perl] modules/DhcpServer.pm(DhcpServer::LdapPrepareToWrite):2694 Error descr: $VAR1 = { 'code' => 65, 'tls_error' => 0, 'msg' => 'Object class violation', 'server_msg' => 'unknown object class "suseDhcpConfiguration" ' }; 2021-12-22 17:28:36 <3> obel1x(32695) [agent-ldap] LdapAgent.cc(debug_exception):505 ldap error while adding cn=config1,cn=obel1x,ou=DHCP,dc=obel1x,dc=de (20): Type or value exists 2021-12-22 17:28:36 <3> obel1x(32695) [agent-ldap] LdapAgent.cc(debug_exception):505 ldap error while adding cn=192.168.178.0,cn=config1,cn=obel1x,ou=DHCP,dc=obel1x,dc=de (32): No such object In https://doc.opensuse.org/documentation/leap/security/single-html/book-secur… there is a migration- step mentioned when changing from openldap to 389, but in a fresh 389 there seems to be no such scheme as suseDhcpConfiguration. I would like to fix it myself, but i need input: 1. how should the attributes and shemes look like (please provide ldifs) 2. should they be made part of 389 dirsrv OR part of yast2-dhcp-server setup? 3. where to find the source for either one to make a pull request regards, daniel -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1195295] New: [Build 20220127] tensorflow fails to build
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195295 Bug ID: 1195295 Summary: [Build 20220127] tensorflow fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2163772/modules/tvm/ steps/3 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_ai_ml@64bit fails in [tvm](https://openqa.opensuse.org/tests/2163772/modules/tvm/steps/3) ## Test suite description Test AI/ML software ## Reproducible Fails since (at least) Build [20220127](https://openqa.opensuse.org/tests/2163259) ## Expected result Last good: [20220126](https://openqa.opensuse.org/tests/2161774) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1185893] opensuse-welcome: typo in German translation "siech"
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185893 http://bugzilla.opensuse.org/show_bug.cgi?id=1185893#c11 --- Comment #11 from Jan Pape�� <honyczek(a)centrum.cz> --- *** Bug 1179540 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179540] New: opensuse-welcome localization is not updated
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179540 Bug ID: 1179540 Summary: opensuse-welcome localization is not updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: honyczek(a)centrum.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are some translation updates on l10n.opensuse.org for package opensuse-welcome, but version in Tumbleweed is not updated. E.g. there are some updates for Czech translation including typo fixes, but Tumbleweed version of opensuse-welcome has same state of translation as openSUSE Leap 15.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 1