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

Segfault when runing without sdc-client home dir option #304

Closed
sssoleileraaa opened this issue Apr 12, 2019 · 3 comments · Fixed by #305
Closed

Segfault when runing without sdc-client home dir option #304

sssoleileraaa opened this issue Apr 12, 2019 · 3 comments · Fixed by #305
Assignees
Labels
bug Something isn't working

Comments

@sssoleileraaa
Copy link
Contributor

Description

Segfault happens when you run the client with no sdc-home option.

Logs (not much to go on)

./run.sh: line 44: 21070 Segmentation fault      exec python -m securedrop_client --sdc-home "$SDC_HOME" --no-proxy $@

More info

This looks like the same upstream bug that we came up with a workaround for. This might have been re-introduced when moving CSS from instance to class variables. See #273 for more info.

@sssoleileraaa sssoleileraaa added the bug Something isn't working label Apr 12, 2019
@sssoleileraaa sssoleileraaa self-assigned this Apr 12, 2019
@redshiftzero
Copy link
Contributor

I can't reproduce this on latest master (8f69f01), my STR are just to execute ./run.sh - do I need to login or take another action?

@sssoleileraaa
Copy link
Contributor Author

Ah, sorry. Forgot the STR...

STR

  1. ./run.sh
  2. select a source

Do the same with the sdc-home option (this is how I normally test as I develop but will start testing both situations to catch bugs like this sooner) and see it not segfault

@redshiftzero
Copy link
Contributor

ahh gotcha, I can indeed reproduce this on master with Qt 5.12.1

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

Successfully merging a pull request may close this issue.

2 participants