August 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1157035] New: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush
by bugzilla_noreply＠novell.com 03 May '22

03 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1157035 Bug ID: 1157035 Summary: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 824366 --> http://bugzilla.suse.com/attachment.cgi?id=824366&action=edit tw.txt A fresh TW 20191112 shows the attached backtrace in dom0 after initial boot. Only the Xenstore domU is running. [ 61.673738] WARNING: CPU: 2 PID: 1416 at arch/x86/xen/multicalls.c:102 xen_mc_flush+0x1d0/0x200 [ 61.680650] CPU: 2 PID: 1416 Comm: (agetty) Not tainted 5.3.9-1-default #1 openSUSE Tumbleweed (unreleased) [ 61.685777] Hardware name: HP ProLiant SL160z G6 /ProLiant SL160z G6 , BIOS O33 07/28/2009 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1159958] New: All YaST icons lost
by bugzilla_noreply＠novell.com 29 Apr '22

29 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1159958 Bug ID: 1159958 Summary: All YaST icons lost Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 826804 --> http://bugzilla.opensuse.org/attachment.cgi?id=826804&action=edit screenshot Did a zypper dup from openSUSE-Leap-15.1-ARM-LXQT-raspberrypi3.aarch64-2019.05.17-Snapshot1.62.raw.xz to Leap 15.2 That worked nice so far, but there seems to be a problem with YaST: all icons lost, see picture. Inside the YST application there are no icons either -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1175038] New: Reinstalling bcm20702a1-firmware-1201650-5.1.noarch seems to remove the *.hcd files
by bugzilla_noreply＠suse.com 25 Apr '22

25 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175038 Bug ID: 1175038 Summary: Reinstalling bcm20702a1-firmware-1201650-5.1.noarch seems to remove the *.hcd files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: nick.chorley(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From dmesg, I found that the firmware for my device couldn't be found and was lead to believe it was provided by the package above. My system already had it installed, but the files were not present in /lib/firmware/brcm. I don't know how my system got into this state and figuring that the installation went wrong somehow, I decided to try and reinstall with # zypper in -f bcm20702a1-firmware-1201650-5.1.noarch This looked like it was successful, the output ending with Converting BCM_DriverOnly/64/BCM20702A1_001.002.014.1443.1467.hex to BCM20702A1-0b05-17cb.hcd Converting BCM_DriverOnly/64/BCM20702A1_001.002.014.1443.1469.hex to BCM20702A1-0b05-17cf.hcd Converting BCM_DriverOnly/64/BCM20702A1_001.002.014.1483.1647.hex to BCM20702A1-05ac-21e1.hcd Converting BCM_DriverOnly/64/BCM20702A1_001.002.014.1483.1669.hex to BCM20702A1-0a5c-21e6.hcd Converting BCM_DriverOnly/64/BCM20702A1_001.002.014.1443.1467.hex to BCM20702A1-050d-065a.hcd but after completion, the firmware files were still not present in /lib/firmware/brcm. Over on the openSUSE forums, someone told me that the installation script unconditionally removes the files in its post-uninstall step and that that is always run on update (see the thread here: https://forums.opensuse.org/showthread.php/542851-Problem-reinstalling-bcm2…) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1173050] New: Get rid of system config files in /etc : xfs
by bugzilla_noreply＠suse.com 25 Apr '22

25 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1173050 Bug ID: 1173050 Summary: Get rid of system config files in /etc : xfs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- # rpm -qpl xfs-1.2.0-45.7.x86_64.rpm |grep etc /etc/X11/fs /etc/X11/fs/config -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1116053] New: Please convert SysV init scripts by xfs into native systemd services
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1116053 Bug ID: 1116053 Summary: Please convert SysV init scripts by xfs into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1135733] New: vorta package should be updated
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1135733 Bug ID: 1135733 Summary: vorta package should be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sekhemty(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "vorta" package should be updated https://build.opensuse.org/package/show/openSUSE%3AFactory/vorta currently the repo has version 0.6.10, while upstream has v0.6.20, which includes several fixes and performance improvements -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1165052] New: [Upstream] Fish shell: Builtin test command aborts on NaN
by bugzilla_noreply＠novell.com 20 Apr '22

20 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1165052 Bug ID: 1165052 Summary: [Upstream] Fish shell: Builtin test command aborts on NaN Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: andreas_nordal_4(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a notice about an upstream bug in fish that makes it easy to crash one's shell session. For example: test NaN -ge 0 I noticed this in fish 3.0.2-2.4 (latest in Tumbleweed). A fix was made upstream, and is awaiting backport. Upstream issue: https://github.com/fish-shell/fish-shell/issues/6655 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1081947] New: PAM module pam_keyinit is still not included in the PAM stack
by bugzilla_noreply＠novell.com 20 Apr '22

20 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1081947 Bug ID: 1081947 Summary: PAM module pam_keyinit is still not included in the PAM stack 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bug #1045886 revealed the lack of the integration of the PAM module "pam_keyinit". The pam_keyinit PAM module ensures that the invoking process has a session keyring other than the user default session keyring. The created session keyring will be linked to the user keyring. Even if it currently works without the integration of "pam_keyinit", in this case the user session keyring is used as fallback, it's strongly recommended to use a session-keyring instead especially for root user, see man user-session-keyring(7). That would also has the benefit to re-enable the keyring support in systemd where each system service gets its own session keyring automatically not linked with the user-keyring (the root one). pam-config gained support for the configuration of pam_keyinit recently [1] but it's still not used and therefore pam_keyinit is still not integrated in the PAM stack. [1] https://build.opensuse.org/request/show/565816 -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 1128846] New: chrony-dnssrv@.service has wrong path to helper script
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1128846 Bug ID: 1128846 Summary: chrony-dnssrv@.service has wrong path to helper script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190307" # grep helper /usr/lib/systemd/system/chrony-dnssrv@.service ExecStart=/usr/share/chrony-helper update-dnssrv-servers %I ^^^^^^^^^^^^^^^^^^^^^^^^ rpm -ql chrony | grep helper /usr/lib/chrony/helper ^^^^^^^^^^^^^^^^^^^^^^ Please correct the path in ExecStart to point correctly to the helper script. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1146932] New: lvm cachepool on system lv causes system to be unbootable
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1146932 Bug ID: 1146932 Summary: lvm cachepool on system lv causes system to be unbootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: william.brown(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If a suse leap 15.1 machine is configured post-install to have a lvm cache pool device on the system lv, grub2 fails to boot with "Error invalid segment". IE the lvs are: # lvs home system rwi-aor--- 104.00g 100.00 root system rwi-aor--- 80.00g 100.00 swap system rwi-aor--- 8.00g 100.00 cache system rwi-aor--- .... -- You are receiving this mail because: You are on the CC list for the bug.

2 7