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

sdw-login should probably be started by a systemd unit instead of autostart entry #1073

Open
1 task done
legoktm opened this issue Jun 6, 2024 · 1 comment · May be fixed by #1086
Open
1 task done

sdw-login should probably be started by a systemd unit instead of autostart entry #1073

legoktm opened this issue Jun 6, 2024 · 1 comment · May be fixed by #1086
Assignees

Comments

@legoktm
Copy link
Member

legoktm commented Jun 6, 2024

  • I have searched for duplicates or related issues

Description

sdw-login is currently started by an autostart entry:

dom0-login-autostart-desktop-file:
file.managed:
- name: /home/{{ gui_user }}/.config/autostart/press.freedom.SecureDropUpdater.desktop
- source: "salt://securedrop_salt/dom0-xfce-desktop-file.j2"
- template: jinja
- context:
desktop_name: SDWLogin
desktop_comment: Updates SecureDrop Workstation DispVMs at login
desktop_exec: /usr/bin/sdw-login
- user: {{ gui_user }}
- group: {{ gui_user }}
- mode: 664
- require:
- file: dom0-login-autostart-directory

so it has a hardcoded sleep to make sure the desktop is set up properly:

if __name__ == "__main__":
# Wait for the dom0 GUI widgets to load
# If we don't wait, a "Houston, we have a problem..." message is displayed
# to the user.
time.sleep(5)

probably it should be a systemd unit that triggers on login, with the necessary Requires/After stanzas instead of a sleep

@rocodes rocodes self-assigned this Jun 17, 2024
@rocodes
Copy link
Contributor

rocodes commented Jun 17, 2024

@rocodes rocodes linked a pull request Jun 17, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants