April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1116431] New: systemd tmpfiles does not clean-up sddm-auth files
by bugzilla_noreply＠novell.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1116431 Bug ID: 1116431 Summary: systemd tmpfiles does not clean-up sddm-auth files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin(a)winter-rosenheim.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Over time, the /tmp directory contains a growing number of sddm-auth files. The systemd tmpfile services makes no attempt to clean them up. I would suggest to add a rule to /etc/tmpfiles.d to remove these files. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1084717] New: The Leap 15.0 installation procedure creates a 500 MB EFI partition
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 Bug ID: 1084717 Summary: The Leap 15.0 installation procedure creates a 500 MB EFI partition Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Executing a default "fresh" Leap 15.0 installation (Build 153) results in a 500 MB EFI partition being created. Attempting to change the EFI partition size to something less than 256 MB results in an error message indicating that, "the partition size is much too small" being raised. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1168104] New: Issue with Patch openSUSE-2020-401
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1168104 Bug ID: 1168104 Summary: Issue with Patch openSUSE-2020-401 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running the Patch openSUSE-2020-401 from the KDE Update Plasma - PackageKit - results in the following errors being noted in the Zypper history: # 2020-03-29 15:26:07 Output of grub2-i386-pc-2.02-lp151.21.12.1.noarch.rpm %posttrans script: # update-bootloader: 2020-03-29 15:26:04 <3> update-bootloader-6892 run_command.294: '/usr/lib/bootloader/grub2-efi/ install' failed with exit code 127, output: # <<<<<<<<<<<<<<<< # target = x86_64-efi # + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg # copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/opensuse/grub.efi # x86_64-efi wird f374r Ihre Plattform installiert. # installation beendet. Keine Fehler aufgetreten. # /usr/sbin/shim-install: Zeile 326: efibootmgr: Kommando nicht gefunden. # /usr/sbin/shim-install: Zeile 352: efibootmgr: Kommando nicht gefunden. # >>>>>>>>>>>>>>>> # update-bootloader: 2020-03-29 15:26:07 <3> update-bootloader-6892 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 127, output: # <<<<<<<<<<<<<<<< # + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg # Generating grub configuration file ... # Found theme: /boot/grub2/themes/openSUSE/theme.txt # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.44-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.44-default # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.40-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.40-default # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.36-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.36-default # /etc/grub.d/80_suse_btrfs_snapshot: Zeile 7: btrfs: Kommando nicht gefunden. # >>>>>>>>>>>>>>>> -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1129549] New: YaST Control Center - Multilingual issue
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129549 Bug ID: 1129549 Summary: YaST Control Center - Multilingual issue Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- System Language and System Locale: de_DE.UTF-8 User "root" Locale: de_DE.UTF-8 Regardless of whether the Qt graphical user interface or the ncurses text-mode user interface, the following module names and, where noted, also the associated comment, are English: * "Software-Repositories" - comment also in English. * "Create New Directory Server" - comment also in English. * "Create New Kerberos Server" - comment also in English. * "User Logon Management" - comment also in English. The following German language module names have English comments: * "Datum und Zeit". * "Netzwerkeinstellungen". * "Benutzer und Gruppenverwaltung". -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1151703] New: python3-yamllint is missing requirement on python3-setuptools
by bugzilla_noreply＠novell.com 18 Jul '22

