February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208682] New: journalctl: option "--list-boots" does not honor --output options
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208682 Bug ID: 1208682 Summary: journalctl: option "--list-boots" does not honor --output options 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: Other Assignee: screening-team-bugs(a)suse.de Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- According to the manual page of journalctl(1), it should accept the "--output" options (e.g. "short-unix", or "json") as defined in the manual. However, it seems that with the "--list-boots" the "--output=<whatever>" is ignored. Example: # journalctl --output=short-unix --list-boots -3 bfdc1672ba224e4a84aa4655ed90ec0a Thu 2023-02-23 02:11:17 CET��Fri 2023-02-24 06:13:16 CET -2 26ef56c47e734985b3805a8af7f394c3 Fri 2023-02-24 06:20:50 CET��Sat 2023-02-25 08:29:24 CET -1 6132b2a1bc4c4ac1b0bc0c4afc9bda5a Sat 2023-02-25 08:30:17 CET��Sat 2023-02-25 14:50:14 CET 0 666e5a91b4274dac87640d1199dac62c Sat 2023-02-25 14:50:37 CET��Sun 2023-02-26 11:01:50 CET # journalctl --output=json --list-boots -3 bfdc1672ba224e4a84aa4655ed90ec0a Thu 2023-02-23 02:11:17 CET��Fri 2023-02-24 06:13:16 CET -2 26ef56c47e734985b3805a8af7f394c3 Fri 2023-02-24 06:20:50 CET��Sat 2023-02-25 08:29:24 CET -1 6132b2a1bc4c4ac1b0bc0c4afc9bda5a Sat 2023-02-25 08:30:17 CET��Sat 2023-02-25 14:50:14 CET 0 666e5a91b4274dac87640d1199dac62c Sat 2023-02-25 14:50:37 CET��Sun 2023-02-26 11:02:02 CET For scripting it would be valuable to have the output formatted as described in the manual page. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1199383] New: [Tumbleweed][lftp][Build_20220423] Connetion via lftp failed due with self signed certificate
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1199383 Bug ID: 1199383 Summary: [Tumbleweed][lftp][Build_20220423] Connetion via lftp failed due with self signed certificate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: weixuan.hao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Summary This test is to test lftp with ssl enabled ## Observation After setting up vsftpd server and lftp, using lftp to login to ftp server and try to download/upload files, connection will fail with self signed certificate ## Environment # uname -m x86_64 # cat /etc/*release NAME="openSUSE Tumbleweed" # VERSION="20220423" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20220423" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20220423" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ## Reproducible Follow steps from https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769978 to set up vsftpd server and https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769945 for lftp testing ## Error # lftp -d -u ftpuser -e 'set ftp:ssl-force true' localhost Password: ---- Resolving host address... ---- 2 addresses found: ::1, 127.0.0.1 lftp ftpuser@localhost:~> ls ---- Connecting to localhost (::1) port 21 **** Socket error (Connection refused) - reconnecting ---- Closing control socket ---- Connecting to localhost (127.0.0.1) port 21 <--- 220 Welcome to SUSE FTP service. ---> FEAT <--- 211-Features: <--- AUTH TLS <--- EPRT <--- EPSV <--- MDTM <--- PASV <--- PBSZ <--- PROT <--- REST STREAM <--- SIZE <--- TVFS <--- UTF8 <--- 211 End ---> AUTH TLS <--- 234 Proceed with negotiation. ---> OPTS UTF8 ON Certificate depth: 0; subject: /C=CN/ST=Beijing/L=Beijing/O=SUSE/OU=QA/CN=shawn/emailAddress=weixuan.hao(a)suse.com; issuer: /C=CN/ST=Beijing/L=Beijing/O=SUSE/OU=QA/CN=shawn/emailAddress=weixuan.hao(a)suse.com ERROR: Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) **** Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) ---- Closing control socket ls: Fatal error: Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) lftp ftpuser@localhost:~> exit -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1207989] New: liblapacke.so.3 has unresolved references
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207989 Bug ID: 1207989 Summary: liblapacke.so.3 has unresolved references 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: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This was created to carry the info from the closed https://bugzilla.suse.com/show_bug.cgi?id=1087426 -- There undefined references in shared object file for the lapack library. Simple test program to reproduce #include <stdio.h> #include "lapacke.h" int main() { printf("Hello world!\n"); int* pi = NULL; double* pd = NULL; LAPACKE_dgesv(0, 1, 1, pd, 1, pi, pd, 1); return 0; } When trying to compile dynamically linked it give following error: s12-sp2-sss:~ # gcc -o test test.c -llapack -llapacke /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `clagge_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `clatms_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `dlagsy_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `slatms_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `zlatms_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `slagsy_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `dlagge_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `clagsy_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `claghe_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `zlagsy_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `slagge_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `zlagge_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `dlatms_' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/liblapacke.so: undefined reference to `zlaghe_' collect2: error: ld returned 1 exit status When lapacke is linked static it does work -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1184786] New: Deduplicate directory ownership with filesystem package
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1184786 Bug ID: 1184786 Summary: Deduplicate directory ownership with filesystem package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, checksec pointed out that various directories in our /usr are 0755 while they're 0555 on Fedora and Red Hat. For more hardened environments this might make a difference, as it prevents a user "root" that doesn't have DAC_OVERRIDE permission to no longer write/create files there. In order to achieve that, only one package need to own the permissions of that directory. currently we have various packages co-owning it, which means actual permission would depend on installation order, and we'd get installation conflicts. This can be prevented by de-duplicating directory ownership. this is a tracker bug that tracks the work related to it. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1198668] New: Tumbleweed: Purge old kernels service block during boot
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1198668 Bug ID: 1198668 Summary: Tumbleweed: Purge old kernels service block during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sometimes "Purge old kernels" service does not run after booting, but during boot, which slows down boot: $ LC_ALL=C journalctl -b 0 |grep -i purge Apr 20 08:16:01 dell5510 systemd[1]: Starting Purge old kernels... Apr 20 08:16:02 dell5510 zypper[1546]: Preparing to purge obsolete kernels... Apr 20 08:17:09 dell5510 systemd[1]: purge-kernels.service: Deactivated successfully. Apr 20 08:17:09 dell5510 systemd[1]: Finished Purge old kernels. Apr 20 08:17:09 dell5510 systemd[1]: purge-kernels.service: Consumed 53.594s CPU time. It started few weeks ago, it does not happen every boot, but maybe once a week. But bothered me enough to report the problem. $ LC_ALL=C rpm -qi purge-kernels-service Name : purge-kernels-service Version : 0 Release : 8.4 Architecture: noarch Install Date: Tue Feb 22 11:51:00 2022 Group : Unspecified Size : 346 License : MIT Signature : RSA/SHA256, Sat Feb 19 22:50:00 2022, Key ID b88b2fd43dbdc284 Source RPM : purge-kernels-service-0-8.4.src.rpm Build Date : Sat Feb 19 22:37:41 2022 ... $ lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220415 Codename: n/a -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1205636] New: zypper ps -s shows wrong command and no service
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205636 Bug ID: 1205636 Summary: zypper ps -s shows wrong command and no service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After zypper dup and restarting all services reported by zypper ps -s on openSUSE Tumbleweed, USB-hotplug did not work anymore. Reason is that zypper shows wrong commands and thus not the service, which needs a restart: # zypper ps -s The following running processes use deleted files: PID | PPID | UID | User | Command | Service ------+------+------------+------------+-------------+-------- 1 | 0 | 0 | root | systemd | 2682 | 2680 | 1366800143 | kukuk | systemd | 24860 | 1 | 0 | root | udevadm | But PID 24860 is: root 24860 0.0 0.1 29840 1436 ? Ss Nov21 0:00 /usr/lib/systemd/systemd-udevd Since zypper detects the wrong command and thus does not show, that systemd-udevd.service needs to be restarted, running udevd and installed udev rules don't match and in this case e.g. USB-hotplug does not work anymore, since no more kernel modules get loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1205157] New: nrpe: %pre needs usrmerge update
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205157 Bug ID: 1205157 Summary: nrpe: %pre needs usrmerge update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: lars.vogdt(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- nrpe.spec %pre does # check if the port for nrpe is already defined in /etc/services if grep -q %{nrpeport} %{_sysconfdir}/services ; then : OK - port already defined else %{nnmmsg} "Adding port %{nrpeport} to %{_sysconfdir}/services" echo "nrpe %{nrpeport}/tcp # Nagios nrpe" >> etc/services fi With usrmerge and /usr/etc/services, this means that installing nrpe will create /etc/services with just one line: nrpe 5666/tcp # Nagios nrpe Needless to say that you can find exactly this line in /usr/etc/services ;-) Please adjust the %pre script to also check /usr/etc/services. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1191381] New: gnu-compilers-hpc: Move rpm macros to %_rpmmacrodir
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1191381 Bug ID: 1191381 Summary: gnu-compilers-hpc: Move rpm macros to %_rpmmacrodir Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1191379 Found By: --- Blocker: --- rpm macros aren't config files for the administrator, as such they should be installed into %_rpmmacrodir (ie /usr/lib/rpm/macros.d) instead of /etc/rpm. Please consider adjusting gnu-compilers-hpc -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208498] New: groff: mom-pdf.pdf is dangling symlink
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208498 Bug ID: 1208498 Summary: groff: mom-pdf.pdf is dangling symlink Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/share/doc/packages/groff/pdf/mom-pdf.pdf: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203594] New: xscreensaver v 6.03 GL Slideshow fails
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203594 Bug ID: 1203594 Summary: xscreensaver v 6.03 GL Slideshow fails 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: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: suse(a)stanmiller.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to run the GL Slideshow screensaver v 6.03 fails with this message. X error in glslideshow: glslideshow: Failed request: 158 glslideshow: Major opcode: 151 () glslideshow: Resource id: 0x0 glslideshow: Serial number: 117 / 117 It appears (quick test) that all other savers work. Manually installing xscreensaver v 5.44, from Open Suse 15.3 on 15.4 works with no problems. -- You are receiving this mail because: You are on the CC list for the bug.

1 4