Closed Strahinja closed 5 months ago
This line seems indicative:
It tells this path doesn't exist which is true and irrelevant. It happens for everyone.
Here's the example test command which will tell if this is problem with flatpak or dbus on your system. For 99% it's the latter. I see you don't have portals either.
Running that command gives:
$ flatpak run --command=flatpak-spawn com.github.Eloston.UngoogledChromium --sandbox echo 123
error: Unable to allocate instance id
Update: The command above was issued from the session started by slim, with the relevant parts of ~/.xinitrc:
#!/bin/sh
# ...
# WM override; if set, overrides and skips WM selection
WM=dwm
# List of WMs
wms="dwm:icewm-session:wmaker"
# ...
exec dbus-launch --exit-with-x11 -- env WM="$WM" wms="$wms" sh -c '{
if [ ! $WM ]; then
WM=$(printf "%s\n" "$wms" | tr : \\n |
dmenu -l 10 -fn "sans serif:size=24")
fi
/usr/libexec/pipewire-launcher
$WM; }'
I managed to get Ungoogled Chromium running simply by stopping slim with
# rc-service slim stop
and logging from getty, while having
# ...
startx
in my ~/.profile. So it seems this is some kind of interaction of slim with dbus, not present in Alpine v3.18, but present in v3.19. I'll close the issue for now, even though this is a workaround. I haven't tested other DMs. I usually use autostart X at login (startx
) on GNU/Linux, but I was testing slim for a couple of months on this particular system.
Summary of workaround: use autostart X at login, not slim.
The issue similar to #81 and https://github.com/flathub/com.discordapp.Discord/issues/349 is still happening for me after switching the repository URLs in Alpine Linux in /etc/apk/repositories to
v3.19
fromv3.18
, upgrading the system and flatpak and rebooting.This line seems indicative:
ie. the flatpak app expects to find the lib32 directory when the files in the flatpak are organized differently, as lib and lib64.