Bug 440976 - partition resize causes traceback in Fedora 9 beta
Summary: partition resize causes traceback in Fedora 9 beta
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-04 19:07 UTC by Paul Walmsley
Modified: 2008-04-04 19:27 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-04 19:27:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda python stack trace (714 bytes, text/plain)
2008-04-04 19:25 UTC, Paul Walmsley
no flags Details

Description Paul Walmsley 2008-04-04 19:07:53 UTC
Description of problem:
In Fedora 9 beta, selecting "Resize existing partition and create default layout
in free space" causes a Python crash and stack backtrace on a stock IBM Thinkpad
T61 8897CTO with factory partition layout.  First partition is recovery
partition; second is Windows Vista Home Basic.  Both partitions are NTFS.

The partition selection dialog appears in the top left corne

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

How reproducible:
See above.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Paul Walmsley 2008-04-04 19:24:42 UTC
more information:

When "Resize existing partition ..." is selected, and the "Next" button is
pressed, a dialog appears in the top left corner of the screen, without the
window frame.  It reads: "Which partition would you like to resize to make room
for your installation?" and displays a blank drop-down.  Below that, it reads
"Resize target" along with a corresponding drop-down, which reads "1".  

A stack trace is immediately generated, however, without any opportunity to
interact with this window.  I've attached the Python traceback, which I had to
copy by hand due to other Anaconda bugs.  It does not include the Anaconda dump
due to sheer size, but if there is specific information you need from the
Anaconda portion of the dump, please let me know and I will provide it.  


Comment 2 Paul Walmsley 2008-04-04 19:25:24 UTC
Created attachment 301327 [details]
anaconda python stack trace

Comment 3 Jeremy Katz 2008-04-04 19:27:02 UTC
Fixed this up last week and it should be working with last week's snapshot


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