diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/108/boot/1906181 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/108/boot/1906181')
| -rw-r--r-- | results/classifier/108/boot/1906181 | 61 |
1 files changed, 0 insertions, 61 deletions
diff --git a/results/classifier/108/boot/1906181 b/results/classifier/108/boot/1906181 deleted file mode 100644 index 7f057239..00000000 --- a/results/classifier/108/boot/1906181 +++ /dev/null @@ -1,61 +0,0 @@ -boot: 0.933 -graphic: 0.914 -other: 0.882 -performance: 0.757 -device: 0.747 -KVM: 0.667 -permissions: 0.636 -files: 0.629 -PID: 0.626 -semantic: 0.611 -vnc: 0.548 -network: 0.525 -debug: 0.462 -socket: 0.397 - -Mouse starts jumping wildly on guest desktop - -Sometimes mouse goes completely crazy and starts jumping around the guest desktop by itself and becomes completely unusable. - -This does not happen on every boot, only sometimes. It may be caused by some input combination but I haven't yet found any specific cause. It happens soon after the desktop has been loaded and rebooting seems to be the only way to resolve the situation. - - -Guest: Kubuntu 20.04 64-bit (live), with KDE desktop -Host: Arch Linux, with KDE desktop -QEMU version: 5.1.0 - -QEMU start command: -qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga virtio -soundhw hda -display sdl,gl=on - -The QEMU project is currently moving 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 the bug state to "Incomplete" now. - -If the bug has already been fixed in the latest upstream version of QEMU, -then please close this ticket as "Fix released". - -If it is not fixed yet and you think that this bug report here is still -valid, then you have two options: - -1) If you already have an account on gitlab.com, please open a new ticket -for this problem in our new tracker here: - - https://gitlab.com/qemu-project/qemu/-/issues - -and then close this ticket here on Launchpad (or let it expire auto- -matically after 60 days). Please mention the URL of this bug ticket on -Launchpad in the new ticket on GitLab. - -2) If you don't have an account on gitlab.com and don't intend to get -one, but still would like to keep this ticket opened, then please switch -the state back to "New" or "Confirmed" within the next 60 days (other- -wise it will get closed as "Expired"). We will then eventually migrate -the ticket automatically to the new system (but you won't be the reporter -of the bug in the new system and thus you won't get notified on changes -anymore). - -Thank you and sorry for the inconvenience. - - -[Expired for QEMU because there has been no activity for 60 days.] - |
