Bug 221218 - Yumex crashes at Enable/Disable Repositories
Summary: Yumex crashes at Enable/Disable Repositories
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-02 23:45 UTC by Enrique Luna Estrada
Modified: 2014-01-21 22:56 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-06-12 06:58:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Enrique Luna Estrada 2007-01-02 23:45:01 UTC
Description of problem:
When I start Yumex from the Menu, at the moment of executing the Enable/Disable
Repositories step it sends an exception code then Exits.

Version-Release number of selected component (if applicable):
1.2.1

How reproducible:
Always (everytime it starts)

Steps to Reproduce:
1. Just run Yumex from the Menu 
  
Actual results:
Not able to install components with Yumex

Expected results:
Be able to install components with Yumex

Additional info:
I selected Yumex because I receive an error on the Add/Remove Software
applications that comes with Fedora, but since this applications sends me an
error of "UNABLE TO RETRIEVE SOFTWARE INFORMATION: Cannot find a valid baseurl
for repo: core" I looked for another option and found Yumex, I installed yumex
with yum install yumex, them executed it for the first time, it opened ok, then
I whent to Preferences and set up a proxy, closed it and re-open it and the
exception started.

Comment 1 Tim Lauridsen 2007-01-03 10:24:18 UTC
Please attach the exception text, so i can see the error.

It sounds like there is a problem with the proxy definition, what have you typed
in the proxy preferences.

you can use 'yumex -n' to start yumex without loading repo metadata, and then
check the proxy preferences.


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