18 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1151703 Bug ID: 1151703 Summary: python3-yamllint is missing requirement on python3-setuptools Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jayvdb(a)gmail.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation yamllint tries to read out information during runtime using "pkg_resources" which is supplied by setuptools, if installed, but the package does not pull in this dependency. ## Steps to reproduce ``` $ docker run --rm -it registry.opensuse.org/opensuse/tumbleweed 5da80e2533ad:/ # zypper -n in python3-yamllint && yamllint Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ............................................[done] Building repository 'openSUSE-Tumbleweed-Non-Oss' cache .................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ................................................[done] Building repository 'openSUSE-Tumbleweed-Oss' cache .....................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Update' metadata .............................................[done] Building repository 'openSUSE-Tumbleweed-Update' cache ..................................................[done] Loading repository data... Reading installed packages... Resolving package dependencies... The following 9 NEW packages are going to be installed: libexpat1 libpython3_7m1_0 libuuid1 libyaml-0-2 python-rpm-macros python3-PyYAML python3-base python3-pathspec python3-yamllint 9 new packages to install. Overall download size: 8.9 MiB. Already cached: 0 B. After the operation, additional 34.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libexpat1-2.2.7-1.2.x86_64 (1/9), 87.7 KiB (206.3 KiB unpacked) Retrieving: libexpat1-2.2.7-1.2.x86_64.rpm ..............................................................[done] Retrieving package libpython3_7m1_0-3.7.3-1.3.x86_64 (2/9), 1.1 MiB ( 3.2 MiB unpacked) Retrieving: libpython3_7m1_0-3.7.3-1.3.x86_64.rpm .......................................................[done] Retrieving package libuuid1-2.34-2.1.x86_64 (3/9), 50.3 KiB ( 30.1 KiB unpacked) Retrieving: libuuid1-2.34-2.1.x86_64.rpm ................................................................[done] Retrieving package libyaml-0-2-0.2.2-2.1.x86_64 (4/9), 53.9 KiB (126.3 KiB unpacked) Retrieving: libyaml-0-2-0.2.2-2.1.x86_64.rpm ............................................................[done] Retrieving package python-rpm-macros-20190610.2ee3233-1.2.noarch (5/9), 25.8 KiB ( 47.0 KiB unpacked) Retrieving: python-rpm-macros-20190610.2ee3233-1.2.noarch.rpm ...........................................[done] Retrieving package python3-base-3.7.3-1.3.x86_64 (6/9), 7.2 MiB ( 29.7 MiB unpacked) Retrieving: python3-base-3.7.3-1.3.x86_64.rpm ...............................................[done (4.5 MiB/s)] Retrieving package python3-pathspec-0.5.9-1.4.noarch (7/9), 47.0 KiB (188.0 KiB unpacked) Retrieving: python3-pathspec-0.5.9-1.4.noarch.rpm .......................................................[done] Retrieving package python3-PyYAML-5.1.2-1.1.x86_64 (8/9), 189.8 KiB (739.6 KiB unpacked) Retrieving: python3-PyYAML-5.1.2-1.1.x86_64.rpm .........................................................[done] Retrieving package python3-yamllint-1.17.0-1.1.noarch (9/9), 71.9 KiB (294.0 KiB unpacked) Retrieving: python3-yamllint-1.17.0-1.1.noarch.rpm ......................................................[done] Checking for file conflicts: ............................................................................[done] (1/9) Installing: libexpat1-2.2.7-1.2.x86_64 ............................................................[done] (2/9) Installing: libpython3_7m1_0-3.7.3-1.3.x86_64 .....................................................[done] (3/9) Installing: libuuid1-2.34-2.1.x86_64 ..............................................................[done] (4/9) Installing: libyaml-0-2-0.2.2-2.1.x86_64 ..........................................................[done] (5/9) Installing: python-rpm-macros-20190610.2ee3233-1.2.noarch .........................................[done] (6/9) Installing: python3-base-3.7.3-1.3.x86_64 .........................................................[done] (7/9) Installing: python3-pathspec-0.5.9-1.4.noarch .....................................................[done] (8/9) Installing: python3-PyYAML-5.1.2-1.1.x86_64 .......................................................[done] (9/9) Installing: python3-yamllint-1.17.0-1.1.noarch ....................................................[done] Traceback (most recent call last): File "/usr/bin/yamllint", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' ``` ``` -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1165351] New: systemd libpam-systemd immediate memory exhaustion triggers oom upon ssh
by bugzilla_noreply＠novell.com 18 Jul '22

18 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1165351 Bug ID: 1165351 Summary: systemd libpam-systemd immediate memory exhaustion triggers oom upon ssh 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: luis.chamberlain(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a fresh install of OpenSUSE Tumbleweed on two HP ProLiant DL380 Gen9, its at version 20200222 right now both with 30 GiB of RAM using systemd-244-2.1.x86_64. On one of them I noticed that whenever I ssh in as a regular user but not root I see the out of memory killer triggered. That is.. 30 GiB of RAM eaten up. The system now has the debug boolean set on /etc/pam.d/common-session and sudo journalctl -f reveals: Feb 29 16:31:18 chivo sshd[16511]: Accepted publickey for mcgrof from 10.100.208.217 port 44016 ssh2: RSA SHA256:tOilLVI1jM/Pvg5uJVQbeXGEAU0mma6Jxma9c5eVX0w Feb 29 16:31:18 chivo sshd[16511]: pam_systemd(sshd:session): pam-systemd initializing Feb 29 16:31:18 chivo sshd[16511]: pam_systemd(sshd:session): Asking logind to create session: uid=1000 pid=16511 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.100.208.217 Feb 29 16:31:18 chivo sshd[16511]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 29 16:31:18 chivo systemd-logind[2184]: New session 62 of user mcgrof. Feb 29 16:31:18 chivo systemd[1]: Starting User Manager for UID 1000... -- <oom trace> --- Feb 29 16:31:34 chivo kernel: oom_reaper: reaped process 16513 ((systemd)), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Feb 29 16:31:34 chivo systemd[1]: user(a)1000.service: Failed with result 'protocol'. Feb 29 16:31:34 chivo systemd[1]: Failed to start User Manager for UID 1000. Feb 29 16:31:34 chivo systemd[1]: Started Session 62 of user mcgrof. Feb 29 16:31:34 chivo sshd[16511]: pam_systemd(sshd:session): Reply from logind: id=62 object_path=/org/freedesktop/login1/session/_362 runtime_path=/run/user/1000 session_fd=7 seat= vtnr=0 original_uid=1000 Feb 29 16:31:34 chivo sshd[16511]: pam_unix(sshd:session): session opened for user mcgrof(uid=1000) by (uid=0) Here's what a vmstat log looks like every second, first with the system on idle, then I create a new ssh session, it takes a while to eat up all the memory and then the oom takes over and kills the pam systemd service, and I am able to log in. The blank links are put in place below to highlight when the ssh session is just delaying and the oom is about to hit: mcgrof@chivo ~ $ sudo vmstat 1 procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 1 0 248704 31981364 136 160708 2 248 35 252 31 63 0 1 99 0 0 0 0 248704 31981056 136 160856 0 0 0 0 131 101 0 0 100 0 0 0 0 248704 31981056 136 160856 0 0 0 0 82 92 0 0 100 0 0 0 0 248704 31980552 136 160824 52 0 384 0 108 157 0 0 100 0 0 0 0 248704 31980472 136 161196 0 0 0 232 164 280 0 0 100 0 0 0 0 248704 31980200 136 161344 128 0 228 0 155 240 0 0 100 0 0 0 0 248704 31980200 136 161412 0 0 0 0 160 106 0 0 100 0 0 0 0 248704 31979628 136 161484 0 0 0 0 95 108 0 0 100 0 0 0 0 248704 31979628 136 161484 0 0 0 0 114 146 0 0 100 0 0 0 0 248704 31979628 136 161484 0 0 0 0 79 84 0 0 100 0 0 1 0 248704 31932744 136 161484 0 0 16 0 120 133 0 0 100 0 0 0 0 248704 31929664 136 161504 0 0 0 0 116 104 0 0 100 0 0 0 0 248704 31929640 136 161508 0 0 0 0 125 162 0 0 100 0 0 1 0 248704 28031352 136 163092 416 0 1940 0 574 515 3 2 95 0 0 1 0 248704 22681916 136 163092 0 0 64 340 473 354 3 2 95 0 0 1 0 248704 17326052 136 163172 0 0 0 0 364 116 3 2 95 0 0 1 0 248704 11968392 136 163172 0 0 0 0 364 124 3 2 95 0 0 1 0 248704 6612528 136 163172 0 0 0 0 374 110 3 2 95 0 0 1 0 248704 1257168 136 163172 0 0 0 0 366 114 3 2 95 0 0 1 1 565632 215044 136 82292 192 316912 1864 316912 1678 1135 1 2 91 6 0 2 1 954816 207848 136 76672 264 389708 1564 389708 30002 12569 0 1 89 9 0 3 2 353004 24513544 136 78252 140 139752 8480 139752 38917 113910 0 16 83 1 0 0 0 350444 32073372 136 122312 3040 24 42184 68 4774 14383 0 1 98 1 0 0 0 350444 32073372 136 122344 8 0 24 0 134 159 0 0 100 0 0 Running $(sudo htop --sort-key PERCENT_MEM -d 1) reveals the same but in a much more fun way. FWIW it is using yp, and I so I have: /etc/yp.conf domain suse.de server <some-private-ip> domain suse.de server <some-other-ip> However leaving this blank, running $(netconfig update -f), and then ssh'ing in reveals it still triggers. Related public issues: https://github.com/systemd/systemd/issues/11502 https://bugzilla.redhat.com/show_bug.cgi?id=1666690 https://github.com/systemd/systemd/commit/084eeb865ca63887098e0945fb4e93c85… Red Hat's bug reveals it was a bad backport of the fix for CVE-2018-16864 and so that itself introduced another CVE, CVE-2019-3815. I can reproduce very thing with a simple shiny new user created as user named test. The user root does not trigger the issue. What is however odd is that this issue is not reproducible on the other twin system. -- You are receiving this mail because: You are on the CC list for the bug.

2 85

[Bug 1041090] New: trackerbug: packages do not build reproducibly from unsorted input
by bugzilla_noreply＠novell.com 18 Jul '22

18 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1041090 Bug ID: 1041090 Summary: trackerbug: packages do not build reproducibly from unsorted input Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other 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/docs/stable-inputs/ When linking .o files in random filesystem order the linker will vary the ordering of functions and apply varying optimizations resulting 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 15

[Bug 1160091] New: Boinc Manager fails to auto-connect to localhost on application start
by bugzilla_noreply＠novell.com 15 Jul '22

15 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1160091 Bug ID: 1160091 Summary: Boinc Manager fails to auto-connect to localhost on application start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: marix(a)marix.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When starting up the Boinc Manager application (boinc-manager) it fails to utilise the credentials in gui_rpc_auth.cfg to automatically connect to the Boinc client running on localhost. Weirdly, the automatic connection to localhost does work if the Boinc Manager is started automatically by KDEs session restore. This works even when the client was not connected to localhost when the previous KDE session was ended. Using boinccmd on the command line also works flawlessly. My initial assumption was that this was somehow related to the desktop file of the Boinc manager. However, explicitly launching boinc-manager from the command line and thus bystepping the desktop file shows the same issue. The behaviour I'd expect would be for the client to behave identical when being launched via the application launcher and via KDE's session restore mechanism, ideally auto-connecting successfully in both cases. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1123721] New: suse-module-tools must not depend on mkintird / dracut
by bugzilla_noreply＠novell.com 14 Jul '22

