Bug 1284615 - blivet-gui crashes on f23
blivet-gui crashes on f23
Product: Fedora
Classification: Fedora
Component: python-blivet (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vojtech Trefny
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-23 11:33 EST by Peter Robinson
Modified: 2016-12-20 11:12 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 11:12:15 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
blivet log (64.19 KB, text/plain)
2015-12-08 06:23 EST, Martin Kolman
no flags Details
program log (2.07 KB, text/plain)
2015-12-08 06:24 EST, Martin Kolman
no flags Details

  None (edit)
Description Peter Robinson 2015-11-23 11:33:47 EST
$ rpm -qa|grep blivet

$ blivet-gui 
Traceback (most recent call last):
  File "/usr/lib64/python3.4/socketserver.py", line 305, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib64/python3.4/socketserver.py", line 331, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib64/python3.4/socketserver.py", line 344, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib64/python3.4/socketserver.py", line 673, in __init__
  File "/usr/lib/python3.4/site-packages/blivetgui/communication/server.py", line 123, in handle
  File "/usr/lib/python3.4/site-packages/blivetgui/communication/server.py", line 286, in _blivet_utils_init
    self.blivet_utils = BlivetUtils(*args)
  File "/usr/lib/python3.4/site-packages/blivetgui/blivet_utils.py", line 178, in __init__
  File "/usr/lib/python3.4/site-packages/blivet/blivet.py", line 279, in reset
  File "/usr/lib/python3.4/site-packages/blivet/devicetree.py", line 554, in populate
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 1623, in populate
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 1692, in _populate
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 715, in addUdevDevice
    device = self.addUdevDMDevice(info)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 305, in addUdevDMDevice
    slave_devices = self._addSlaveDevices(info)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 253, in _addSlaveDevices
    slave_name = udev.device_get_name(slave_info).replace("!", "/")
  File "/usr/lib/python3.4/site-packages/blivet/udev.py", line 147, in device_get_name
    if "DM_NAME" in udev_info:
TypeError: argument of type 'NoneType' is not iterable
Traceback (most recent call last):
  File "/usr/bin/blivet-gui", line 120, in <module>
  File "/usr/bin/blivet-gui", line 109, in main
  File "/usr/lib/python3.4/site-packages/blivetgui/blivetgui.py", line 80, in __init__
    ret = self.client.remote_control("init", self.kickstart_mode)
  File "/usr/lib/python3.4/site-packages/blivetgui/communication/client.py", line 220, in remote_control
    answer = pickle.loads(self._recv_msg())
TypeError: 'NoneType' does not support the buffer interface
Comment 1 Martin Kolman 2015-12-08 06:23 EST
Created attachment 1103544 [details]
blivet log
Comment 2 Martin Kolman 2015-12-08 06:24 EST
Created attachment 1103545 [details]
program log
Comment 3 Martin Kolman 2015-12-08 06:25:08 EST
NAME                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                                             8:0    0 298,1G  0 disk  
├─sda1                                          8:1    0   500M  0 part  /boot
└─sda2                                          8:2    0 297,6G  0 part  
  └─luks-03eeaf47-f9e1-4172-9bdf-f96a6ed68e59 253:0    0 297,6G  0 crypt 
    ├─fedora_dhcp--29--242-swap               253:1    0   7,5G  0 lvm   [SWAP]
    ├─fedora_dhcp--29--242-root               253:2    0    50G  0 lvm   /
    └─fedora_dhcp--29--242-home               253:4    0 240,1G  0 lvm   /home
sdb                                             8:16   0 447,1G  0 disk  
└─sdb1                                          8:17   0     1G  0 part
Comment 4 Fedora End Of Life 2016-11-24 08:39:59 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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 23 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 5 Fedora End Of Life 2016-12-20 11:12:15 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

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.