Bug 743875 - AttributeError: 'NoneType' object has no attribute 'path'
Summary: AttributeError: 'NoneType' object has no attribute 'path'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3c584356344e7c33e025d5967cf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 11:13 UTC by D. Charles Pyle
Modified: 2013-02-13 16:41 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:34:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb-0W5OzB (572.55 KB, text/plain)
2011-10-06 11:13 UTC, D. Charles Pyle
no flags Details

Description D. Charles Pyle 2011-10-06 11:13:13 UTC
libreport version: 2.0.5.982
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-0.rc6.git0.3.fc16.x86_64
product:        Fedora
reason:         AttributeError: 'NoneType' object has no attribute 'path'
time:           Thu Oct  6 05:12:13 2011
version:        16-Beta

anaconda-tb-0W5OzB: Binary file, 586296 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 16.20 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/bootloader_main_gui.py", line 185, in getScreen
:    (self.bldev.path,))
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1272, in display_step
:    new_screen = self.currentWindow.getScreen(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1159, in display_step
:    return self.icw.display_step(step)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 377, in dispatch
:    rc = self.anaconda.intf.display_step(self.step)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1203, in nextClicked
:    self.anaconda.dispatch.go_forward()
:AttributeError: 'NoneType' object has no attribute 'path'

Comment 1 D. Charles Pyle 2011-10-06 11:13:24 UTC
Created attachment 526674 [details]
File: anaconda-tb-0W5OzB

Comment 2 Chris Lumens 2011-10-11 13:33:58 UTC
What bootloader-related selections did you make that resulted in this situation?

Comment 3 D. Charles Pyle 2011-10-11 20:31:23 UTC
(In reply to comment #2)
> What bootloader-related selections did you make that resulted in this
> situation?

This also is not the first time it happened. It happened previously but I did not have a bugzilla account at that time.

The first time around, the one not reported, I chose the option to write grub2 to a partition and overwrite the previous boot information on an upgrade. The second time it happened, I was attempting a fresh installation of Fedora 16 Beta.

I finally got it to work by installing Fedora 15 and upgrading that with Fedora 16 Beta and leaving the original boot configuration intact.

I never was able to get Fedora 16 Alpha to install reliably on my machine.

Dell Inspiron 560
4GiB DDR3 RAM
1 Terabyte secondary drive with 300 GiB allocated for Linux install on two logical volumes in an extended partition type, DELL OEM partition, Utilities partition, and Windows 7 Home x64.
2 Terabyte primary drive with Windows 7 Ultimate x64 and a BSD-derived unix system
3.2 GHz E6700 Dual Core processor with Speedstep active (I have since disabled it).
ATi-based Asus EAH5750Formula video card with 1 GByte GDDR5 RAM.

There is other hardware installed but it probably is not relevant to the above.

Comment 4 D. Charles Pyle 2011-10-11 20:35:16 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > What bootloader-related selections did you make that resulted in this
> > situation?
> 
> This also is not the first time it happened. It happened previously but I did
> not have a bugzilla account at that time.
> 
> The first time around, the one not reported, I chose the option to write grub2
> to a partition and overwrite the previous boot information on an upgrade. The
> second time it happened, I was attempting a fresh installation of Fedora 16
> Beta.
> 
> I finally got it to work by installing Fedora 15 and upgrading that with Fedora
> 16 Beta and leaving the original boot configuration intact.
> 
> I never was able to get Fedora 16 Alpha to install reliably on my machine.
> 
> Dell Inspiron 560
> 4GiB DDR3 RAM
> 1 Terabyte secondary drive with 300 GiB allocated for Linux install on two
> logical volumes in an extended partition type, DELL OEM partition, Utilities
> partition, and Windows 7 Home x64.
> 2 Terabyte primary drive with Windows 7 Ultimate x64 and a BSD-derived unix
> system
> 3.2 GHz E6700 Dual Core processor with Speedstep active (I have since disabled
> it).
> ATi-based Asus EAH5750Formula video card with 1 GByte GDDR5 RAM.
> 
> There is other hardware installed but it probably is not relevant to the above.

I forgot to add that even after the installation I was left with literally thousands of dependency problems after the upgrade install, which I manually had to fix using various tools such as rpmreaper, yum, and so forth as no one solution would fix them all.

Comment 5 Gilles J. Seguin 2011-11-07 15:40:30 UTC
after fc16-beta install on /dev/sdd 
choosing sdd1 from grub menu does not chain boot grub2

trying upgrade on fc16-beta to install grub2 on sdd1 instead of sdd
give same result.

Comment 6 Gilles J. Seguin 2011-11-08 00:06:15 UTC
(In reply to comment #5)
the message was badly explain.

> after fc16-beta install on /dev/sdd
the first boot requires
> choosing sdd1 from the grub menu of a previous fc15.
> this selection does not boot chain grub2 that is on /dev/sdd

i decided to try upgrade. The upgrade on the fresh fc16 install would allow changing the boot loader position from /dev/sdd MRB to /dev/sdd1 partition.  Which is failing with this error message.

Comment 7 Michael 2011-11-12 22:04:09 UTC
After Bug 748119 fix , Anaconda find Fedora 15 for Upgrade but when i choose "create new boot loader configuration"  Popup an anaconda window with this Error.

Comment 8 Michael 2011-11-14 07:33:36 UTC
successfully upgrade to Fedora 16 following this steps :

1. Install grub2 to Fedora 15 and setting up to boot with it.
2. Upgrade to Fedora 16 with selection "to not change bootloader".
3. Run grub2-install /dev/sd* from Rescue mode.

Comment 9 D. Charles Pyle 2011-11-14 22:20:03 UTC
(In reply to comment #8)
> successfully upgrade to Fedora 16 following this steps :
> 
> 1. Install grub2 to Fedora 15 and setting up to boot with it.
> 2. Upgrade to Fedora 16 with selection "to not change bootloader".
> 3. Run grub2-install /dev/sd* from Rescue mode.

That did not work for me. I was left with an unbootable system no matter how many times I ran the grub2 installer. I also use the Windows BCD to load all of the operating systems on my computer's two hard disks. Fedora is on the second hard drive.

I had to install Fedora 15 and use the standard Grub, afterward upgrading to Fedora 16 and leaving Grub unchanged. It boots but I had to manually configure Grub to load the new kernel to do so.

Comment 10 Adam Williamson 2011-11-15 21:03:03 UTC
Magnum: it's worth giving us your exact traceback, as 'NoneType' object has no attribute 'path' is one of those 'generic' traces that can be caused by multiple, different bugs.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Michael 2011-11-15 21:34:39 UTC
I tried to Upgrade from Fedora 15 to 16 but suffered from the Bugs :

a. Bugzilla: #748119 (Attempting to upgrade a system with /var on a different partition or LV to / will fail)
b.  Bugzilla: #750794 (Cannot boot with /boot partition on a software RAID array)

After i find the fix for Bug 748119 with 748119,img the upgrade process with Fedora 16 DVD find my previous installation of Fedora 15.

When i choose to upgrade F15, for the bootloader i had only 2 options:
(I think there was an option of updating bootloader in fedora 15)

1. Create new boot loader configuration
2. Skip - Do not change bootloader 

 As i said, in my first attempt i choose 1 and then popup window anaconda logger which automatically subscribe me to this bug.

Comment 12 gatlibs 2012-06-05 00:07:17 UTC
Dell Studio 1555
F16 x86_64 (3.3.7-1)
2 Intel Core2 Duo
54GB fedora root volume /
524MB grub boot volume /boot
grub2 bootloader (from fedora without external modification besides one preupgrade entry for Fedora 17 alpha that wouldn't work.)
The failure occured immediately after the selection of non-thrid party bootloader A.K.A. default fedora boot loader option that was auto-selected.
Unless having a preupgrade entry breaks the D.V.D. upgrade, then I don't know why I would have an issue. How would I give a traceback or anything that might help solve this issue?

Comment 13 Pavel Zhukov 2012-11-23 17:09:40 UTC
The problem still persists in Fedora 17. 

1) Install new system 
2) Boot from installation media
3) select "update exiting system"
4) Select "Update bootloader"

Comment 14 Fedora End Of Life 2013-01-16 10:10:24 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 15 Fedora End Of Life 2013-02-13 08:34:13 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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