Description of problem: I didn't do anything. libvirtd appeared to crash after I logged in. Version-Release number of selected component: libvirt-daemon-0.10.2.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/sbin/libvirtd --timeout=30 crash_function: virDomainDefFree executable: /usr/sbin/libvirtd kernel: 3.6.9-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 virDomainDefFree at conf/domain_conf.c:1626 #1 virDomainObjDispose at conf/domain_conf.c:1737 #2 virObjectUnref at util/virobject.c:139 #3 qemuDomainObjEndJob at qemu/qemu_domain.c:943 #4 qemuDomainDestroyFlags at qemu/qemu_driver.c:1996 #5 virDomainDestroyFlags at libvirt.c:2264 #6 remoteDispatchDomainDestroyFlags at remote_dispatch.h:1329 #7 remoteDispatchDomainDestroyFlagsHelper at remote_dispatch.h:1307 #8 virNetServerProgramDispatchCall at rpc/virnetserverprogram.c:431 #9 virNetServerProgramDispatch at rpc/virnetserverprogram.c:304
Created attachment 685266 [details] File: backtrace
Created attachment 685267 [details] File: build_ids
Created attachment 685268 [details] File: cgroup
Created attachment 685269 [details] File: core_backtrace
Created attachment 685270 [details] File: dso_list
Created attachment 685271 [details] File: environ
Created attachment 685272 [details] File: limits
Created attachment 685273 [details] File: maps
Created attachment 685274 [details] File: open_fds
Created attachment 685275 [details] File: proc_pid_status
Created attachment 685276 [details] File: var_log_messages
Since ABRT just popped up immediately after I logged in, and I wasn't using libvirt at all, I suspect this bug is just something that ABRT pulled out of its guts at random and decided to submit.
I'm just gonna assume this is related to the destroy() race since the backtrace is close. *** This bug has been marked as a duplicate of bug 877110 ***