Since there wasn't a reply to my question since more than half a year,
I'm assuming that this does not affect upstream QEMU anymore. Thus I'm
removing upstream QEMU from this ticket now.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is there still an issue left here for upstream QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't capture keys
** Changed in: xserver
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't capture keys properly under wayland
To manage notifications about this
upstream can't reproduce this bug, so I wonder if the backport was
incomplete and it's fixed in the current release (1.20.8), could you
test again?
** Changed in: xserver
Importance: Medium => Unknown
** Changed in: xserver
Remote watch: freedesktop.org Bugzilla #102475 =>
Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=102475.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu
Actually, this bug would affect current 1.19-branch too since the
patches are backported there as well. You can test
ppa:canonical-x/x-staging to verify, which has xorg-server from current
stable branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
is the patch providing any user visible improvement? if not it would
probably make sense to delay including it to next cycle
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't
Now the question is should the patch be dropped or wait for a fix from
upstream. I'm leaning towards the first option, since artful is about to
be released.
** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Triaged
** Changed
** Changed in: xserver
Status: Unknown => Incomplete
** Changed in: xserver
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't capture
Upstream bug is probably
https://bugs.freedesktop.org/show_bug.cgi?id=102475 ?
** Bug watch added: freedesktop.org Bugzilla #102475
https://bugs.freedesktop.org/show_bug.cgi?id=102475
** Also affects: xserver via
https://bugs.freedesktop.org/show_bug.cgi?id=102475
Importance: Unknown
So it is likely a wayland <-> SDL thing.
@Desktop Team could you take alook into this - the repro steps in c#2 are
pretty easy I'd think but none of us would know where in the UI stack to look
for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi! I am running Artful on my X1 Carbon Gen3.
I downloaded the Ubuntu Server Artful final beta and attempt to do an
install with the following qemu cli:
$ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d -hda
vdisk.img -cdrom artful-server-amd64.iso -monitor stdio
Trying to use the
I wanted to write steps to reproduce, which should be as simple as:
$ wget http://cdimage.ubuntu.com/daily-live/current/artful-desktop-amd64.iso
$ qemu-system-x86_64 -m 512 -boot d -cdrom artful-desktop-amd64.iso
But that works for me as seen in the attached video.
@Mathieu - can you elaborate
Hi Mathieu,
thanks for the report but since we are up-to-date with qemu and I can't find an
obvious breakage we might have introduced for this, this should go to
qmeu-upstream in this case.
Furthermore are these actually two issues?:
#1 - wayland crashes under spice
more of a wayland bug
15 matches
Mail list logo
