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

gtk initialization failed #862

Open
ademirtug opened this issue Feb 13, 2025 · 1 comment
Open

gtk initialization failed #862

ademirtug opened this issue Feb 13, 2025 · 1 comment

Comments

@ademirtug
Copy link

I'm encountering the error "GTK initialization failed" when running the following command from the Windows Terminal:

docker run -it --device /dev/kvm -p 50921:10022 -v /mnt/wslg/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e RAM=8 -e EXTRA='-smp 8,sockets=4,cores=2' -e GENERATE_UNIQUE=true -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' -e SHORTNAME=sonoma sickcodes/docker-osx:latest

However, if I first launch WSL (wsl) and then run the same command inside the WSL environment, everything works fine.

Is this the intended behavior?

@ipaqmaster
Copy link

Experienced the same for SHORTNAME=ventura and SHORTNAME=sonoma.

Ran xhost + and it worked.

Relevant log lines:

Authorization required, but no authorization protocol specified
gtk initialization failed

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