Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 551768 - [abrt] crash detected in pidgin-2.6.4-2.fc12
[abrt] crash detected in pidgin-2.6.4-2.fc12
Product: Fedora
Classification: Fedora
Component: pidgin-gfire (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Andreas Osowski
Fedora Extras Quality Assurance
: 557321 566343 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-01-01 16:36 EST by dillonlaw
Modified: 2010-12-03 19:59 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 19:59:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (11.31 KB, text/plain)
2010-01-01 16:36 EST, dillonlaw
no flags Details

  None (edit)
Description dillonlaw 2010-01-01 16:36:03 EST
abrt 1.0.0 detected a crash.

Comment: Installed Gfire and tried to use it.
Attached file: backtrace
cmdline: /usr/bin/pidgin
component: pidgin
executable: /usr/bin/pidgin
package: pidgin-2.6.4-2.fc12
rating: 3
reason: Process was terminated by signal 6
Comment 1 dillonlaw 2010-01-01 16:36:06 EST
Created attachment 381218 [details]
File: backtrace
Comment 2 Andreas Osowski 2010-01-02 05:33:01 EST
first of all thanks for the report.
Could you maybe be a bit more precise as to what you were doing when the crash occured?

The crash appears to be related to the games list.
Deleting and redownloading it locally, however, does not reproduce the crash.

I shall inform upstream of this bug, but I expect a new release in due time.
Comment 3 Andreas Osowski 2010-01-03 10:47:13 EST
upstream has already fixed this bug in SVN. (http://my-trac.assembla.com/gfire/ticket/12) 

Apparently, as this next release is a full rewrite of the "old" gfire, it'll (still) take ~1-2 months :(
Comment 4 Andreas Osowski 2010-01-21 01:46:54 EST
*** Bug 557321 has been marked as a duplicate of this bug. ***
Comment 5 Andreas Osowski 2010-02-25 15:02:57 EST
*** Bug 566343 has been marked as a duplicate of this bug. ***
Comment 6 Bug Zapper 2010-11-03 22:04:51 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 7 Bug Zapper 2010-12-03 19:59:06 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.