Bug 199351 - Crashing yumex via changing options on start
Summary: Crashing yumex via changing options on start
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 5
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: 2006-07-19 01:54 UTC by James Burke
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 1.0.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-07-19 06:25:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Burke 2006-07-19 01:54:54 UTC
Description of problem:
Yumex crashes if one decides to change Repository options before it finished
updating headers/etc upon start.

Version-Release number of selected component (if applicable):
Name        : yumex                        Relocations: (not relocatable)
Version     : 0.99.16                           Vendor: Fedora Project
Release     : 1.0.fc5                       Build Date: Thu 06 Apr 2006 07:17:53
AM EDT


How reproducible:


Steps to Reproduce:
1. start yumex from an xterm box
2. Upon starting, progress bars on bottom indicate download/updating things--
While it's doing this, click on 'Repos' in left pane.
3. Now in repos dialog, change repos checkboxes and select 'Refresh'
  
Actual results:
Crashes 

Expected results:

Additional info:
I would get different crash reports. A routing is not being reset while using
obsolete variables-- I can tell this because one crash report says 'out of
range' for some tuple. I believe this shouldn't be too hard to fix. If one does
activity on any of the buttons, there should be a cancel dialog popup or there
should be a suspend/wait/reset states implemented so the variables set from the
Repos dialog box be reflected.

Comment 1 Tim Lauridsen 2006-07-19 06:25:32 UTC
Try to update to the latest stable yumex release 1.0.2.
You can change anything before metadata is loaded in the stable release.



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