14 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1123721 Bug ID: 1123721 Summary: suse-module-tools must not depend on mkintird / dracut 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Discussion on https://build.opensuse.org/request/show/657402 and via email. Email from Dominique Leuenberger, 2019-01-24 ------------- Some more thinking and tinkering around the problems with suse-module- tools - and your https://github.com/openSUSE/rpm-config-SUSE/pull/6 Adding a runtime dependency from suse-module-tools to dracut is a bad thing (with the current setup), as you already know: * coreutils buildrequires suse-module-tools in order to get the initrd macros in place. * coreutils is part of the distro bootstrap cycle (which is already large/too large). Adding dracut (plus dependency chain) into this cycle will make it close to impossible to bootstrap any new distro, namely SLE16 This shall not mean that dracut as a dependency on suse-module-tools is wrong per se, and as you did in the last weeks, we should try to find a solution for this issue, and I think the started path is not the worst: * we remove the macro to rebuild the initrd from suse-module-tools, and move that to a common place (rpm-config-SUSE comes to mind, it already contains commonly used macros) * With this, coreutils could completely give up on the dependency on suse-module-tools, which means s-module-tools could be downgraded from a ring0 to a ring1 package. The macro is already smart enough to skipt over the execution of /usr/lib/module-init-tools/regenerate-initrd- posttrans if it does not exist * An additional problem will show up though: dracut requires suse- module-tools, and suse-module-tools will require dracut. To break that cycle in OBS you will have to add a "#!BuildIgnore: suse-module-tools" to suse-module-tools.spec. This way forward would solve the technical difficulties we have around building a self-contained distro, without making it harder on the distro maintainers AND will allow us to add a dependency to s-m-t that is being interpreted by OBS (or we could even add a fileprovides then - once coreutils no longer cares for it) If any mail recipient has a valid reason AGAINST this plan, please speak up - but please also offer alternative solutions. Otherwise, let's get things moving. There are still two ring0 packages that will need touching (rpm-config-SUSE and coreutils) - and ring0 packages are 'tough' as they put a high load onto the distro build, meaning stagins willing to take them are scarse. ------------- https://github.com/openSUSE/rpm-config-SUSE/pull/6 has been accepted for rpm-config-SUSE. The initrd-related macros have _not_ been removed from suse-module-tools yet (15.0.20). The dependency on mkinitrd has been replaced by a weak "recommends". -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1123697] New: "rpm -V kernel-default" shows wrong permissions for initrd
by bugzilla_noreply＠novell.com 14 Jul '22

14 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1123697 Bug ID: 1123697 Summary: "rpm -V kernel-default" shows wrong permissions for initrd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # rpm -V kernel-default .M....... g /boot/initrd-4.12.14-25.23-default This happens on all distros at least since SLE12-SP3. The reason is that dracut creates the initrd with permissions 0600 (bug 1008340), but the kernel package contains a dummy initrd with permissions 0644. -- You are receiving this mail because: You are on the CC list for the bug.

2 30