Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ArchLinux installation with Xfce4 #10

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Fix ArchLinux installation with Xfce4 #10

wants to merge 3 commits into from

Conversation

pgoltsev
Copy link

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'.

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
Copy link
Author

pgoltsev commented Oct 25, 2018

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!

Since servive-related users are unable to login it
is better to set their home directory to root of
a filesystem instead of a folder in /home.
@meefik
Copy link
Owner

meefik commented Nov 25, 2018

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 meefik force-pushed the master branch 9 times, most recently from 85e41b6 to 387a28d Compare August 12, 2019 13:25
@meefik meefik force-pushed the master branch 2 times, most recently from 1b30072 to 95f7f2c Compare November 5, 2019 20:29
@meefik meefik force-pushed the master branch 3 times, most recently from 7aff94d to cc09794 Compare January 3, 2020 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants