-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Error message sometimes missing when inter-qube file copy/move fails due to disallowed characters in filename #8738
Error message sometimes missing when inter-qube file copy/move fails due to disallowed characters in filename #8738
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Could we keep this ticket focused though...
Just so we're all on the same page, in a Bash shell that should be identical to (1) What's the sticking point with these strings? I've tried a few online Unicode analyzers such as https://unicodedecode.com/ and they both seem to be valid UTF-8, made of ordinary(?) Arabic or Hebrew letters, without directionality changes or embedded right-to-left markers.
(2) The filecopy GUI should surface any error to the user. |
Implicit right-to-left: https://github.com/QubesOS/qubes-linux-utils/blob/main/qrexec-lib/unicode-generator.c#L180-L190 |
Harsh (and a point in favor of adding less restrictive modes), but not unreasonable as a default IMO. Leaving (2), why is |
This comment was marked as off-topic.
This comment was marked as off-topic.
qvm-copy
/qvm-move
fails due to disallowed characters in filename
If I understand correctly, this issue is only about there sometimes not being an error message when inter-qube file copy/move fails due to disallowed characters in the filename. It is not about whether the failure itself is desirable or should be changed (that's #8332). The point here is simply that when the failure occurs, there should always be a suitable error message, which is not currently the case. |
qvm-copy
/qvm-move
fails due to disallowed characters in filenameqvm-copy
/qvm-move
fails due to disallowed characters in filename
qvm-copy
/qvm-move
fails due to disallowed characters in filenameIn practice kdialog wasn't used, because the package was built without USE_KDIALOG being defined. Fixes QubesOS/qubes-issues#8738
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
1 similar comment
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
2 similar comments
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
For PROGRESS_TYPE=gui the error handler calls zenity, which fails to launch if the error message contains characters not supported by the locale's charset (e.g. LC_CTYPE=C). Filenames in the error message were already sanitized to printable ASCII, but then enclosed in UTF-8 curly quotation marks. Fixes QubesOS/qubes-issues#8738 (cherry picked from commit 71f5b04)
Qubes OS release
4.2.0
Installed RC4 and installed updates since then.
Brief summary
As discussed in #8332 , copy/move files can fail when there are non-english characters, and that is an intended behavior.
However, copy/move sometimes fails without any warning message, which can result in loss of data.
Steps to reproduce
Create a file named عربية or עברית, e.g.
touch عربية
ortouch עברית
.From the file manager, choose copy to other appVM.
Expected behavior
File is copied or an error message is presented.
Actual behavior
File not copied and no error message is displayed to user.
I haven't checked if command line provides any error indication, but if it does not, it would create issues with automatic scripts.
As side note, I am sure that the choice to have strict file name validation has been debated. I personally find that it damages usability (even if there is an error message) because user have existing files and receive files from others. I am sure that there are good security reasons for the choice.
The text was updated successfully, but these errors were encountered: