Bug 928906 - AttributeError: 'NoneType' object has no attribute 'unpack' (change SSID in the Network Spoke)
Summary: AttributeError: 'NoneType' object has no attribute 'unpack' (change SSID in t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-28 17:27 UTC by Reartes Guillermo
Modified: 2015-02-18 11:10 UTC (History)
5 users (show)

Fixed In Version: anaconda-19.21-1
Clone Of:
Environment:
Last Closed: 2015-02-18 11:10:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda-tb-xxx file (297.54 KB, text/plain)
2013-03-28 17:27 UTC, Reartes Guillermo
no flags Details
anaconda.log (2.33 KB, text/plain)
2013-03-28 17:27 UTC, Reartes Guillermo
no flags Details
program.log (28.24 KB, text/plain)
2013-03-28 17:33 UTC, Reartes Guillermo
no flags Details
storage.log (114.35 KB, text/plain)
2013-03-28 17:34 UTC, Reartes Guillermo
no flags Details
syslog file (113.09 KB, text/plain)
2013-03-28 17:34 UTC, Reartes Guillermo
no flags Details
ifc (486 bytes, text/plain)
2013-03-28 17:35 UTC, Reartes Guillermo
no flags Details
anaconda-tb-xxx file (another system) (272.72 KB, text/plain)
2013-03-28 17:35 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2013-03-28 17:27:01 UTC
Created attachment 717739 [details]
anaconda-tb-xxx file

Description of problem:

If i switch the SSIDs in the Network Spoke, anaconda crashes. Please note that i did not connect to the first SSID, i just made the mistake and selected an incorrect SSID and then selected the correct one. 

Version-Release number of selected component (if applicable):
F19a TC2 (19.13)

How reproducible:
always

Steps to Reproduce:
0. Boot normal video without any kernel parameters.
1. Anaconda will proceed to the Netowrk Spoke automatically:

There are two network devices shown, a USB WIFI and an onboard ETHERNET.
There is also an unsupported (need staging) PCIe WIFI that is not shown nor used in this case. 
For the onboard ETHERNET, the cable is not connected, so it is off.
By default the ETHERNET device is selected and since the cable is unplugged, there is no option to turn it on.

2. Select the WIFI device and select an incorrect SSDI (not the one i want)
3. Change the SSID to the corrrect one.
4. Enter "configure" to set the password, click cancel
5. anaconda cashes

Note, the crash happens sometimes on #2, or sometimes just changing SSIDs.

  
Actual results:
anaconda crahes

Expected results:
no crash, just switch the SSID.

Additional info:

anaconda 19.13 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/pyanaconda/nm.py", line 125, in nm_activated_devices
    devices = proxy.get_cached_property("Devices").unpack()
  File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 166, in getHostname
    for dev in nm.nm_activated_devices():
  File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 1303, in _update_hostname
    hostname = network.getHostname()
  File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 35, in wrap
    func(*args)
AttributeError: 'NoneType' object has no attribute 'unpack'

Comment 1 Reartes Guillermo 2013-03-28 17:27:29 UTC
Created attachment 717740 [details]
anaconda.log

Comment 2 Reartes Guillermo 2013-03-28 17:33:48 UTC
Created attachment 717742 [details]
program.log

Comment 3 Reartes Guillermo 2013-03-28 17:34:16 UTC
Created attachment 717743 [details]
storage.log

Comment 4 Reartes Guillermo 2013-03-28 17:34:40 UTC
Created attachment 717744 [details]
syslog file

Comment 5 Reartes Guillermo 2013-03-28 17:35:07 UTC
Created attachment 717745 [details]
ifc

Comment 6 Reartes Guillermo 2013-03-28 17:35:42 UTC
Created attachment 717746 [details]
anaconda-tb-xxx file (another system)

Comment 7 Radek Vykydal 2013-06-14 13:53:40 UTC
This should be fixed in anaconda-19.21-1

Comment 8 Fedora End Of Life 2015-01-09 22:32:49 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 9 Fedora End Of Life 2015-02-18 11:10:32 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.