Bug 771126

Summary: [abrt] moovida-1.0.9-3.fc14: sem_wait: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Wendell Baker <wendellcraigbaker>
Component: moovidaAssignee: Orphan Owner <extras-orphan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: extras-orphan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9b00931ad97382995fdc94c6d23946aa1aadd436
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:29:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Wendell Baker 2012-01-01 18:44:38 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 105994 bytes
cmdline: /usr/bin/python /usr/bin/elisa
component: moovida
Attached file: coredump, 64557056 bytes
crash_function: sem_wait
executable: /usr/bin/python
kernel: 2.6.35.14-95.fc14.x86_64
package: moovida-1.0.9-3.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1325441907
uid: 500

How to reproduce
-----
1. install it via yum
2. run it
3. see the crash
Comment 1 Wendell Baker 2012-01-01 18:44:41 UTC 
Created attachment 550160 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:29:34 UTC 
Backtrace analysis found this bug to be similar to bug #742048, closing as duplicate.

Bugs which were found to be similar to this bug: 
  awn-extras-applets: bug #758612
  deluge: bug #790903
  glibc: bug #710355
  ipython: bug #754595
  pychess: bug #750102
  quodlibet: bug #802001
  telepathy-sunshine: bug #700195, bug #757325
  virt-manager: bug #742048

This comment is automatically generated.

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