blob: 6a3de7fd7dd57f959ed79933183713c4158886dd (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
graphic: 0.870
x86: 0.842
boot: 0.767
architecture: 0.729
device: 0.728
performance: 0.629
debug: 0.604
i386: 0.570
PID: 0.566
mistranslation: 0.555
semantic: 0.530
ppc: 0.480
permissions: 0.422
user-level: 0.399
register: 0.396
arm: 0.384
files: 0.379
vnc: 0.369
peripherals: 0.366
network: 0.363
risc-v: 0.318
socket: 0.317
TCG: 0.307
hypervisor: 0.300
VMM: 0.282
virtual: 0.234
kernel: 0.233
assembly: 0.197
KVM: 0.130
-display gtk,gl=on crashes on Wayland
steps to reproduce:
1. run a Wayland compositor (I use sway, probably the same bug exists for other compositors)
2. execute qemu -display gtk,gl=on
expected results:
a GTK window is created that shows SeaBIOS failing to boot
actual results:
segmentation fault qemu-system-x86_64 -display gtk,gl=on
additional information:
qemu version 2.12.0 from Arch Linux
looks like qemu is trying to take the Wayland display from GTK and initialize EGL but telling EGL it's a X11 display, which is not correct. setting GDK_BACKEND=x11 works around the issue.
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
|
