Skip to content
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

Dialog displays a system error (possibly export-related) #1368

Open
gonzalo-bulnes opened this issue Dec 6, 2021 · 5 comments
Open

Dialog displays a system error (possibly export-related) #1368

gonzalo-bulnes opened this issue Dec 6, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@gonzalo-bulnes
Copy link
Contributor

gonzalo-bulnes commented Dec 6, 2021

Observed

An sd-app dialog seems to display a system error.

qfile-unpacker: Fatal error: Cannot umount incoming directory (error type: invalid argument)

Reported by @ninavizz
May be related to #554

Expected

No errors are directly displayed to the user, instead they're handled and copy is adjusted for end-user audiences.

Steps to reproduce

Unclear

@gonzalo-bulnes gonzalo-bulnes added bug Something isn't working needs/reproducing labels Dec 6, 2021
@eloquence eloquence changed the title Dialog displays a system error Dialog displays a system error (possibly export-related) Dec 8, 2021
@eloquence
Copy link
Member

eloquence commented Dec 8, 2021

Per @conorsch

that error can occur if qvm-copy is used simultaneously with the same target VM.

It shouldn't be possible to kick off an export operation when one is in flight due to the modal dialog. @ninavizz speculated that she may have removed a USB drive prematurely.

@ninavizz
Copy link
Member

ninavizz commented Dec 8, 2021

@eloquence I was taking screenshots and transferring screenshots, while doing export things. Could that perhaps have been a part of it, or are you thinking just qvm-copy to the export vm?

@eloquence
Copy link
Member

If you ran multiple inter-VM copy operations manually for the screenshots, that could very well have been the cause.

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Dec 9, 2021

some more details from @conorsch (just to contribute some more context to what @eloquence wrote in #1368 (comment))

that error can occur if qvm-copy is used simultaneously with the same target VM. based on the screenshot, the src files were named differently, but the target VM was the same. if the src files were also named the same, then there'd be an additional error message. screenshot to illustrate STR
qvm-copy-only-serially

@eloquence
Copy link
Member

I just encountered this issue twice during QA of freedomofpress/securedrop-workstation#751. Specifically, what I did is:

  1. Initialize a fresh .securedrop_client directory with only the config.json containing the submission key fingerprint
  2. Launch the client in offline mode
  3. From there, log in and wait for it to sync
  4. While it's syncing (specifically downloading replies), tried to download some files

During this, I encountered the error twice. After the sync finished, I could no longer reproduce the error.

This might suggest some concurrency issues between downloads and syncs.

To be clear, I have no evidence that this is a recent regression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants