Bug 525544 - [abrt] crash detected in geany-0.18-6.fc12
Summary: [abrt] crash detected in geany-0.18-6.fc12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: geany
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9aa03dabc4b9e800e2ebf8d322c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-24 18:52 UTC by al morris
Modified: 2010-03-15 21:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-15 21:00:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (3.86 KB, text/plain)
2009-09-24 18:52 UTC, al morris 		no flags Details
View All

Description al morris 2009-09-24 18:52:02 UTC 
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Comment
-----
issued reset command using terminal tab of geany (preferences >tools>Terminal>Terminal --disable-server)

Additional information
======


Attached files
----
backtrace

cmdline
-----
geany 


component
-----
geany


executable
-----
/usr/bin/geany


kernel
-----
2.6.31-33.fc12.x86_64


package
-----
geany-0.18-6.fc12


reason
-----
Process was terminated by signal 6
Comment 1 al morris 2009-09-24 18:52:05 UTC 
Created attachment 362556 [details]
File: backtrace
Comment 2 Dominic Hopf 2009-09-27 08:22:29 UTC 
Hi,
is it possible to describe a way how to reproduce this issue?
Which version of vte are you using? If it is not yet vte-0.22.1-2.fc12 could you try to update it and see if it might fixes this issue? (Maybe get if from koji). Most likely this is an vte issue which should have got fixed with 0.22.1.
Comment 3 Bug Zapper 2009-11-16 12:52:17 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Dominic Hopf 2010-03-15 21:00:05 UTC 
This issue got fixed with an vte update some weeks ago.
Note You need to log in before you can comment on or make changes to this bug.