February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206745] New: Unnecessary log entries for rtkit
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206745 Bug ID: 1206745 Summary: Unnecessary log entries for rtkit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jimoe(a)sma-inc.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed 20221222 The system log has many entries (generally tens per day, grouped in bunches of 5 - 30) like this: 2022-12-29T06:30:59-0700 sma-station14l rtkit-daemon[7852]: Supervising 0 threads of 0 processes of 0 users. Is this really necessary? It is merely saying it has nothing to do. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1047218] New: trackerbug: packages do not build reproducibly from including build time
by bugzilla_noreply＠novell.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1047218 Bug ID: 1047218 Summary: trackerbug: packages do not build reproducibly from including build time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: SUSE Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://reproducible-builds.org/specs/source-date-epoch/ When packages include the current time of build it results in binaries that differ on every build and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 30

[Bug 1207730] New: vncserver requires dbus-1-x11
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207730 Bug ID: 1207730 Summary: vncserver requires dbus-1-x11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: christian.smietana(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- VNC connection using the vncserver script included in xorg-x11-Xvnc works only when dbus-1-x11 is installed. Otherwise the vnc client shows only a black screen. Steps to reproduce: 1. Make a minimal installation of OpenSUSE. In the installer, select the following components: patterns: only "X Window system" additional packages: xorg-x11-essentials, xorg-x11-Xvnc, icewm recommended packages: off Make sure that dbus-1-x11 isn't installed. 2. Start the system, open xterm, run "vncserver". Try to connect via VNC client. -> connection is possible, but only a black screen shows up. 3. Stop vncserver (run "vncserver -kill :1"). Install "dbus-1-x11". 4. Start vncserver, connect again via VNC client: -> works -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1131931] New: OCFS2: Defragmentation error: No space left on device
by bugzilla_noreply＠novell.com 07 Apr '23

07 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1131931 Bug ID: 1131931 Summary: OCFS2: Defragmentation error: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: weikai.wang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 802412 --> http://bugzilla.suse.com/attachment.cgi?id=802412&action=edit this script is used to generate disk framentation when I used the defragfs.ocfs2 to clean up disk fragmentation that generated by the attached shell script. you could execute the scrip by command "./defragfs_test.sh -d DEVICE -m MOUNT_POINT -n CLUSTER_NAME -s pcmk -o /tmp" You should use the device on your cluster replace DEVICE, use the same way replace MOUNT_POINT and CLUSTER_NAME. Then use the command defragfs.ocfs2 MOUNT_POINT. And if no accident, you will see some message like this: “ defragfs.ocfs2 1.8.5 [1/201]/mnt/ocfs2/tmp_file:Success [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd1" - No space left on device [2/201]/mnt/ocfs2/test_from_dd1:Failed [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd2" - No space left on device [3/201]/mnt/ocfs2/test_from_dd2:Failed [ERROR]Move extent failed:"/mnt/ocfs2/test_from_dd3" - No space left on device ” but if you execute defragfs.ocfs2 MOUNT_POINT again, the error message will not show again. and all the defragmentation will pass. please make sure your device's capacity is more tha 1G. Some times this error can make mount, unmount, and mkfs crushed. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1199184] New: switch Tumbleweed to a 4096bit RSA signing key
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1199184 Bug ID: 1199184 Summary: switch Tumbleweed to a 4096bit RSA signing key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dimstar(a)opensuse.org Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com Found By: --- Blocker: --- We currently still use a 2048 bit key for signing. It would be better to switch to a 4096 RSA key. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1182998] New: libcontainers-common seems to miss prerequires
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1182998 Bug ID: 1182998 Summary: libcontainers-common seems to miss prerequires Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are several errors during initial installation of libcontainers-common. As result, the configuration is broken and podman not correct working: # 2021-03-04 05:56:10 libcontainers-common-20210112-2.1.noarch.rpm installed ok # Additional rpm output: # /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found # /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found # 2021-03-04 05:56:10|install|libcontainers-common|20210112-2.1|noarch||openSUSE-MicroOS-20210302-0|867c95e8e8cd2e09046dc327b743e9134c6072146f59c6f3b357b0e92420b494| # 2021-03-04 05:56:10 openssh-8.4p1-4.1.x86_64.rpm installed ok # Additional rpm output: # find: '/etc/init.d/rc[35].d': No such file or directory # -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1200441] New: go1.19 release tracking
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1200441 Bug ID: 1200441 Summary: go1.19 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.19 (expected August 2022) is a major release of Go. Minor releases of go1.19.x will be provided through August 2023. This issue tracks go1.19.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1205667] New: VUL-0: CVE-2021-44758: heimdal -- security update
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205667 Bug ID: 1205667 Summary: VUL-0: CVE-2021-44758: heimdal -- security update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/348699/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- openSUSE:Backports and openSUSE:Factory only. CVE-2021-44758 Several vulnerabilities were discovered in Heimdal, an implementation of Kerberos 5 that aims to be compatible with MIT Kerberos. CVE-2021-3671 Joseph Sutton discovered that the Heimdal KDC does not validate that the server name in the TGS-REQ is present before dereferencing, which may result in denial of service. CVE-2021-44758 It was discovered that Heimdal is prone to a NULL dereference in acceptors where an initial SPNEGO token that has no acceptable mechanisms, which may result in denial of service for a server application that uses SPNEGO. CVE-2022-3437 Several buffer overflow flaws and non-constant time leaks were discovered when using 1DES, 3DES or RC4 (arcfour). CVE-2022-41916 An out-of-bounds memory access was discovered when Heimdal normalizes Unicode, which may result in denial of service. CVE-2022-42898 It was discovered that integer overflows in PAC parsing may result in denial of service for Heimdal KDCs or possibly Heimdal servers. CVE-2022-44640 It was discovered that the Heimdal's ASN.1 compiler generates code that allows specially crafted DER encodings to invoke an invalid free on the decoded structure upon decode error, which may result in remote code execution in the Heimdal KDC. For the stable distribution (bullseye), these problems have been fixed in version 7.7.0+dfsg-2+deb11u2. We recommend that you upgrade your heimdal packages. For the detailed security status of heimdal please refer to its security tracker page at: https://security-tracker.debian.org/tracker/heimdal References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44758 https://security-tracker.debian.org/tracker/DSA-5287-1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996586 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1155207] New: systemctl command line completion is very slow
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1155207 Bug ID: 1155207 Summary: systemctl command line completion is very slow Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- systemctl command line completion is very slow Suppose I type: systemctl status smart[tab][tab] and I get nothing. One second, two seconds... so I insist and hit tab several times, and after several seconds I get (one line per second): Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart and then I can type "d" and enter. Why is it that slow? It is an M2 disk. ie, SSD technology. It responds instantly when completing a normal command: Isengard:~ # smart smart_agetty smartctl smartd Isengard:~ # smart And that system is not busy at all, load 0.20. I can replicate the issue on other machines, and has been so probably for a year or so. Google "systemctl completion slow" finds reports on other distributions and several media. <https://bugzilla.redhat.com/show_bug.cgi?id=1491668> <https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1471723> and: <https://github.com/systemd/systemd/issues/7185> -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1207419] New: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207419 Bug ID: 1207419 Summary: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: fvogt(a)suse.com Reporter: aherzig(a)suse.com QA Contact: jsrain(a)suse.com CC: vmoutoussamy(a)suse.com Found By: Development Blocker: --- The dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package, to be addressed. spec file requires wicked and needs adaptation to also work with networkmanager if it is installed (and not wicked), configurable or detected on run-time -- You are receiving this mail because: You are on the CC list for the bug.

1 7