mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-11 21:10:25 +01:00
gtk initialization failed (Possibly ALSA Related) #607
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tokenwizard on GitHub (Jul 31, 2024).
Requested info is logged below. Also, I put the console output that seemed relevant (ALSA errors just before the system exists with the gtk initialization error).
Is ALSA a prerequisite for this to work? Is there something else I'm missing?
I regularly run other docker containers on this system.
OS related issued, please help us identify the issue by posting the output of this
uname -a \
Linux OfficePC 6.9.9-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri Jul 12 10:32:52 UTC 2024 x86_64 GNU/Linux; echo "${DISPLAY}" \
:0.0; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs \
1; grep NAME /etc/os-release \
; df -h . \
; qemu-system-x86_64 --version \
; libvirtd --version
libvirtd (libvirt) 10.5.0; free -mh \
; nproc
16; egrep -c '(svm|vmx)' /proc/cpuinfo \
; ls -lha /dev/kvm
crw-rw-rw- 1 root kvm 10, 232 Jul 31 11:15 /dev/kvm; ls -lha /tmp/.X11-unix/ \
; ps aux | grep dockerd \
; docker ps | grep osx
(NULL)
; grep "docker|kvm|virt" /etc/group
Seemingly-relevant log output:
@tokenwizard commented on GitHub (Jul 31, 2024):
I tried updating my run command to use PulseAudio by adding these lines:
and now it no longer shows the ALSA-related errors, but still exits, whether run with sudo or not.
@cjdb commented on GitHub (Aug 11, 2024):
I was able to get around this by following the steps in https://github.com/sickcodes/Docker-OSX/issues/7#issuecomment-639356240 on my host.
@qianxilihulu commented on GitHub (Aug 19, 2024):
ALSA is not related and happens to everyone, according to README. The real error is the last line, "gtk initialization failed," which is most likely about how you set up your display. Please provide your docker command for further troubleshoot. you should also check if you're using wayland or X.
There're many issues about X already. i'm using Wayland, and one important thing is /run/user/{UID} has been given enough permission.
@DIGist commented on GitHub (Mar 31, 2025):
Getting a similiar pulseaudio error, but not connecting. Running Bazzite (Fedora Silverblue) with podman.
osx.log
@sojab0on commented on GitHub (Jun 26, 2025):
i get exactly the same pulse errors