Bug 579132

Summary: [abrt] crash in terminator-0.14-3.fc13: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Fabian A. Scherschel <fabsh>
Component: terminatorAssignee: Dominic Hopf <dmaphy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anto.trande, dmaphy, fabsh, steve
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:89639d07f1babe108ad5a7a38f18f77993f30bac
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-05 18:31:08 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 Fabian A. Scherschel 2010-04-02 19:24:56 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/terminator
component: terminator
executable: /usr/bin/python
kernel: 2.6.33.1-19.fc13.i686.PAE
package: terminator-0.14-3.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: No idea what I did.
Comment 1 Fabian A. Scherschel 2010-04-02 19:24:59 UTC 
Created attachment 404230 [details]
File: backtrace
Comment 2 Dominic Hopf 2010-04-05 18:31:08 UTC 
Hi Fabian,
unfortunately the backtrace lacks debugging information. Combined with the fact that you're obviously not able to reproduce the issue, your report unfortunately is not very useful. :(

There will be updates for terminator 0.91 the next days, maybe they will fix your issue. Otherwise I'd be pleased if you get in touch with me in case the issue occurs again and you can reproduce it.

Regards,
Dominic
Comment 3 Fabian A. Scherschel 2010-04-05 19:57:35 UTC 
I have managed to reproduce it now. It basically happens when one tries to divide the window into more than one terminal (horizontally or vertically). Might be related to the latest Metacity problems in F13?

Fab
Comment 4 Dominic Hopf 2010-04-05 22:14:10 UTC 
Would it be possible to get another backtrace then?

I'm still running on F12 and can not reproduce it here. So it's likely, that it is an F13 related issue, yes. Maybe with metacity. I'll try to get an installation of F13 running in a virtual machine next weekend to reproduce it here.

I leave this issue closed anyway as of the update I mentioned above. It already is available in Rawhide and  I like to see if it works fine there before pushing it to F13.
Comment 5 Dominic Hopf 2010-04-21 23:21:59 UTC 

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