I was doing some routine maintance tasks such as using apt-get to upgrade the system's packages when virt-manager just stopped responding and it had to be forced to quit. However as the process with the VM kept running, after restarting virt-manager I was able to continue without any data loss which I noticed.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: virt-manager 1:1.3.2-3ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 19 19:54:55 2016
ExecutablePath: /usr/share/virt-manager/virt-manager
InstallationDate: Installed on 2016-05-15 (221 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 5
SourcePackage: virt-manager
StacktraceTop:
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_variant () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
__GI___libc_free (mem=<optimised out>) at malloc.c:2982
?? () from /lib/x86_64-linux-gnu/libpthread.so.0
?? () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: virt-manager crashed with signal 5 in g_log_default_handler()
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
StacktraceTop:
g_log_
g_log_variant () from /tmp/apport_
__GI___libc_free (mem=<optimized out>) at malloc.c:2982
?? () from /tmp/apport_
?? () from /tmp/apport_