You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I inserted a drive not provisioned for the workstation, I receive no error-message or other feedback within the UI to tell me that what I've done will not work. I do however, get a flood of "Something is happening, but what?" toast messages—which adds to the confusion.
Drive was a removable SSD USB drive, but not a thumb-drive
I suspect the Mac encryption or Mac formatting (APFS or HFS+) on a thumb drive to be a more common issue, than encryption to other FOSS standards or non-proprietary linux drive formats, as journalists appear to largely be Mac dominant users.
The text was updated successfully, but these errors were encountered:
Changed labeling and text above, to make this a bug—as I found what I'd thought I'd seen in #666. Much as I'd like to change how errors are presented, uniformly, across the Export and Print experiences... the intended functionality from the 666 PR would be awesome for Beta. :D
When I inserted a drive not provisioned for the workstation, I receive no error-message or other feedback within the UI to tell me that what I've done will not work. I do however, get a flood of "Something is happening, but what?" toast messages—which adds to the confusion.
I tested this today and when I insert a non-luks encrypted thumb drive I saw:
I will have to look into APFS and HFS+ to test the bug you found.
sssoleileraaa
changed the title
Incorrect drive does not prompt error on export
APFS or HFS+ forrmatted drives don't show an error when exporting
Mar 24, 2020
Problem
When I inserted a drive not provisioned for the workstation, I receive no error-message or other feedback within the UI to tell me that what I've done will not work. I do however, get a flood of "Something is happening, but what?" toast messages—which adds to the confusion.
What I expected
From Allie's #666 PR...
Conditions
The text was updated successfully, but these errors were encountered: