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

Display one _readable_ message when vm2vm file copy fails... #156

Closed
marmarek opened this Issue Mar 8, 2015 · 6 comments

Comments

Projects
None yet
1 participant
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 29 Mar 2011 00:34 UTC
...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?

Migrated-From: https://wiki.qubes-os.org/ticket/156

@marmarek marmarek added this to the Release 1 Beta 1 milestone Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 29 Mar 2011 08:39 UTC
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).

Member

marmarek commented Mar 8, 2015

Comment by rafal on 29 Mar 2011 08:39 UTC
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).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 29 Mar 2011 11:09 UTC
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.

Member

marmarek commented Mar 8, 2015

Comment by rafal on 29 Mar 2011 11:09 UTC
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.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by rafal on 29 Mar 2011 11:09 UTC

Member

marmarek commented Mar 8, 2015

Modified by rafal on 29 Mar 2011 11:09 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 30 Mar 2011 08:45 UTC
Just make it somehow understandable for the typical gui user -- no references to log files, xids, etc.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 30 Mar 2011 08:45 UTC
Just make it somehow understandable for the typical gui user -- no references to log files, xids, etc.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 30 Mar 2011 08:54 UTC
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.

Member

marmarek commented Mar 8, 2015

Comment by rafal on 30 Mar 2011 08:54 UTC
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.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 30 Mar 2011 08:55 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 30 Mar 2011 08:55 UTC

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment