Actions
Feature #3604
closedprint lookup path when reporting -ENOENT to user-space
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
100%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
With the advent of 0.55, some users mentioned that the error message is not helpful when the keyring file is not found.
Apparently the error message is pretty much a 'foo: no such file or directory' or similar, and it would be helpful to output the path in which the file was looked up on -- it would at the very least save time while trying to trace down where that file should be but isn't.
Actions