[Bug]: Black screen on launch

[kevinpastor]

Describe the Bug

After the last update, I have a black screen on launch. The cursor does show up though. I tried downgrading the GPU driver version, but I still have the same issue.

In the logs, it seems like the desktop process is trying to launch, but fails. It then loops infinitely trying to launch it again.

Steps to Reproduce

No response

Expected Behavior

No response

Screenshots

No response

Relevant Settings

No response

Version

latest

Platform

• Distribution: Debian GNU/Linux - 11 (bullseye)
• Linux Kernel: 6.1.36-Unraid unknown unknown GNU/Linux
• GPU Driver versions: 535.54.03
• Docker: 20.10.18, build b40c2f6
• Docker-compose:20.10.18, build b40c2f6

Relevant log output

2023-07-07 15:47:51,170 INFO supervisord started with pid 1
2023-07-07 15:47:52,172 INFO spawned: 'dbus' with pid 265
2023-07-07 15:47:52,175 INFO spawned: 'udev' with pid 266
2023-07-07 15:47:52,178 INFO spawned: 'dind' with pid 267
2023-07-07 15:47:52,181 INFO spawned: 'xorg' with pid 269
2023-07-07 15:47:52,185 INFO spawned: 'novnc' with pid 271
2023-07-07 15:47:52,188 INFO spawned: 'pulseaudio' with pid 274
2023-07-07 15:47:52,192 INFO spawned: 'vncproxy' with pid 280
2023-07-07 15:47:52,195 INFO spawned: 'x11vnc' with pid 282
2023-07-07 15:47:52,199 INFO spawned: 'desktop' with pid 287
2023-07-07 15:47:52,200 INFO reaped unknown pid 259 (exit status 127)
PULSEAUDIO: Starting pulseaudio service
2023-07-07 15:47:52,202 INFO success: vncproxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-07-07 15:47:52,219 INFO exited: dind (exit status 4; not expected)
2023-07-07 15:47:52,219 INFO reaped unknown pid 317 (exit status 0)
2023-07-07 15:47:53,213 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,213 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,214 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,214 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,214 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,214 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:53,214 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:54,205 INFO spawned: 'dind' with pid 344
2023-07-07 15:47:54,237 INFO exited: dind (exit status 4; not expected)
2023-07-07 15:47:55,067 INFO exited: desktop (exit status 1; not expected)
2023-07-07 15:47:55,476 INFO spawned: 'desktop' with pid 369
2023-07-07 15:47:55,494 INFO reaped unknown pid 373 (exit status 0)
2023-07-07 15:47:56,772 INFO spawned: 'dind' with pid 385
2023-07-07 15:47:56,773 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:58,467 INFO success: dind entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-07 15:47:59,522 INFO exited: desktop (exit status 1; not expected)
2023-07-07 15:48:00,528 INFO spawned: 'desktop' with pid 539

[HarmonyTechLabs]

I had the same, I restarted the container and it came right up.

[Josh5]

I did post an announcement about this in a couple of places. You must have missed it. The desktop is waiting for the flatpaks to be downloaded for the first time.