Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 586457 - [abrt] crash in sugar-0.88.0-1.fc13: Process /usr/bin/python was killed by signal 6 (SIGABRT)
[abrt] crash in sugar-0.88.0-1.fc13: Process /usr/bin/python was killed by si...
Product: Fedora
Classification: Fedora
Component: sugar (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Simon Schampijer
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2010-04-27 12:26 EDT by Frederick Grose
Modified: 2011-06-27 11:54 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 11:54:35 EDT
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 (72.51 KB, text/plain)
2010-04-27 12:26 EDT, Frederick Grose
no flags Details

  None (edit)
Description Frederick Grose 2010-04-27 12:26:43 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/bin/sugar-session
component: sugar
executable: /usr/bin/python
global_uuid: 97737067857f4b577d714cc3b6b98ee34d73a356
package: sugar-0.88.0-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

1.  Playing in Journal testing keystrokes
2.  Had tabbed around, cursored left and right
3.  search and was prompted with a no results found
4.  Click clear search, then abrt appeared
5.  Haven't been able to repeat the crash
Comment 1 Frederick Grose 2010-04-27 12:26:53 EDT
Created attachment 409514 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-04 21:13:02 EDT
This bug has been triaged

Fedora Bugzappers volunteer triage team
Comment 3 Peter Robinson 2010-06-29 17:59:35 EDT
Can you confirm if the 0.88.1 release has fixed this issue?
Comment 4 Bernie Innocenti 2010-06-29 18:21:17 EDT
(In reply to comment #3)
> Can you confirm if the 0.88.1 release has fixed this issue?    

I doubt 0.88.1 includes any patch that could fix a bug like this.

Looks like Frederick has found this bug:

Comment 5 Bug Zapper 2011-06-02 10:48:36 EDT
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 6 Bug Zapper 2011-06-27 11:54:35 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.