Opened 2 years ago
Closed 2 years ago
#156 closed defect (fixed)
Display one _readable_ message when vm2vm file copy fails...
| Reported by: | joanna | Owned by: | rafal |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1 Beta 1 |
| Component: | core | Keywords: | |
| Cc: |
Description
...instead of cryptic messages (in a dozen of windows) that tell absolutely nothing and only intimidate the user. Just ONE window, and one CLEAR message, ok?
Change History (6)
comment:1 Changed 2 years ago by rafal
comment:2 Changed 2 years ago by rafal
http://git.qubes-os.org/?p=rafal/core.git;a=commit;h=93e5b749fd20ae7c3ce879057e469f09cd2dcd04
tries to ensure only one error window is produced.
No information on required error message format so far, so no changes there.
comment:3 Changed 2 years ago by rafal
- Status changed from new to accepted
comment:4 Changed 2 years ago by joanna
Just make it somehow understandable for the typical gui user -- no references to log files, xids, etc.
comment:5 Changed 2 years ago by rafal
In the current version, there is no reference to log files nor xids.
The typical error message looks like this:
qfile-agent: Fatal error: opendir somefile (error type: permission denied)
Is it somehow understandable for the typical gui user ? If not, please specify what to change.
comment:6 Changed 2 years ago by joanna
- Resolution set to fixed
- Status changed from accepted to closed

This ticket is hardly useful.
Please specify in which circumstances there is a dozen of error messages windows. I can see there can be two. If that is what you mean, it can be done, although with some added code - it will require to split error handling path to distinguish between "local" error, eg disk write, and "remote" error - e.g. unexpected EOF when reading, and ignore the latter (assuming the other end will produce proper message).
The error messages are not cryptic and carry information on the cause of the problem, if this information is available. If you do not agree, please specify the format of error messages (e.g. Internet Explorer style catch-all "sorry, something went went wrong; maybe disk full, maybe unreadable file, maybe something else; contact your Qubes support for help if the issue persists"). "Just one CLEAR message" is not a sufficient specification (as stated before, for me the current error messages are clear).