Bug 1328560 - crash when choosing ISO on samba server
crash when choosing ISO on samba server
Status: NEW
Product: Fedora
Classification: Fedora
Component: liveusb-creator (Show other bugs)
Unspecified Windows
unspecified Severity unspecified
: ---
: ---
Assigned To: Martin Bříza
Fedora Extras Quality Assurance
Depends On:
Blocks: 1310542
  Show dependency treegraph
Reported: 2016-04-19 12:30 EDT by Chris Murphy
Modified: 2016-09-20 10:24 EDT (History)
3 users (show)

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

Attachments (Terms of Use)

  None (edit)
Description Chris Murphy 2016-04-19 12:30:18 EDT
Description of problem: When choosing a Fedora ISO on a Samba server, liveusbcreator crashes.

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

How reproducible:

Steps to Reproduce:
1. Fedora-Live-Workstation-x86_64-23-10.iso on a Fedora 23 Samba server
2. Windows 10 in this virt-manager VM can copy files to and from the server through Explorer just fine
3. Launch liveusb-creator.exe as administrator
4. Click on Custom OS > Select Live ISO > navigate to the server share and find the ISO, click Open.

Actual results:

Crash. "liveusb-creator.exe has stopped working.

Expected results:

Should not crash.

Additional info:

Traceback (most recent call last):
  File "liveusb\gui.py", line 464, in path
  File "liveusb\gui.py", line 193, in path
  File "liveusb\creator.py", line 238, in set_iso
WindowsError: [Error 123] The filename, directory name, or volume label syntax is incorrect: u'C:\\Users\\chris\\Downloads\\liveusb-creator\\liveusb-creator\\file:\\f23s\\brick1\\software\\Fedora\\Fedora-Cloud_Atomic-x86_64-23.iso'

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

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