Strictly confined snapped desktop applications can't toggle Launch at Login
Bug #1665683 reported by
Martin Wimpress
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
I'm talking to a couple of ISVs with closed source communication and collaboration applications. Each features an option in the UI to "Launch at Login".
When strictly confined this writes the autostart file to ~/snap/
| Changed in snappy: | |
| assignee: | nobody → Martin Wimpress (flexiondotorg) |
| status: | New → In Progress |
| tags: | added: isv |
| summary: |
- Strictly confined desktop applications snaps can't toggle Launch at + Strictly confined snapped desktop applications can't toggle Launch at Login |
| Changed in snappy: | |
| assignee: | Martin Wimpress (flexiondotorg) → nobody |
| status: | In Progress → New |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| affects: | snappy → snapd |
| Changed in snapd: | |
| status: | New → Fix Released |
To post a comment you must log in.
This has been implemented for a long time now. For reference it is the "autostart" part of https:/