abrt version: 1.1.18
Attached file: backtrace, 83233 bytes
cmdline: python /usr/bin/sugar-activity TurtleArtActivity.TurtleArtActivity -b org.laptop.TurtleArtActivity -a f4fff6836757edc11ed59dd8457c236cddafb3ea
comment: sorry i couldnt write down the little error mesage
Attached file: coredump, 51834880 bytes
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1.i was trying to use sound jucer to read a audio cd when i got a dbus error somthing about a peer to peer conection to 1. somthing and i needed to finish extracting the audio, i couldnt find the pi of the problem so i killed gnome session with the SIGABRT signal
Created attachment 519188 [details]
OS Release: Fedora release 15 (Lovelock)
Downloaded Turtle Blocks 113.
Clicked .xo bundle in Journal to test installation in case of existing version 114.
Crashed back to Journal.
There is Turtle Blocks Activity instance that started up but crashed after a few seconds.
Does the 114 version in fedora-updates work?
(In reply to comment #4)
> Does the 114 version in fedora-updates work?
Yes, it launches and appears fine in Sugar in a Window.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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: