*** This bug is a duplicate of bug 1845198 ***
https://bugs.launchpad.net/bugs/1845198
I have the exact same stack trace on multiple virtual machines running
fully updated release version of 19.10.
ApportVersion: 2.20.11-0ubuntu8.1
Maybe not a duplicate if the other fix didn't resolve it?
*** This bug is a duplicate of bug 1845198 ***
https://bugs.launchpad.net/bugs/1845198
@Christian - by flavours I mean Budgie, Lubuntu, Xubuntu and Kubuntu.
I've installed all of them and had no issues of this kind.
I've also had no further issues with Ubuntu (Gnome) since my last
comment a
@jane glad that spice-vdagent resolved one of your issued.
@Rafel - thanks for checking that stack trace.
The channel should (tm) be either up as early as the guest starts or never
(undefined). It would be interesting if this really was starting qemu-ga before
it was fully initialized.
@Jane
Forget the last paragraph of the previous comment. Bug 1845198 seems
more likely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845827
Title:
qemu-ga crashed with SIGABRT in raise()
To manage
Today's update to spice-vdagent means that the mouse pointer will move
smoothly in and out of the VM - no need for manual release.
I think that the crash may be related to not having libguestfs channel
installed/active, but I'd need to do some further tests to be sure.
--
You received this bug
Looks like there was an issue during GAState channel initialization...
as the channel was used (by run_agent() ?) before it was fully
initialized (by initialize_agent()), so the assert:
static int send_response(GAState *s, const QDict *rsp)
{
const char *buf;
QString *payload_qstr,
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845827
Title:
qemu-ga crashed with SIGABRT in raise()
To manage notifications about this bug go
