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

Screenshot broken #136

Open
CrazyWolf13 opened this issue Apr 19, 2024 · 1 comment
Open

Screenshot broken #136

CrazyWolf13 opened this issue Apr 19, 2024 · 1 comment

Comments

@CrazyWolf13
Copy link

Hi @Lissy93
Awesome tool you created!

Deployed my own, but sadly the screenshot tool is not working correctly?

I'm running the latest docker and getting the following error:

Failed to load resource: the server responded with a status of 500 (Internal Server Error)
instrument.ts:132 Fetch Error - screenshot[13:40:32] The screenshot job failed after 582ms, with the following error:Failed to launch the browser process![108:108:0419/114031.894572:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY[108:108:0419/114031.894782:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.[108:132:0419/114031.896153:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directoryTROUBLESHOOTING: https://pptr.dev/troubleshooting
@qdii
Copy link

qdii commented Jun 1, 2024

In Docker, it looks like the web-check app may not be able talk with Chromium for the following reasons:

  • dbus isn't started
  • chromium may not be able to start if the user is root
  • chromium cannot start if there is no X server running

I think the solution would be to modify the Dockerfile to first start xvfb and dbus.

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

No branches or pull requests

2 participants