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

Unstarring consistently fails on Qubes #173

Closed
eloquence opened this issue Nov 15, 2018 · 4 comments
Closed

Unstarring consistently fails on Qubes #173

eloquence opened this issue Nov 15, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@eloquence
Copy link
Member

Note: I'm not able to reproduce this issue in the Docker development environment on current master, only in a Qubes environment built from the securedrop-workstation repo as of today. So, this may no longer be valid, but filing in case it's a Qubes-specific issue.

Steps to reproduce:

  1. Sign in to a SecureDrop instance that has some submissions.
  2. Star a submission.
  3. Once it is starred, unstar the submission.

Expected behavior:

Submission is unstarred.

Actual behavior:

Unstarring fails with "Failed to apply change"

@eloquence eloquence added the bug Something isn't working label Nov 15, 2018
@zenmonkeykstop
Copy link
Contributor

zenmonkeykstop commented Nov 15, 2018

Confirmed for me on current master in Qubes.

@redshiftzero redshiftzero self-assigned this Nov 15, 2018
@redshiftzero
Copy link
Contributor

yep this appears to be Qubes only

@redshiftzero
Copy link
Contributor

note that logs are in ~/.securedrop_client/logs/*.log in sd-svs (fishing out the relevant log lines helps with repro)

@redshiftzero
Copy link
Contributor

since freedomofpress/securedrop#3977 was resolved, this is also resolved on staging instances provisioned on develop

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

3 participants