Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 65515 bytes cmdline: python /usr/bin/sugar-activity webactivity.WebActivity -s -b org.laptop.Surf -a e0141dc4ab6108e82ac612891021698989de86f5 component: sugar Attached file: coredump, 2219720704 bytes crash_function: PyArg_ParseTupleAndKeywords executable: /usr/bin/python kernel: 2.6.35.12-90.fc14.x86_64 package: sugar-0.92.1-2.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1304310065 uid: 500 comment ----- The Surf Sugar activity does NOT crash in my 32-bit Fedora 14 VM, or my 64-bit Fedora 15 Beta VM. But it crashes consistantly in my 64-bit Fedora 14 one. All virtual machines are updated to the latest updates as of a few hours ago and the latest updates-testing for sugar related items. How to reproduce ----- 0. Install the sugar-surf RPM if it is not already installed. 1. Start the Surf activity from Sugar, not loading any previous Journal entry so it defaults to the local sugarlabs home page. 2. Click on the Wiki or Bugs link on the home/start page. 3. Surf should crash with an activity log entry like the following: Terminated by signal 11, pid 2231 data (None, <open file '<fdopen>', mode 'w' at 0x22394b0>, 'e0141dc4ab6108e82ac612891021698989de86f5'
Created attachment 496162 [details] File: backtrace
Lucian: Can you possibly have a look at the backtrace and see if anything comes out.
*** Bug 684588 has been marked as a duplicate of this bug. ***
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