Closed khallebal closed 1 year ago
It has nothing to do with Xlibe, sorry for the noise.
Can't close this thing?
It likely does have to do with Xlibe. QEMU probably expects to be able to get a full keymap, which Xlibe doesn't provide, and it doesn't expect this to fail (which is reasonable, Xlibe isn't really "within specifications" in doing this.) Whether we can or should do something about it is another matter.
Ah okay i didn't know that, but still that doesn't explain the crash at start up, it should just go through the checks and then issue the warning at the end of the gd_get_keymap() function and return NULL, why does it [crash?.] I wonder how @X547 dealt with this keymap issue in wayland?
Wayland uses real keymaps. Since GTK now uses the Wayland layer instead of Xlibe, I think we can close this.
No problem, you have more important things to do.
From what i have understood of the trace is that qemu searchs for a (X)server X11;quartz,win32 or broadway and doesn't find any? is this a good assumption? Anyway the trace report is include.