Bug 546748 - yumex - History Enabled - Segmentation fault -
Summary: yumex - History Enabled - Segmentation fault -
Keywords:
Status: CLOSED DUPLICATE of bug 548849
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-11 20:53 UTC by Flóki Pálsson
Modified: 2009-12-22 08:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-22 08:58:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
yumex core dump log (9.31 KB, text/plain)
2009-12-21 21:01 UTC, Electron
no flags Details

Description Flóki Pálsson 2009-12-11 20:53:17 UTC
Description of problem:
Starting yumex from terminal ( and menu ) then yumex ends with "Segmentation fault".

Version-Release number of selected component (if applicable):
yumex-2.9.4-1.fc12.noarch
python-2.6.2-2.fc12.x86_64


How reproducible:
always

Steps to Reproduce:
1. start yumex from terminal
2.
3.
  
Actual results:
yumex ends with "Segmentation fault".
from terminal log ( see attachment ).
Starting yum child process
YUM: Loaded plugins: presto
History Enabled
/usr/bin/yumex: line 5:  2388 Segmentation fault      (core dumped) /usr/bin/python /usr/share/yumex/yumex.pyc $*


Expected results:
See yumex gui

Additional info:
There is ABRT on python-2.6.2-2.fc12.x86_64
After working 10 minutes to report then there is no report yet.
"3194 Segmentation fault      (core dumped) "  the number 3194 is not constant

System is fully update as Software Update says.

Comment 1 Electron 2009-12-21 21:01:43 UTC
Created attachment 379711 [details]
yumex core dump log

Same here

cpu : x86-32
yumex-2.9.4-1.fc12.noarch
python-2.6.2-2.fc12.i686

attachement : terminal log of 'yumex -d'

Comment 2 Tim Lauridsen 2009-12-22 08:58:10 UTC

*** This bug has been marked as a duplicate of bug 548849 ***


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