Black screen after connecting , cc-novnc keeps exiting

[sticklerer]

Hi,
I'm trying to run this on my rpi and while i manage to open noVNC and connect it has a black screen and seems like that noVNC keeps crashing. The pi is running headless with no desk env , i don't know if it could be a problem or not .
Here is the log from the docker :
2024-10-08 10:18:07,231 INFO supervisord started with pid 1
2024-10-08 10:18:08,250 INFO spawned: 'easy-novnc' with pid 12
2024-10-08 10:18:08,257 INFO spawned: 'x11' with pid 13
2024-10-08 10:18:08,263 INFO spawned: 'cc-novnc' with pid 14
2024-10-08 10:18:08,270 INFO spawned: 'openbox' with pid 15
2024-10-08 10:18:09,273 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:09,274 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:09,275 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:09,275 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:19,105 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:19,313 INFO spawned: 'cc-novnc' with pid 34
2024-10-08 10:18:20,428 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:23,980 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:24,989 INFO spawned: 'cc-novnc' with pid 48
2024-10-08 10:18:25,998 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:28,077 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:29,089 INFO spawned: 'cc-novnc' with pid 60
2024-10-08 10:18:30,066 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:31,080 INFO spawned: 'cc-novnc' with pid 72
2024-10-08 10:18:32,065 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:34,078 INFO spawned: 'cc-novnc' with pid 84
2024-10-08 10:18:35,027 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:38,420 INFO spawned: 'cc-novnc' with pid 96
2024-10-08 10:18:39,424 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:39,541 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:40,552 INFO spawned: 'cc-novnc' with pid 108
2024-10-08 10:18:41,485 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:42,497 INFO spawned: 'cc-novnc' with pid 120
2024-10-08 10:18:43,481 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:45,488 INFO spawned: 'cc-novnc' with pid 132
2024-10-08 10:18:46,492 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:47,751 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:48,760 INFO spawned: 'cc-novnc' with pid 144
2024-10-08 10:18:49,764 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:18:50,119 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:51,124 INFO spawned: 'cc-novnc' with pid 156
2024-10-08 10:18:52,050 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:53,055 INFO spawned: 'cc-novnc' with pid 168
2024-10-08 10:18:53,989 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:55,998 INFO spawned: 'cc-novnc' with pid 180
2024-10-08 10:18:56,990 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:18:59,998 INFO spawned: 'cc-novnc' with pid 192
2024-10-08 10:19:01,000 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:19:01,075 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:02,084 INFO spawned: 'cc-novnc' with pid 204
2024-10-08 10:19:03,093 INFO success: cc-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-08 10:19:03,093 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:04,099 INFO spawned: 'cc-novnc' with pid 216
2024-10-08 10:19:05,027 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:06,032 INFO spawned: 'cc-novnc' with pid 228
2024-10-08 10:19:06,969 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:08,978 INFO spawned: 'cc-novnc' with pid 240
2024-10-08 10:19:09,952 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:12,960 INFO spawned: 'cc-novnc' with pid 252
2024-10-08 10:19:13,881 WARN exited: cc-novnc (exit status 127; not expected)
2024-10-08 10:19:14,892 INFO gave up: cc-novnc entered FATAL state, too many start retries too quickly

[sticklerer]

Forgot to post the picture

[Staninna]

Hey there! Thanks for reaching out. This is my first issue on a repo, and I'm sorry I overlooked it. I'll redeploy on my own server soon, and if the problem continues, I'll investigate further. Let me know if you're still experiencing the issue, and if you fixed it yourself, please share the solution for others! :)

[sticklerer]

Hi ! Haven't tried since i opened the issue but i can also try again to check if it still happens . I will post an update when i've done it but i'm also looking forward to your results .

[qinz1yang]

Hi! Thanks for the issue and the wonderful project! This issue comes from electron and here is a quick fix:

• Replace libasound2 with libasound2t64 in the Dockerfile.
• Install Electron locally (via npm install electron --save-dev) in the Dockerfile
• Use npx electron . instead of electron . in cc-novnc.sh

I cannot upload the .sh file here, but just in case you can retrieve the Dockerfile and cc-novnc.sh I edited here: https://github.com/qinz1yang/cc-novnc

I also submitted a pull request( I am not sure whether I am doing this correctly). I am not a CS major and it is my very first time contributing on github. Please forgive me if I am messing things up.

Thanks Staninna again for the great project, this is exactly what I am dreaming for.