Bug 711701 - [abrt] yumex-3.0.3-1.fc14: PyEval_EvalCodeEx: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] yumex-3.0.3-1.fc14: PyEval_EvalCodeEx: Process /usr/bin/python was kil...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:07d6df7d5fb85f5f301041513e9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 08:29 UTC by edo
Modified: 2012-05-09 10:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-09 10:18:29 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (83.12 KB, text/plain)
2011-06-08 08:29 UTC, edo
no flags Details

Description edo 2011-06-08 08:29:09 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 85111 bytes
cmdline: /usr/bin/python /usr/share/yumex/yumex.pyc
component: yumex
Attached file: coredump, 22065152 bytes
crash_function: PyEval_EvalCodeEx
executable: /usr/bin/python
kernel: 2.6.35.13-92.fc14.x86_64
package: yumex-3.0.3-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307462775
uid: 500

How to reproduce
-----
1.start PC and Gnome session
2.crash annoucement
3.

Comment 1 edo 2011-06-08 08:29:12 UTC
Created attachment 503642 [details]
File: backtrace

Comment 2 Tim Lauridsen 2011-06-08 09:16:54 UTC
Can you reproduce this every time you start yumex ?


Note You need to log in before you can comment on or make changes to this bug.