-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pathname with non-ASCII cause cannot extract ISO image #93
Comments
@ShvonderSiN |
@ShvonderSiN The screenshot below shows I have selected Ubuntu Mini Remix 14.04 32-bit ISO into Customizer 4.1.0 from master branch, as proof. Please make sure you have read and follow the recommended way of installation, as I have noted in the point no.4 in the First guide page. Tested valid on Xubuntu and Linux Mint 32-bit host systems. If you still face problem, please provide the output log and screenshot for our troubleshooting. |
still experiencing the problem on my computer or in a virtual machine, does not begin unpacking. Linux Mint 17.1 cinnamon x64 |
I can't help you because you don't provide any details of the problem.. Please provide the output log and screenshot when you face the problem. Don't know how? Do I need to explain the lengthy steps?
Copy and paste the Terminal output log on somewhere like GitHub Gists or Pastebin. And provide the link to the content you have pasted in your reply here. |
@ShvonderSiN What locale (language encoding) are you using on your system?
Copy and paste the output from the Terminal window into your reply here. |
LANG=ru_RU.UTF-8 |
@ShvonderSiN At first, I changed my test machine locale to same as yours (ru_RU.UTF-8), but still failed to reproduce this issue. So this is not host system locale problem. Next, I changed the ISO filename from English to Russian, and bingo! This issue can be reproduced with similar error. It was the filename locale problem. The quick solution? As temporary workaround, please change your ISO image filename to using English alphanumeric characters only. For example, if your ISO image filename is Now, Customizer should be able to extract the ISO file properly. |
I have all the names of the ISO without Cyrillic characters, as downloaded from the official websites so I kept. Just in case renamed one way just in cinnamon - it didn't help. |
I see.. this looks more tricky than I thought. Now I have different opinion: Customizer 4.1.0 might not read non-ASCII filenames, which is the reason seeing such error. Even without the Cyrillic characters and even looks like using normal alphanumeric characters, those may not be using ASCII filenames. To check this, do the following:
To summarize, do something like this (showing how I did on my test machine): Copy and paste the output in step 5 from the Terminal into your reply here. |
|
I found what the problem is. The problem is in the Cyrillic alphabet but not in the file name, but the path to him. My Downloads folder called Загрузки. So, I moved the ISO file in the home directory and from there, the ISO began to unpack normally. I hope soon you will fix this annoying bug, so i can use the program without restrictions, thanks for the help!!! |
@ShvonderSiN Anyway, please provide the details from beginning next time. |
unicode has always been a problem both with Python 2 and 3. with PyQt strings returned by dialogs and such as QString which have to be normalized to able able to write them into the config and all. Altough not this fixes some of the issues it can not do more than handle strings properly _internally_, ConfigPraser still fails because it attempts to convert the to string via str() thus any chanages to the config will _not_ apply but atleast the actions will execute now (after an error message) when paths have unicode characters in them. feel free to improve on this.
unicode has always been a problem both with Python 2 and 3. with PyQt strings returned by dialogs and such are QString which have to be normalized to be able to write them into the config and all. Altough this fixes some of the issues it can not do more than handle strings properly _internally_, ConfigPraser still fails because it attempts to convert the key to string via str() thus any chanages to the config will _not_ apply but atleast the actions will execute now (after an error message) when paths have unicode characters in them. feel free to improve on this.
I think i have the same problem. But my ISO-Name is simple...
Edit: Customizer 3.3.2 works fine with this ISO. |
The issue should be fixed, I've tested it with ISO image that has unicode characters in it and is in directory that also has unicode characters in its name - works for me. The only requirement is that the host has unicode locales in use either set globally or via env. variable. On a side note - major distributions build Python with |
Confirmed fix using Customizer with latest commit from master branch. Tested using Japanese unicode renamed in both folder and file names. Below is screenshot as proof from my side. Also updated the Developer notes about this fix. |
@clearkimura |
I have retested the git version from now with kubuntu 14.04.2 and XUbuntu 13.10 that is updated to 14.04.02 (Pakages from today). No more problem when i open an iso. Thanks! |
@ranseyer |
Installation Customizer went without problems. After installation, launched the utility. Clicked on the button Select ISO. Choose the image (Ubuntu, linux Mint) and nothing happens. In version 3.2.3 started unpacking but in this 4.1.0 nothing happens. Launched on LInux Mint 17.1 cinnamon.
The text was updated successfully, but these errors were encountered: