Bug 683217 - [abrt] rabbitvcs-core-0.14.1.1-1.fc14: __lll_lock_wait: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] rabbitvcs-core-0.14.1.1-1.fc14: __lll_lock_wait: Process /usr/bin/pyth...
Keywords:
Status: CLOSED DUPLICATE of bug 700742
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitvcs
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Juan Manuel Rodriguez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:af23c679b3d87691cce31152918...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 21:03 UTC by Szőke Károly
Modified: 2012-03-20 16:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:54:01 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (83.51 KB, text/plain)
2011-03-08 21:03 UTC, Szőke Károly 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Szőke Károly 2011-03-08 21:03:40 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 85510 bytes
cmdline: /usr/bin/python /usr/lib/python2.7/site-packages/rabbitvcs/ui/commit.py /home/karcsi/Program/proba/trunk
component: rabbitvcs
Attached file: coredump, 26374144 bytes
crash_function: __lll_lock_wait
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.x86_64
package: rabbitvcs-core-0.14.1.1-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299617929
uid: 500

How to reproduce
-----
1.update
2.crash
3.file keep locked in repo
Comment 1 Szőke Károly 2011-03-08 21:03:43 UTC 
Created attachment 483014 [details]
File: backtrace
Comment 2 Szőke Károly 2011-03-09 18:09:34 UTC 
Package: rabbitvcs-core-0.14.1.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.update
2.crash
3.file keep locked in repo
Comment 3 abrt-bot 2012-03-20 16:54:01 UTC 
Backtrace analysis found this bug to be similar to bug #700742, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 700742 ***
Note You need to log in before you can comment on or make changes to this bug.