Hello,
I am a Debian newbie and I participated in a Bug Squashing Party recently.

I was running arch on my machine, hence I tried reproducing the bug in a
clean QEMU debian image, but matching all the versions getting the exact
packages for each, I was unable to reproduce the bug on my virtual machine.

So maybe it is due to my environment, or maybe the bug is caused by
something else in the environment of the original reporter.

But again I am a newbie, I was running Debian through QEMU so this might or
might not be valuable info.

more info on my env:
- arch on KDE
- the local unstable Debian we had on hand via QEMU/SPICE
- laptop is HP probook 450 G10 with intel i5-1334U
(company provided, if it was mine it would have been a framework or
thinkpad)

it could be, either the IGPU vs dedicated GPU or the QEMU / SPICE
rendering, or none.
But hopefully this will give a useful data point for future investigation.

Best regards.

Reply via email to