Bug 605347

Summary: [abrt] crash in tortoisehg-1.0.4-1.fc13: _IO_default_xsputn: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Neal Becker <ndbecker2>
Component: tortoisehgAssignee: Mads Kiilerich <mads>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mads
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:288690f1de253d8d78dead9e4c4f55ac32a9ca54
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-17 20:54:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Neal Becker 2010-06-17 17:08:39 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/hgtk merge
component: tortoisehg
crash_function: _IO_default_xsputn
executable: /usr/bin/python
global_uuid: 288690f1de253d8d78dead9e4c4f55ac32a9ca54
kernel: 2.6.33.5-124.fc13.x86_64
package: tortoisehg-1.0.4-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. hgtk merge (with no args or options)
2.
3.
Comment 1 Neal Becker 2010-06-17 17:08:41 UTC 
Created attachment 424884 [details]
File: backtrace
Comment 2 Mads Kiilerich 2010-06-17 20:47:43 UTC 
That looks like a segmentation fault while trying to handle an assertion in pygobject.

More specific instructions for reproducing (on x86):

In hg repo with single head run "hgtk merge".
"Unable to merge" messagebox, choose Close.
See "Merging in hg" window with 4 grey buttons, but after few seconds it dumps core.
Comment 3 Mads Kiilerich 2010-06-17 20:54:15 UTC 

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