Hide Forgot
Description of problem: 1. Installed python-abiword.x86_64 1:3.0.0-4.fc19, updated libabiword.x86_64 1:3.0.0-4.fc19, sugar-write.noarch 0:94-1.fc19 2. Opened Sugar 0.98.8 in a Xephyr window in Fedora 19 3. Launched the Write activity (did not enter any text) 4. Launched the Log activity 5. Toggled the Frame and switched to the Sugar Journal (noticed the Write icon disappear from the Frame 6. Relaunched Write, repeated #5 with same effect. 7. Relaunched Write, repeated #5 (no loss of Write icon) 8. Switched to Write and clicked Stop button. Busy cursor for a long time. 9. Write never closed. Closed Log. 10. Tryed to logout of Sugar from Home screen (not effective) 11. Closed the Xephyr window with its Close button. Version-Release number of selected component: sugar-toolkit-gtk3-0.98.7-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: python /usr/bin/sugar-activity AbiWordActivity.AbiWordActivity -b org.laptop.AbiWordActivity -a 8e9fe08313d00d174840c6e60704c478644fa45a crash_function: _pygi_marshal_cleanup_to_py_array executable: /usr/bin/python2.7 kernel: 3.11.8-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Nov 23 18:26:49 dell abrt-hook-ccpp[8098]: Saved core dump of pid 8077 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-11-23-18:26:46-8077 (69775360 bytes) Truncated backtrace: Thread no. 1 (10 frames) #6 _pygi_marshal_cleanup_to_py_array at pygi-marshal-cleanup.c:438 #7 pygi_marshal_cleanup_args_to_py_marshal_success at pygi-marshal-cleanup.c:122 #8 pygi_callable_info_invoke at pygi-invoke.c:669 #9 ext_do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4408 #10 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2779 #11 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:3330 #12 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4194 #13 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4119 #14 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2740 #15 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4184
Created attachment 828211 [details] File: backtrace
Created attachment 828212 [details] File: cgroup
Created attachment 828213 [details] File: core_backtrace
Created attachment 828214 [details] File: dso_list
Created attachment 828215 [details] File: environ
Created attachment 828216 [details] File: limits
Created attachment 828217 [details] File: maps
Created attachment 828218 [details] File: open_fds
Created attachment 828219 [details] File: proc_pid_status
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.