Bug 591503 - [abrt] crash in virt-manager-0.8.2-3.fc12: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
[abrt] crash in virt-manager-0.8.2-3.fc12: raise: Process /usr/bin/python was...
Status: CLOSED DUPLICATE of bug 544305
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Cole Robinson
Fedora Extras Quality Assurance
abrt_hash:297b2775a3820a7baa5759309f1...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-12 08:32 EDT by Richard A Lochner
Modified: 2010-05-12 10:01 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-12 10:01:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (42.24 KB, text/plain)
2010-05-12 08:32 EDT, Richard A Lochner
no flags Details

  None (edit)
Description Richard A Lochner 2010-05-12 08:32:01 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py --debug --no-dbus --no-fork --sync -c qemu+tls://vmh001.clone1.com/system
component: virt-manager
crash_function: raise
executable: /usr/bin/python
global_uuid: 297b2775a3820a7baa5759309f1a99303b539a64
kernel: 2.6.32.11-99.fc12.x86_64
package: virt-manager-0.8.2-3.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

comment
-----
When opening a window to a VM with virt-manager, it aborts with the following error:
python: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.

Usually, the window will open for a few seconds before the crash occurs.

The log file ends with the following:

2010-05-12 07:24:11,946 (console:562): Graphics console configured at vnc://vmh001.clone1.com:5900
2010-05-12 07:24:11,948 (console:575): Starting connect process for vmh001.clone1.com 5900
2010-05-12 07:24:11,983 (engine:414): window counter incremented to 2
2010-05-12 07:24:11,988 (console:562): Graphics console configured at vnc://vmh001.clone1.com:5900
2010-05-12 07:24:11,990 (console:575): Starting connect process for vmh001.clone1.com 5900
2010-05-12 07:24:12,721 (console:626): Got credential request <enum VNC_DISPLAY_CREDENTIAL_CLIENTNAME of type VncDisplayCredential>
2010-05-12 07:24:12,836 (console:464): VNC initialized
python: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.

How to reproduce
-----
I ran virt-manager as follows:
virt-manager --debug --no-dbus --no-fork --sync -c qemu+tls://vmh001.clone1.com/system 2>virt-manager.log
Comment 1 Richard A Lochner 2010-05-12 08:32:03 EDT
Created attachment 413415 [details]
File: backtrace
Comment 2 Daniel Berrange 2010-05-12 09:57:22 EDT
Please provide the precise gtk-vnc and libvirt  RPM versions installed. Looks like a libvirt bug to me though.
Comment 3 Cole Robinson 2010-05-12 10:01:05 EDT
There's a nearly identical bug against libvirt, so just duping to that.

*** This bug has been marked as a duplicate of bug 544305 ***

Note You need to log in before you can comment on or make changes to this bug.