Version-Release number of selected component: blivet-gui-1.0.2-1.fc23 Additional info: reporter: libreport-2.6.3 cmdline: /usr/bin/python3 /usr/bin/blivet-gui executable: /usr/bin/blivet-gui kernel: 4.2.6-301.fc23.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: client.py:220:remote_control:TypeError: 'NoneType' does not support the buffer interface Traceback (most recent call last): File "/usr/bin/blivet-gui", line 120, in <module> main() File "/usr/bin/blivet-gui", line 109, in main kickstart_mode=options.kickstart) 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 Local variables in innermost frame: args: (False,) command: 'init' self: <blivetgui.communication.client.BlivetGUIClient object at 0x7f48f2ebc780> pickled_data: b'\x80\x03C\n2643336066q\x00X\x04\x00\x00\x00initq\x01\x89\x85q\x02\x87q\x03.'
Created attachment 1102028 [details] File: backtrace
Created attachment 1102029 [details] File: environ
Hi, there should be some logs in /tmp (blivet.log and program.log are the most important), could you please attach them here? And please run blivet-gui from terminal (simply using "blivet-gui" command), it might print some more errors there. Thanks.
I ran blivet-gui as root from Konsole on KDE Plasma 5.4.3 and it quickly crashed by selecting sdb a External USB 3.0 drive from disks. I reported it "New bug id: 1288943" Here are The error messages from the terminal: [root@localhost tmp] # blivet-gui Can't open file 'uid': No such file or directory Failed to open connection to D-Bus session bus: The connection is closed Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Can't open /root/.config/abrt/settings/forbidden_words.conf Can't open /root/.config/abrt/settings/ignored_words.conf
Created attachment 1103016 [details] Blivet Logs from /tmp Here are the requested logs from /tmp. I ran blivet-gui from Konsole as both Root and through sudo and it crashed both times very quickly.
Similar problem has been detected: I tried to start blivet-gui. reporter: libreport-2.6.4 cmdline: /usr/bin/python3 /usr/bin/blivet-gui executable: /usr/bin/blivet-gui kernel: 4.4.6-300.fc23.x86_64 package: blivet-gui-1.0.5-1.fc23 reason: client.py:220:remote_control:TypeError: 'NoneType' does not support the buffer interface runlevel: N 5 type: Python3 uid: 1000
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.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.