linuxdeploy-cli icon indicating copy to clipboard operation
linuxdeploy-cli copied to clipboard

Fix ArchLinux installation with Xfce4

Open pgoltsev opened this issue 7 years ago • 2 comments
trafficstars

During install of dbus in ArchLinux there are missing 'network' group and some service-related users which are needed for correct start up of dbus. These users have been added manually via deployment script. Also command to run Xfce4 is different. For this distribution it has been changed to 'dbus-launch xfce4-session' instead of 'dbus-run-session xfce4-session'.

pgoltsev avatar Oct 25 '18 16:10 pgoltsev

Hi! I've faced with an issue installing ArchLinux with linuxdeploy on my Samsung Tab 10.1 SM-T520. During install there was a problem required package 'zstd' (I see you already added it in master). Once I added installation was complete but once I tried to start Xfce4 DE I got

:: Starting desktop/dbus ... dbus[4060]: Unknown username "systemd-timesync" in message bus configuration file
dbus[4060]: Unknown username "systemd-network" in message bus configuration file
dbus[4060]: Unknown username "colord" in message bus configuration file
dbus[4060]: Unknown username "systemd-resolve" in message bus configuration file
dbus[4060]: Unknown username "polkitd" in message bus configuration file
dbus[4060]: Unknown username "polkitd" in message bus configuration file
dbus[4060]: Unknown username "avahi" in message bus configuration file
dbus[4060]: Unknown group "network" in message bus configuration file

Once I added them manully, I got another error when I started XServer XSDL, it said something about broken session or missing XDG_CONFIG_HOME env variable. I googled and found that command dbus-launch worked instead of dbus-run-session. If the fix is dirty, you may adjust it according your preferences or I can do it if you point me on the right way. Cheers!

pgoltsev avatar Oct 25 '18 16:10 pgoltsev

Doesn't work for me :( "Failed to connect to socket /tmp/dbus-XXX: Connection refused"

Xfce works If I run xterm (/home/android/.xsession):

exec dbus-launch --exit-with-session xterm -max

and after that I run xfce4-session:

unset DBUS_SESSION_BUS_ADDRESS
xfce4-session

Or as single line:

exec dbus-launch --exit-with-session xterm -max -e "unset DBUS_SESSION_BUS_ADDRESS; exec xfce4-session"

List of dbus processes after success starting xfce4-session:

dbus     22602     1  0 22:05 ?        00:00:00 dbus-daemon --system --fork
android  27433     1  0 23:21 pts/17   00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session
android  27434     1  0 23:21 ?        00:00:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
android  27520 27514  0 23:21 ?        00:00:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3

What could be the reason for this behavior?

meefik avatar Nov 25 '18 20:11 meefik