XFCE only wakes up to blackscreen and mouse pointer

[Joe_Ge]

After the latest kernel updates my system dont loads the desktop anymore.
After suspend, it awakes, but only shows a black screen with only the mouse pointer.

I changed lately the video card from a gtx960 to a gtx750, but still the same problem.

When i load my backup system with Kernel 6.1.62-1 it still works normal.
When i boot with the current system with Kernel 6.1.69-1, it still stucks and i have to restart lightdm.

This problem did appear right with the kernel update.

Latest journald-log, from where i pressed a key until i restarted lightdm from TTY.

30.12.23 18:35	systemd-logind	Operation 'sleep' finished.
30.12.23 18:35	ModemManager	<msg> [sleep-monitor-systemd] system is resuming
30.12.23 18:35	NetworkManager	<info>  [1703957730.9032] manager: sleep: wake requested (sleeping: yes  enabled: yes)
30.12.23 18:35	NetworkManager	<info>  [1703957730.9034] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
30.12.23 18:35	kernel	RTL8211B Gigabit Ethernet r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_hq
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_sq
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_mq
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/aptx_hd
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/aptx_hd
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/aptx
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/aptx
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_453
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_453
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_512
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_512
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_552
30.12.23 18:35	bluetoothd	Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_552
30.12.23 18:35	NetworkManager	<info>  [1703957731.0740] manager: NetworkManager state is now DISCONNECTED
30.12.23 18:35	kernel	r8169 0000:03:00.0 enp3s0: Link is Down
30.12.23 18:35	ModemManager	<msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:0a.0/0000:03:00.0': not supported by any plugin
30.12.23 18:35	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
30.12.23 18:35	NetworkManager	<info>  [1703957738.4279] device (enp3s0): carrier: link connected
30.12.23 18:35	kernel	r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
30.12.23 18:35	kernel	IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
30.12.23 18:35	NetworkManager	<info>  [1703957738.4285] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957738.4300] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (97463cd5-5afd-3881-be37-2aaeb4ca2deb)
30.12.23 18:35	NetworkManager	<info>  [1703957738.4312] device (enp3s0): Activation: starting connection 'Kabelgebundene Verbindung 1' (97463cd5-5afd-3881-be37-2aaeb4ca2deb)
30.12.23 18:35	NetworkManager	<info>  [1703957738.4314] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957738.4322] manager: NetworkManager state is now CONNECTING
30.12.23 18:35	NetworkManager	<info>  [1703957738.4327] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957738.4337] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957738.4348] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
30.12.23 18:35	avahi-daemon	Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::40d1:baed:d064:ce58.
30.12.23 18:35	avahi-daemon	New relevant interface enp3s0.IPv6 for mDNS.
30.12.23 18:35	avahi-daemon	Registering new address record for fe80::40d1:baed:d064:ce58 on enp3s0.*.
30.12.23 18:35	dbus-daemon	[system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=1052 comm="/usr/bin/NetworkManager --no-daemon")
30.12.23 18:35	NetworkManager	<info>  [1703957740.4389] dhcp4 (enp3s0): state changed new lease, address=192.168.178.32
30.12.23 18:35	NetworkManager	<info>  [1703957740.4401] policy: set 'Kabelgebundene Verbindung 1' (enp3s0) as default for IPv4 routing and DNS
30.12.23 18:35	avahi-daemon	Joining mDNS multicast group on interface enp3s0.IPv4 with address 192.168.178.32.
30.12.23 18:35	avahi-daemon	New relevant interface enp3s0.IPv4 for mDNS.
30.12.23 18:35	avahi-daemon	Registering new address record for 192.168.178.32 on enp3s0.IPv4.
30.12.23 18:35	systemd	Starting Network Manager Script Dispatcher Service...
30.12.23 18:35	dbus-daemon	[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
30.12.23 18:35	systemd	Started Network Manager Script Dispatcher Service.
30.12.23 18:35	NetworkManager	<info>  [1703957740.5050] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957740.5185] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957740.5191] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
30.12.23 18:35	NetworkManager	<info>  [1703957740.5201] manager: NetworkManager state is now CONNECTED_SITE
30.12.23 18:35	NetworkManager	<info>  [1703957740.5209] device (enp3s0): Activation: successful, device activated.
30.12.23 18:35	NetworkManager	<info>  [1703957740.5802] dhcp6 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
30.12.23 18:35	NetworkManager	<info>  [1703957740.5815] policy: set 'Kabelgebundene Verbindung 1' (enp3s0) as default for IPv6 routing and DNS
30.12.23 18:35	avahi-daemon	Leaving mDNS multicast group on interface enp3s0.IPv6 with address fe80::40d1:baed:d064:ce58.
30.12.23 18:35	avahi-daemon	Joining mDNS multicast group on interface enp3s0.IPv6 with address 2003:d7:2f45:1e00:e61:c8e6:1b4b:62f0.
30.12.23 18:35	avahi-daemon	Registering new address record for 2003:d7:2f45:1e00:e61:c8e6:1b4b:62f0 on enp3s0.*.
30.12.23 18:35	avahi-daemon	Withdrawing address record for fe80::40d1:baed:d064:ce58 on enp3s0.
30.12.23 18:35	NetworkManager	<info>  [1703957740.6236] dhcp6 (enp3s0): state changed new lease
30.12.23 18:35	NetworkManager	<info>  [1703957740.6439] manager: NetworkManager state is now CONNECTED_GLOBAL
30.12.23 18:35	avahi-daemon	Withdrawing address record for 192.168.178.32 on enp3s0.
30.12.23 18:35	avahi-daemon	Withdrawing address record for ::1 on lo.
30.12.23 18:35	avahi-daemon	Withdrawing address record for 127.0.0.1 on lo.
30.12.23 18:35	avahi-daemon	Host name conflict, retrying with oli-2
30.12.23 18:35	avahi-daemon	Registering new address record for 2003:d7:2f45:1e00:e61:c8e6:1b4b:62f0 on enp3s0.*.
30.12.23 18:35	avahi-daemon	Registering new address record for 192.168.178.32 on enp3s0.IPv4.
30.12.23 18:35	avahi-daemon	Registering new address record for ::1 on lo.*.
30.12.23 18:35	avahi-daemon	Registering new address record for 127.0.0.1 on lo.IPv4.
30.12.23 18:35	avahi-daemon	Server startup complete. Host name is oli-2.local. Local service cookie is 827352193.
30.12.23 18:35	systemd	Started Getty on tty2.
30.12.23 18:35	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
30.12.23 18:35	dbus-daemon	[system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.75' (uid=0 pid=2536 comm="/bin/login -p --    ")
30.12.23 18:35	dbus-daemon	[system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
30.12.23 18:35	login	pam_unix(login:session): session opened for user xxxx(uid=1000) by oli(uid=0)
30.12.23 18:35	systemd-logind	New session 4 of user xxxx.
30.12.23 18:35	systemd	Started Session 4 of User xxxx.
30.12.23 18:35	login	LOGIN ON tty2 BY xxxx
30.12.23 18:35	dbus-daemon	[system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.77' (uid=0 pid=2558 comm="sudo systemctl restart lightdm")
30.12.23 18:35	dbus-daemon	[system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
30.12.23 18:36	sudo	     xxxx : TTY=tty2 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/systemctl restart lightdm
30.12.23 18:36	sudo	pam_unix(sudo:session): session opened for user root(uid=0) by oli(uid=1000)
30.12.23 18:36	systemd	Stopping Light Display Manager...
30.12.23 18:36	at-spi-bus-launcher	X connection to :0 broken (explicit kill or server shutdown).

[andreas85]

Welcome to Manjaro!

1. Please read the information behind this link. It will help you to post necessary information.

[HowTo] Request support

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major points. Provide context Simply signaling an issue is rarely enough to understand how it occurred. It is thus important to provide details on how it happened: Detail prior actions leading to the issue. List solutions and guides you already tried, with links when…

2. Please press the three dots … below your post and then press the

• If you give us information about your system, we can see what we’re talking about and make better suggestions.
• You can do this by using inxi in a terminal or in console.

sudo inxi --admin --verbosity=7 --filter --no-host --width

• Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
• Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.

3. Copy the output from inxi (including the command) and paste it into your post.

• To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

[HowTo] Post command output and file content as formatted text

Difficulty: ★☆☆☆☆ Formatting differences Discourse – this forum’s engine – uses Markdown to format its posts, and removes “unnecessary” whitespace. Terminal commands often produce output formatted so that they are better readable by the user, taking advantage of the monospaced font used. Programming code often rely on indentation to make it more readable. Using preformatting in Markdown Markdown includes a pattern to provide preformatting when necessary. You only need to put the part to f…

Have you already for your problem in the forum ? (Wisdom lies in asking → listening → reading )

[Joe_Ge]

Andreas, why do you spam always this message at every topic.
The problem is at the kernels, not my system.

And second, you dont offer any help, only post you standard comment.
Stop that at my topics in future please, since you dont offer more.

[andreas85]

@Joe_Ge

Stop that at my topics in future please,

As you wish

[Joe_Ge]

Today it seems it fixed it. So far it works the last half day.
There are 2 possible solution, where #1 seems works better.

It seems its a problem at settings - power managment - system - System power saving.
At the tab System i set system sleep mode from hibernate-sleep to suspend.

As shown here, the second graphic below.
https://docs.xfce.org/xfce/xfce4-power-manager/preferences

and also described as a problem at 2019 related to light-locker
https://askubuntu.com/questions/1132291/screen-goes-dark-after-suspending-or-locking-from-xfce-logout-menu

The second method was do delete ```~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml``
or simple rename it once, after you reload your session, xfce4 will create that file again, just maybe with an other resolution.
As seen here

XFCE blank/black screen with cursor after login (solution)

and here from the topic.

black screen at desktop login [GTX 750 Ti] [390.25]

I did both at the same time, and now it works again, that there is not only a black screen with only a mousepointer on it.
Maybe its related to eachother, if the first one doesnt work, that xfce has to create a new displays.xml.

I also tested, to set back hibernate at powermanagment, and only deleted/renamed displays.xml again, but it didnt work, i got the black screen back.
Setting the powermanagement back to suspend seems works better to avoide this black screen.