Closed Markarian421 closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Nice find, I will get a solution in the bases for audio in priv mode
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This is fixed in the latest build.
I just stumbled across this problem and can confirm that this problem also exists for debian-kde.
I helped myself with a workaround by modifying /etc/s6-overlay/s6-rc.d/svc-de/run
tmp
exist/usr/bin/dbus-launch
before startwm.sh
to export the DBUS env variables systemwide#!/usr/bin/with-contenv bash
if ! mountpoint -q /tmp; then
mount -t tmpfs none /tmp
fi
cd $HOME
exec s6-setuidgid abc \
/usr/bin/dbus-launch \
/bin/bash /defaults/startwm.sh
I am not sure this is a good and general solution but it worked for debian-kde
👍
Is there an existing issue for this?
Current Behavior
System Settings won't start from menu. Starting from shell (/usr/bin/systemsettings) yields:
Problem seems to be that docker-in-docker (dind) initialization does a very late
mount -t tmpfs none /tmp
which shadows the initial /tmp containing the dbus unix socket. (s6 svc-docker depends on svc-de and even waits 5s before calling/usr/local/bin/dockerd-entrypoint.sh
. This seems due to avoid some interference with pulseaudio startup.Have verified that e.g. introducing a dependency from svc-de to a new s6 init-tmp-mount script that does
fixes the problem.
Expected Behavior
The System Settings control panel should open.
Steps To Reproduce
This seems reproducible directly after all fresh starts of the container.
Environment
CPU architecture
x86-64
Docker creation
Container logs