[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault wi
QEMU 0.10 is pretty much outdated nowadays... can you reproduce this
issue with the latest version of QEMU, and if so, provide a backtrace of
the crash?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Hi,
Xen Orchestra project leader here. Exactly the same problem with noVNC +
qemu-dm.
I assume there is maybe an invalid param from noVNC somewhere, but
crashing the process is not really expected.
The bug is also reported at Citrix (see
https://bugs.xenserver.org/browse/XSO-381)
I don't know h
Dubravko: can you get a good backtrace from your crash?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
Bug description:
Hey,
No, sorry. I've stopped researching this issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
Bug description:
Hey,
I'm u
Hi,
Did you resolve your problem? Because I have the same issus..
Dubravko
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
Bug
Can you attach GDB to your qemu-dm process and attempt to capture a full
stack trace when it crashes (ie thread apply all backtrace)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Seg
