forked from obel1x/fedora-OEMDRV
0110_nextcloud_talk_app: fix Electron GPU crash on service exit
--scope ... & had two problems: 1. systemd-run stayed alive in the autostart service cgroup; KillMode=control-group sent it SIGTERM when logon_script.sh exited, tearing down the scope and killing Talk mid-initialization. 2. The scope lacked Delegate=yes, preventing Electron's zygote from creating sub-cgroups for the GPU/renderer processes. The previous commit added Delegate=yes but kept --scope, so problem 1 remained: the scope was still torn down on service exit, causing the GPU/network service crash visible in talk.log. Switch to a transient service unit identical to the Nextcloud Desktop Client fix: --no-block returns immediately so systemd-run is gone from the cgroup before the service ends; --property=Delegate=yes is retained for Electron's zygote. Tested: service active, zygote and network service running, no GPU crash. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -8,7 +8,7 @@ fi
|
||||
# Start Nextcloud Talk in Background
|
||||
#Current Version of Talk is dumping Core
|
||||
echo "Starting Nextcloud Talk in Background."
|
||||
systemd-run --user --scope --unit=nextcloud-talk --property=Delegate=yes \
|
||||
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=electron-wrapper --file-forwarding com.nextcloud.talk --background >${TEMPDIR}/talk.log 2>&1 &
|
||||
systemd-run --user --no-block --unit=nextcloud-talk.service --property=Delegate=yes \
|
||||
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=electron-wrapper --file-forwarding com.nextcloud.talk --background >>${TEMPDIR}/talk.log 2>&1
|
||||
|
||||
exit 0
|
||||
|
||||
Reference in New Issue
Block a user