blob: 2d5b0c8b44cdf6aa2ca14cc54cc559ac0b8bb26b (
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
55
|
debug: 0.974
graphic: 0.950
device: 0.820
ppc: 0.817
semantic: 0.729
user-level: 0.717
vnc: 0.711
performance: 0.709
architecture: 0.662
peripherals: 0.595
socket: 0.538
files: 0.534
boot: 0.533
permissions: 0.532
x86: 0.519
register: 0.501
i386: 0.495
PID: 0.489
arm: 0.479
TCG: 0.474
risc-v: 0.462
kernel: 0.455
hypervisor: 0.454
network: 0.399
VMM: 0.395
assembly: 0.294
mistranslation: 0.292
KVM: 0.183
virtual: 0.182
QEMU locks out user interface after waking from laptop sleep
Description of problem:
If qemu is started on laptop from command line and set to full screen, screen activated with mouse click, then put to sleep by closing lid; after waking up by opening lid the user interface locks out, the mouse cursor doesn't show, mouse clicks and keys are unresponsive.
A Ctrl-ALt-Fn terminal must then be used to locate and kill the qemu process. After which the system can recover if it is terminated. The system tends to be affected in other ways such as wifi being disabled and needs to manually enabled after. So it looks like it disrupts the system from fully restoring the awoken state.
The terminal from which QEMU is running is also filled with debug output. The issue looks to be caused by the SDL backend not knowing what to do with a wake up code. The terminal window is filled with the following text:
`The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL forums/mailing list <https://discourse.libsdl.org/> X11 KeyCode 151 (143), X11 KeySym 0x1008FF2B (XF86WakeUp).`
I have reduced the steps causing the bug to as little as needed with low dependencies.
Steps to reproduce:
1. Using a laptop, start a qemu session in full screen like so:
`./qemu-system-ppc -machine mac99,via=pmu -serial stdio -full-screen`
2. Shut the lid so it sleeps.
3. Shortly after open the lid.
Additional information:
I downloaded the 6.1.0 stable build and compiled it myself.
The SDL issue appears to be low priority. I found some reports here but see no evidence of it being discussed.
https://discourse.libsdl.org/t/key-not-recognised-by-sdl/24181
|