Bug 571165 - [abrt] crash in terminator-0.13-3.fc12: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in terminator-0.13-3.fc12: Process /usr/bin/python was killed by...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: terminator
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:82f7a37fb92c8514e602942b5a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-07 11:21 UTC by Justin O'Brien
Modified: 2010-04-22 19:17 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-21 23:26:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (55.11 KB, text/plain)
2010-03-07 11:21 UTC, Justin O'Brien 		no flags Details
View All

Description Justin O'Brien 2010-03-07 11:21:29 UTC 
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/terminator
comment: ssh'd into my server, opened dvtm, opened irssi
component: terminator
executable: /usr/bin/python
kernel: 2.6.32.9-67.fc12.i686
package: terminator-0.13-3.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. ssh into another box
2. leave open all day
3. report bug when ABRT pops up
Comment 1 Justin O'Brien 2010-03-07 11:21:32 UTC 
Created attachment 398316 [details]
File: backtrace
Comment 2 Dominic Hopf 2010-03-07 20:55:30 UTC 
Would it be possible to try reproducing this issue with terminator 0.14?
It already is available in updates-testing repository. You can update it with 'yum update terminator --enablerepo=updates-testing'.
Comment 3 Justin O'Brien 2010-04-22 19:06:38 UTC 
I'll give it a try
Comment 4 Justin O'Brien 2010-04-22 19:17:20 UTC 
Tried to update but it said there are no packages marked for upgrade so I must have had it for a while, I don't think I've had this issue for a while.

I think its safe to close this bug :)

Thanks for your hard work
Note You need to log in before you can comment on or make changes to this bug.