summary refs log tree commit diff stats
path: root/results/classifier/108/graphic/2674
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/graphic/2674')
-rw-r--r--results/classifier/108/graphic/267439
1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/108/graphic/2674 b/results/classifier/108/graphic/2674
new file mode 100644
index 000000000..ee41a3486
--- /dev/null
+++ b/results/classifier/108/graphic/2674
@@ -0,0 +1,39 @@
+graphic: 0.984
+boot: 0.874
+device: 0.782
+other: 0.684
+semantic: 0.681
+socket: 0.616
+performance: 0.612
+permissions: 0.525
+vnc: 0.469
+PID: 0.467
+debug: 0.452
+files: 0.447
+network: 0.186
+KVM: 0.104
+
+NextSTEP 3.3 for Sparc graphical glitches
+Description of problem:
+It installs/boot by using complex boot syntax and taskset -c 0 under Linux
+
+see end of https://gitlab.com/qemu-project/qemu/-/issues/2620#note_2207999780
+
+But after it installs I see  some gfx corruption
+Steps to reproduce:
+1. install NEXTSTEP 3.3 for RISC computers
+2. Boot to desktop (may need ctrl-c  to skip some services at startup)
+3. Select Info and watch for Workspace Manager info window to appear.
+4. Move this window to the right - it corrupts!
+Additional information:
+Bug also exist if I boot qemu with  -g 1024x768x24
+
+Moving window vertically (up/down) does not corrupt it
+Moving any window around corrupt it.
+
+Resizing and scrolling inside say Terminal emulators work.
+
+There was 86Box issue around one FPU instruction that looked a bit like this, 
+is there way to check fpu emulation?
+
+![ns33-qemu-903-corruption](/uploads/5230c7263bbc44acc37c4736f1d306ff/ns33-qemu-903-corruption.png)