FS#69364 - Xfce4 fails to start (unable to contact settings server) unless network manager is connected

Attached to Project: Arch Linux
Opened by Tomas Mudrunka (harvie) - Monday, 18 January 2021, 21:06 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 12:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I am using XFCE4 with LXDM and NetworkManager.

When i unplug network cable from my laptop and reboot. I cannot login to XFCE.

After login in LXDM i see blank screen for a while and after minute there is a popup saying:

Unable to contact settings server
Could not connect: Connection refused

After clicking "close" it brings me back to LXDM.

When i plug in the ethernet cable and reboot it is fixed.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 21 April 2021, 12:48 GMT
Reason for closing:  Not a bug
Additional comments about closing:  user setup misconfiguration
Comment by Tomas Mudrunka (harvie) - Monday, 18 January 2021, 21:24 GMT
I can provide more informations if needed. But i dont know where to start.
Comment by Tomas Mudrunka (harvie) - Monday, 18 January 2021, 22:11 GMT
I´ve tried this and it DID NOT helped:
systemctl mask NetworkManager-wait-online.service
Comment by Tomas Mudrunka (harvie) - Monday, 18 January 2021, 23:22 GMT
when i try to call command xfconf-query -l
it says dbus-launch exited with code 1

when i try to execute dbus-launch manualy it says "autolaunch requested, but X11 support not compiled in. Cannot continue"

i am not sure if my investigation is going in the right direction, maybe this is irrelevant.
Comment by loqs (loqs) - Tuesday, 19 January 2021, 00:59 GMT
@harvie please try asking for support on the Arch forums, IRC channel or mailing list.
Comment by Tomas Mudrunka (harvie) - Tuesday, 19 January 2021, 13:11 GMT
i am discussing this on IRC

systemd-delta says:
[EXTENDED] /usr/lib/systemd/system/NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf

override contains: After=openvswitch.service
original contains: After=network-pre.target dbus.service

Not sure if this might be problem??
Comment by Tomas Mudrunka (harvie) - Tuesday, 19 January 2021, 13:40 GMT
lots of services with names starting "systemd-" do not start as well. all due to this same error.
once network is up and i can login, they start working again.

Jan 19 00:13:16 anemophobia systemd[738]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/: Input/output error
Jan 19 00:13:16 anemophobia systemd[738]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-timesyncd: Input/output error
Jan 19 00:13:16 anemophobia systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jan 19 00:13:16 anemophobia systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jan 19 00:13:16 anemophobia systemd[1]: Failed to start Network Time Synchronization.

Loading...