Description of problem: Trying to: 1. remove a Fedora Live ISO from an external USB HDD 2. creating a new partition table 3. creating and formatting a vFAT partition Version-Release number of selected component: blivet-gui-runtime-2.1.5-2.fc26 Additional info: reporter: libreport-2.9.1 cmdline: /usr/bin/python3 /usr/bin/blivet-gui crash_function: commit exception_type: _ped.IOException executable: /usr/bin/blivet-gui kernel: 4.11.9-300.fc26.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: #1 commit in /usr/lib64/python3.6/site-packages/parted/disk.py:212 #2 new in /usr/lib64/python3.6/site-packages/parted/decorators.py:42 #3 commit in /usr/lib/python3.6/site-packages/blivet/formats/disklabel.py:284 #4 run_with_lock in /usr/lib/python3.6/site-packages/blivet/threads.py:45 #5 _create in /usr/lib/python3.6/site-packages/blivet/formats/disklabel.py:277 #6 run_with_lock in /usr/lib/python3.6/site-packages/blivet/threads.py:45 #7 create in /usr/lib/python3.6/site-packages/blivet/formats/__init__.py:509 #8 run_with_lock in /usr/lib/python3.6/site-packages/blivet/threads.py:45 #9 execute in /usr/lib/python3.6/site-packages/blivet/deviceaction.py:607 #10 run_with_lock in /usr/lib/python3.6/site-packages/blivet/threads.py:45
Created attachment 1299280 [details] File: backtrace
Created attachment 1299281 [details] File: cgroup
Created attachment 1299282 [details] File: cpuinfo
Created attachment 1299283 [details] File: environ
Created attachment 1299284 [details] File: mountinfo
Created attachment 1299285 [details] File: namespaces
Created attachment 1299286 [details] File: open_fds
Similar problem has been detected: On an external USB harddisk trying to: 1. create a partition 2. format the partition to vfat The error message stated that the kernel could not be informed about the change because the device was busy. Indeed it showed up mounted in nautilus. reporter: libreport-2.9.1 cmdline: /usr/bin/python3 /usr/bin/blivet-gui crash_function: commit exception_type: _ped.IOException executable: /usr/bin/blivet-gui kernel: 4.11.9-300.fc26.x86_64 package: blivet-gui-runtime-2.1.5-2.fc26 reason: blivetgui.py:219:_reraise_exception:_ped.IOException: Partition(s) 1 on /dev/sdd have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. runlevel: N 5 type: Python3 uid: 1000
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.