Bug 696855

Summary: [abrt] sugar-0.90.3-4.fc14: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Samuel Greenfeld <samuel>
Component: sugarAssignee: Simon Schampijer <simon>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bernie+fedora, johnp, pbrobinson, sebastian, simon, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b2a406a3b209743c25029877a7587fe4fe1dfd9c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:48:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Activity log for the Maze activity none

Description Samuel Greenfeld 2011-04-15 02:15:20 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 78293 bytes
cmdline: python /usr/bin/sugar-activity activity.MazeActivity -b vu.lux.olpc.Maze -a c7b035edee85a4ccc3c3a7da9aa93c96d0c3970f
comment: OLPC F14-derived builds for XO laptops have had similar {potentially} GTK crashes within sugar activities lately, not always at the point they are closed, and not always reliably.  I would not be aware of the technical details.
component: sugar
Attached file: coredump, 71151616 bytes
executable: /usr/bin/python
kernel: 2.6.35.12-88.fc14.x86_64
package: sugar-0.90.3-4.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302832995
uid: 500

How to reproduce
-----
0. Group install "sugar-desktop" along with the sugar packages in updates-testing as of this bug's date/time.  Install "sugar-emulator" as well as "sugar-maze" from updates-testing.

1. Start the "Sugar" (sugar-emulator RPM) entry from the Education menu in GNOME.
2. Start the Maze activity (sugar-maze RPM) from Sugar's main menu.  You may have to go into the "List" view to see it.
2b. Note that on my {virtual} F14 64-bit system Maze completely seems to misjudge the size of the available drawing area, drawing an overly large maze which exceeds the Sugar-emulator/"Sugar in a Window" drawable area.
3. Press the "Stop" button (the hexgon with the Square in the middle of it) to stop the activity.
4. You will be returned to the Sugar menu normally but ABRT catches the crash.

Comment 1 Samuel Greenfeld 2011-04-15 02:15:23 UTC
Created attachment 492261 [details]
File: backtrace

Comment 2 Samuel Greenfeld 2011-04-15 02:23:26 UTC
Created attachment 492262 [details]
Activity log for the Maze activity

Activity log for the Maze activity from Sugar's log directory.

The Maze activity has since crashed the second and third time I started it and attempted to exit, all with nearly identical activity logs except for the instance and process IDs used.

Other activities tried (Terminal, Pippy, Calculate, etc.) have not crashed while running or exiting while attempting

Comment 3 Samuel Greenfeld 2011-04-15 02:43:59 UTC
The same behavior happens when Sugar is chosen as the main Window manager from the gdm login screen, so the crash is not sugar-emulator specific.

It looks from the generated mazes like Maze may be presuming it has an XO-size screen instead of the 1024x768 display allocated or the even smaller area made available by the default sugar-emulator shortcut.

Comment 4 Fedora End Of Life 2012-08-16 15:48:07 UTC
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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping