Bug 580603 - [abrt] crash in terminator-0.14-3.fc13: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in terminator-0.14-3.fc13: Process /usr/bin/python was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 579851
Alias: None
Product: Fedora
Classification: Fedora
Component: terminator
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:41d9bfaadaca1e41009a00951fa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 15:43 UTC by James Laska
Modified: 2013-09-02 06:47 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-08 16:09:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (77.96 KB, text/plain)
2010-04-08 15:43 UTC, James Laska 		no flags Details
View All

Description James Laska 2010-04-08 15:43:03 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/terminator
component: terminator
executable: /usr/bin/python
global_uuid: 41d9bfaadaca1e41009a00951fae3881a1fec555
kernel: 2.6.33.1-19.fc13.x86_64
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
-----
1. Start terminator in F-13
2. Maximize the window
3. Right-click, and split horizontally
Comment 1 James Laska 2010-04-08 15:43:05 UTC 
Created attachment 405337 [details]
File: backtrace
Comment 2 Eric Lake 2010-04-08 16:09:06 UTC 
Thank you for taking the time to submit this bug report.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Eric Lake 2010-04-08 16:09:34 UTC 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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