Bug 714246 - [abrt] wxGlade-0.6.3tip20100625-1.fc13: GetStaticBoxBorders: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] wxGlade-0.6.3tip20100625-1.fc13: GetStaticBoxBorders: Process /usr/bin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: wxGlade
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miao ZhiCheng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5fe38099dff80f3bc6db5052496...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-17 17:15 UTC by Bruce vaNorman
Modified: 2011-06-27 11:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:40:18 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (27.09 KB, text/plain)
2011-06-17 17:15 UTC, Bruce vaNorman
no flags Details

Description Bruce vaNorman 2011-06-17 17:15:29 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: python /usr/share/wxGlade/wxglade.py /home/bvn/my/python/ipc/ipc_test/ipc_test_service.wxg
component: wxGlade
crash_function: GetStaticBoxBorders
executable: /usr/bin/python
kernel: 2.6.34.8-68.fc13.i686.PAE
package: wxGlade-0.6.3tip20100625-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1308330364
uid: 500

How to reproduce
-----
1. I was trying to delete a moderatly complicated frame (of 2)
2.
3.

Comment 1 Bruce vaNorman 2011-06-17 17:15:32 UTC
Created attachment 505317 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-27 11:40:18 UTC
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.