On 02/08/2018, 08:32 PM, Thomas Huth wrote:
> Triaging old bug tickets... can you still reproduce this issue with the
> latest version of QEMU? Or could we close this ticket nowadays?
The issue is long gone, feel free to close.
--
js
--
You received this bug notification because you are a mem
That works for scale = 1. Given scale is set only in draw (2d) and not
in render (3d), it never worked with other scales. Apart from that, the
code is full of bugs.
I could make it work with the attached diff modulo the fprintfs,
basically. However I am not going to invest more time into that, as
Ok, should we use
gtk_widget_get_allocated_height and gtk_widget_get_allocated_width
instead of
gdk_drawable_get_size
?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1592351
Title:
mouse point
s->menu_bar's height is really 26px (506-480)
both s->notebook's and vc->tab_item's height is 506 px (the same as
vc->gfx.drawing_area).
I cannot figure out why...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchp
This is because height from gdk_drawable_get_size() in gd_motion_event()
includes menu or whatever:
gl=off:
gd_motion_event: fbw= 640 fbh= 480 ww= 640 wh= 480 mx= 0 my= 0 x= 576 y= 3
gl=on:
gd_motion_event: fbw= 640 fbh= 480 ww= 640 wh= 506 mx= 0 my= 13 x= 571 y= 471
--
You received this
The same happens with qemu from git, commit
a28aae041aa76a779df6467a7fe68b9e8a8b2c0a.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1592351
Title:
mouse pointer offset with gtk,gl=on
Status in QEM
Public bug reported:
When I turn gl=on for -display gtk, some Y offset is added to the mouse
pointer coordinates. That is, when I click on an icon, an icon _above_
the one I clicked triggers.
Using xev, it seems to be offset of 10-12 pixels.
It happens with all ps/2 mouse, -usbdevice mouse and -
Public bug reported:
I run qemu as follows:
qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -m 2371 -usb \
-device virtio-rng-pci \
-drive file=/home/new/suse-fact.img,format=raw,discard=unmap,if=none,id=hd
-device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd \
-soundhw hda \
-
2.1 is OK with vte 2.90, not with 2.91
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1379688
Title:
qemu's monitor and parallel create huge window
Status in QEMU:
New
Bug description:
I have
1.6.0 is good at least.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1379688
Title:
qemu's monitor and parallel create huge window
Status in QEMU:
New
Bug description:
I have qemu 2.1. When
Public bug reported:
I have qemu 2.1. When I try to switch to monitor or parallel0, I get
window which is 30 *thousand* pixels in height. It is only gray with no
content. This did not happen with previous versions of qemu.
Kwin crashes because it cannot handle such a huge window.
** Affects: qem
11 matches
Mail list logo
