Bug 543611 - preupgrade crashes on resume
Summary: preupgrade crashes on resume
Keywords:
Status: CLOSED DUPLICATE of bug 538118
Alias: None
Product: Fedora
Classification: Fedora
Component: preupgrade
Version: 11
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-02 18:07 UTC by Jeremy Huddleston
Modified: 2014-01-21 23:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-02 18:14:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeremy Huddleston 2009-12-02 18:07:27 UTC
Description of problem:

preupgrade crashes when attempting to resume an upgrade from fc11 to fc12

Version-Release number of selected component (if applicable):
1.1.3-1.fc11.noarch

How reproducible:
Uncertain


Steps to Reproduce:
1. Install F11
2. Update F11 to latest versions
3. Run 'preupgrade'
4. Quit preupgrade
5. Restart preupgrade
6. Answer, "Yes, resume"
  
Actual results:

preupgrade crashes:

Traceback (most recent call last):
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 773, in <module>
    widgets = PreUpgradeGtk()
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 376, in __init__
    self._do_main()
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 259, in _do_main
    self.main_preupgrade()
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 436, in main_preupgrade
    download_progressbar=self.dnlProgress)
  File "/usr/lib/python2.6/site-packages/preupgrade/__init__.py", line 130, in setup
    self.complete_repo_setup()
  File "/usr/lib/python2.6/site-packages/preupgrade/__init__.py", line 328, in complete_repo_setup
    repo._grabfunc.opts.user_agent = __user_agent__
AttributeError: 'NoneType' object has no attribute 'opts'


Expected results:

Continue the upgrade


Additional info:

Comment 1 seth vidal 2009-12-02 18:14:17 UTC

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


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