July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227092] New: network/boinc-client: Add WorkingDirectory= to unit file (and other possible unit file enhancements)
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227092 Bug ID: 1227092 Summary: network/boinc-client: Add WorkingDirectory= to unit file (and other possible unit file enhancements) Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: chris(a)computersalat.de Reporter: timuzhti(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: Sascha.Manns(a)outlook.de Target Milestone: --- Found By: --- Blocker: --- This is a pretty minor issue but without WorkingDirectory= set, the ExecStop= command (/usr/bin/boinccmd --quit) does not actually function because it can't find the gui_rpc_auth.cfg file. This causes the unit to report failure every time it's stopped. According to documentation, boinccmd checks three places for the password (it doesn't have a --datadir option). Changing the working directory to either /var/lib/boinc or ~ (which is the same thing by default) seems to be the easiest way to resolve this, since /etc/boinc-client/ and /var/lib/boinc-client are not used by default. I'm not really sure which of the two options would be better. Using the home directory of the boinc user would probably make it easier to reconfigure to another directory, but I'm not sure that's worth it. It might be even better to somehow pull $BOINC_BOINC_DIR into WorkingDirectory= but systemd doesn't seem to support this. Another quirk uncovered looking at the logs is that systemd apparently interprets /lockfile as part of the variable name, sample log message as follows: (rm): boinc-client.service: Invalid environment variable name evaluates to an empty string: BOINC_BOINC_DIR/lockfile This can be avoided by wrapping the variable name in braces, ExecStopPost=/bin/rm -f ${BOINC_BOINC_DIR}/lockfile though I'm not sure if this is actually a systemd issue. Finally, the upstream unit file at https://github.com/BOINC/boinc/blob/master/client/scripts/boinc-client.serv… includes a couple of systemd hardening options. Some of these are off by default because Atlas requires setuid root, but the three options limiting the read/write access of the unit to the boinc directory only might be worthwhile. ProtectSystem=full ProtectControlGroups=true ReadWritePaths=-/var/lib/boinc -/etc/boinc-client -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227467] New: libSDL2_mixer-2_0-0-32bit missing
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227467 Bug ID: 1227467 Summary: libSDL2_mixer-2_0-0-32bit missing Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: asdhio(a)tuta.io QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0 Build Identifier: libSDL2_mixer-2_0-0-32bit is missing from default repos. It was available in Leap 15.5, but went missing in Leap 15.6 (and in addition, Tumbleweed). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227468] New: my hotkey for power management (suspend) stop working
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227468 Bug ID: 1227468 Summary: my hotkey for power management (suspend) stop working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: devguy.ca(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have my shortcut key WIN+ALT+PAUSE set to suspend under power management, but it stop working a few days ago. I've checked and it's still set. All my other shortcut seem to still work fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227139] Redis→valkey migration sets wrong permissions
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227139 https://bugzilla.suse.com/show_bug.cgi?id=1227139#c3 --- Comment #3 from Paul Uiterlinden <paulu(a)xs4all.nl> --- Two additional comments about script /usr/libexec/migrate_redis_to_valkey.bash 1) It searches service files only in /etc/systemd/system. Shouldn't /usr/lib/systemd/system be included as well? On my system the redis service files cannot be found under /etc/systemd/system. The are located under /usr/lib/systemd/system: -rw-r--r-- 1 root root 680 May 19 15:57 /usr/lib/systemd/system/redis@.service -rw-r--r-- 1 root root 744 May 19 15:57 /usr/lib/systemd/system/redis-sentinel@.service 2) The script contains the line: chown -R valkey. /var/lib/valkey The dot should have been a colon, considering this warning: chown: warning: '.' should be ':': 'valkey.' -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227139] Redis→valkey migration sets wrong permissions
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227139 https://bugzilla.suse.com/show_bug.cgi?id=1227139#c2 Paul Uiterlinden <paulu(a)xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paulu(a)xs4all.nl --- Comment #2 from Paul Uiterlinden <paulu(a)xs4all.nl> --- This update breaks Nextcloud. OS: openSUSE Tumbleweed aarch64, Version 20240629 NextCloud: 29.0.3.4 (installed outside zypper) Zypper output: # zypper dup Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: valkey valkey-compat-redis The following package is going to be REMOVED: redis 2 new packages to install, 1 to remove. Overall download size: 1.5 MiB. Already cached: 0 B. After the operation, 30.6 KiB will be freed. Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): Retrieving: valkey-7.2.5-3.1.aarch64 (openSUSE-Tumbleweed-Oss) (1/2), 1.5 MiB Retrieving: valkey-7.2.5-3.1.aarch64.rpm .....................................................................................................[done (3.8 MiB/s)] Retrieving: valkey-compat-redis-7.2.5-3.1.noarch (openSUSE-Tumbleweed-Oss) (2/2), 8.6 KiB Retrieving: valkey-compat-redis-7.2.5-3.1.noarch.rpm .....................................................................................................[done] Checking for file conflicts: .............................................................................................................................[done] /usr/bin/systemd-sysusers - Creating group 'valkey' with GID 460. Creating user 'valkey' (User for valkey key-value store) with UID 460 and GID 460. See /usr/share/doc/packages/valkey/README.SUSE to continue (1/2) Installing: valkey-7.2.5-3.1.aarch64 ...............................................................................................................[done] /etc/redis/*.conf has been copied to /etc/valkey. Manual review of adjusted configs is strongly suggested. chown: warning: '.' should be ':': 'valkey.' On-disk redis dumps copied from /var/lib/redis/ to /var/lib/valkey Removed "/etc/systemd/system/redis.target.wants/redis(a)default.service". Removed "/etc/systemd/system/multi-user.target.wants/redis(a)default.service". Warning: The unit file, source configuration file or drop-ins of redis.target changed on disk. Run 'systemctl daemon-reload' to reload units. Failed to stop redis@.service: Unit name redis@.service is missing the instance name. See system logs and 'systemctl status redis@.service' for details. Warning: The unit file, source configuration file or drop-ins of redis-sentinel.target changed on disk. Run 'systemctl daemon-reload' to reload units. Failed to stop redis-sentinel@.service: Unit name redis-sentinel@.service is missing the instance name. See system logs and 'systemctl status redis-sentinel@.service' for details. warning: file /var/lib/redis: remove failed: No such file or directory (2/2) Installing: valkey-compat-redis-7.2.5-3.1.noarch ...................................................................................................[done] Running post-transaction scripts .........................................................................................................................[done] valkey is not started, also not after reboot, or trying to start manually via systemctl. Consequently, Nextcloud fails to start: Jul 06 21:18:16 ari-pi systemd[1]: Started Nextcloud cron.php job. Jul 06 21:18:17 ari-pi php[1732]: RedisException: No such file or directory in /srv/www/htdocs/nextcloud/lib/private/RedisFactory.php:117 Jul 06 21:18:17 ari-pi php[1732]: Stack trace: Jul 06 21:18:17 ari-pi php[1732]: #0 /srv/www/htdocs/nextcloud/lib/private/RedisFactory.php(117): Redis->pconnect() Jul 06 21:18:17 ari-pi php[1732]: #1 /srv/www/htdocs/nextcloud/lib/private/RedisFactory.php(158): OC\RedisFactory->create() Jul 06 21:18:17 ari-pi php[1732]: #2 /srv/www/htdocs/nextcloud/lib/private/Memcache/Redis.php(73): OC\RedisFactory->getInstance() Jul 06 21:18:17 ari-pi php[1732]: #3 /srv/www/htdocs/nextcloud/lib/private/Memcache/Redis.php(79): OC\Memcache\Redis->getCache() Jul 06 21:18:17 ari-pi php[1732]: #4 /srv/www/htdocs/nextcloud/lib/private/App/InfoParser.php(56): OC\Memcache\Redis->get() Jul 06 21:18:17 ari-pi php[1732]: #5 /srv/www/htdocs/nextcloud/lib/private/App/AppManager.php(727): OC\App\InfoParser->parse() Jul 06 21:18:17 ari-pi php[1732]: #6 /srv/www/htdocs/nextcloud/lib/private/AppFramework/App.php(72): OC\App\AppManager->getAppInfo() Jul 06 21:18:17 ari-pi php[1732]: #7 /srv/www/htdocs/nextcloud/lib/private/legacy/OC_App.php(157): OC\AppFramework\App::buildAppNamespace() Jul 06 21:18:17 ari-pi php[1732]: #8 /srv/www/htdocs/nextcloud/lib/private/AppFramework/Bootstrap/Coordinator.php(119): OC_App::registerAutoloading() Jul 06 21:18:17 ari-pi php[1732]: #9 /srv/www/htdocs/nextcloud/lib/private/AppFramework/Bootstrap/Coordinator.php(90): OC\AppFramework\Bootstrap\Coordinator->registerApps() Jul 06 21:18:17 ari-pi php[1732]: #10 /srv/www/htdocs/nextcloud/lib/base.php(706): OC\AppFramework\Bootstrap\Coordinator->runInitialRegistration() Jul 06 21:18:17 ari-pi php[1732]: #11 /srv/www/htdocs/nextcloud/lib/base.php(1181): OC::init() Jul 06 21:18:17 ari-pi php[1732]: #12 /srv/www/htdocs/nextcloud/cron.php(58): require_once('...') Jul 06 21:18:17 ari-pi php[1732]: #13 {main} Jul 06 21:18:17 ari-pi systemd[1]: nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE Jul 06 21:18:17 ari-pi systemd[1]: nextcloud-cron.service: Failed with result 'exit-code'. Jul 06 21:18:17 ari-pi systemd[1]: nextcloud-cron.service: Consumed 1.059s CPU time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227461] New: KRdp requires ffmpeg from Packman (missing h264 encoder)
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227461 Bug ID: 1227461 Summary: KRdp requires ffmpeg from Packman (missing h264 encoder) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I go to KDE System Settings, and then select the “Remote Desktop” sub-menu, I see the following error at the top of the window: “Remote desktop cannot be enabled because your system does not support H264 video encoding. Please contact your distribution regarding how to enable it.” libopenh264 is installed. My gut feeling is that openSUSE patches ffmpeg to load openh264 library on demand and checks that KRdp performs do not trigger loading of it. Internet search only finds this issue on openSUSE which indirectly confirms it. … quickly checking - yes, replacing ffmpeg packages (and only ffmpeg packages) with Packman version fixes KRdp error. See details in https://forums.opensuse.org/t/plasma-remote-desktop-krdp-and-h264-video-enc… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227462] New: Stressapptest (Package): Process Error: Sat::Initialize() failed
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227462 Bug ID: 1227462 Summary: Stressapptest (Package): Process Error: Sat::Initialize() failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bejoro(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh installation of openSUSE Tumbleweed (KDE). Installed stressapptest package. stressapptest reports an error at execution. This happens on all of my systems. I am using openSUSE Tumbleweed for about 2 years and stressapptest never worked. With Fedora on the identical system stressapptest works perfectly fine. I have to use a Fedora live system to test my hardware. Error message: ❯ stressapptest 2024/07/04-14:42:44(CEST) Log: Commandline - stressapptest 2024/07/04-14:42:44(CEST) Stats: SAT revision 1.0.11_autoconf, 64 bit binary 2024/07/04-14:42:44(CEST) Log: reproducible @ reproducible on Sun Nov 26 17:19:40 UTC 2023 from open source release 2024/07/04-14:42:44(CEST) Log: 1 nodes, 16 cpus. 2024/07/04-14:42:44(CEST) Process Error: Running DEBUG version of SAT, with significantly reduced coverage. 2024/07/04-14:42:44(CEST) Log: Command line option '-A' bypasses this error. 2024/07/04-14:42:44(CEST) Process Error: Sat::Initialize() failed 2024/07/04-14:42:44(CEST) 2024/07/04-14:42:44(CEST) Status: FAIL - test encountered procedural errors 2024/07/04-14:42:44(CEST) 2024/07/04-14:42:44(CEST) Process Error: Fatal issue encountered. See above logs for details. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227464] New: Please subpackage the grub binaries into grub2-bin
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227464 Bug ID: 1227464 Summary: Please subpackage the grub binaries into grub2-bin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: daan.j.demeyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently the grub2 package contains both all the grub binaries and configures the system to use grub as the bootloader. As such it correctly conflicts with sdbootutil-rpm-scriptlets, causing failures when trying to install grub2 on a system with systemd-boot already installed. I want to be able to install the grub binaries without configuring the system to use grub as the bootloader. So please introduce a subpackage grub2-bin or so that contains all the grub binaries (everything from grub in /usr/bin) so that the grub binaries can be installed independently from making the system use grub as the bootloader. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225982] New: mtools: Add missing dependency on glibc-gconv-modules-extra
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225982 Bug ID: 1225982 Summary: mtools: Add missing dependency on glibc-gconv-modules-extra 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: daan.j.demeyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- From the glibc changelog: ``` 2024-05-21 - Andreas Schwab <schwab(a)suse.de> - Move essential (Latin-1 and UTF based) gconv modules to main glibc package, other modules to new package glibc-gconv-modules-extra ``` This causes mcopy to fail with the following if glibc-gconv-modules-extra is not installed: ``` Cannot initialize conversion from codepage 850 to UTF-8: Invalid argument Cannot initialize conversion from UTF-8 to codepage 850: Invalid argument Using internal CP850 conversion table mkfs.fat 4.2 (2021-01-31) Error converting to codepage 850 Invalid argument Error setting code page Cannot initialize '::' ::: Invalid argument ``` Please add a dependency on glibc-gconv-modules-extra. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226512] New: Lenovo B570 does not power off after shutdown
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226512 Bug ID: 1226512 Summary: Lenovo B570 does not power off after shutdown Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bob(a)vickers.simplyms.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875571 --> https://bugzilla.suse.com/attachment.cgi?id=875571&action=edit /var/log/messages I recently repurposed an old Lenovo B570 laptop by installing Leap 15.6 on it and there is a problem shutting it down: the system shuts down but the computer does not power off, and continues to use battery. I need to hold the power button down for a few seconds to shut down properly. It seems to do this regardless of how I shut down; I have tried shutting the lid, using the XFCE menu, also # shutdown -h now and # echo o > /proc/sysrq-trigger I've googled and found similar problems in years gone by, also a more recent Fedora one at https://discussion.fedoraproject.org/t/unable-to-shut-down-system-after-lat… None gives a solution other than "upgrade to the latest software". Previously this computer ran a 32-bit version of Ubuntu, without encountering this problem. I've attached the end of /var/log/messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 2