Feedback needed when clicking on Persistence wizard → configure ASP gear button
When clicking on the configuration button on the Additional software section of the Persistence wizard, nothing happens for a while.
I clicked several times on it, and the menu opened several times too.
While fixing Bug #15528 could also make this experience a little better, I think it would be good to have also a ‘spinner’ while you wait for the configuration window to open.
|Related to Tails - Bug #15528: Additional Software gets opened multiple times||Confirmed||2018-04-12|
Related to Tails -
|Related to Tails - Feature #15827: Give feedback while the persistence setup is starting||Confirmed||2018-08-21|
#6 Updated by alant 2018-07-30 22:51:08
- Assignee changed from alant to intrigeri
- QA Check changed from Ready for QA to Dev Needed
> If there’s correct feedback when starting the same app via other means (e.g. apps menu) then it’s a tps bug.
I fixed the
.desktop file, there is now good feedback from the Applications menu, but not from Persistence Setup.
#7 Updated by intrigeri 2018-08-01 02:51:46
- % Done changed from 10 to 0
I’ll give it a try but we’ve decided this was not a blocker we’re supposed to submit the entire branch for review in a few days, and I was not supposed to be available for this work right now. So to be clear, don’t count on this being fixed in 3.9 (or ever).
#13 Updated by intrigeri 2018-08-10 13:52:46
> Ack. Let’s see if you find time,
Yep! I’m taking a look as we speak.
> otherwise postpone and/or reassign to Alan?
I’d rather say: otherwise forget it (possibly low prio / starter ticket, more realistically reject). This is not a sponsor deliverable. And I doubt Alan will want to touch Perl code.
#14 Updated by intrigeri 2018-08-10 16:19:38
- Subject changed from Feedback needed when clicking on Persistence wizard - gears button to Feedback needed when clicking on Persistence wizard → configure ASP gear button
- Assignee deleted (
- Target version deleted (
I think this problem comes from running t-p-s as a dedicated user with sudo. So first of all I wanted to check whether t-p-s itself was able to signal its startup / GNOME Shell was able to notice it: if that does not work, there’s little chance that it’ll work for another app started from t-p-s. I’ve added these lines:
/usr/share/applications/tails-persistence-setup.desktop and I see a spinner but the mouse cursor is not restored when t-p-s has started (it is restored only after a timeout), which is why — I think — I’ve set
StartupNotify=false in that file in the first place.
I can reproduce this when starting the Unsafe Browser, which is started in a similar manner as t-p-s.
I think this will be fixed for free when we port all our apps run via sudo to run as the amnesia user (with a privileged backend if needed) which we’ll need to do for Wayland. So I’ll mark this as blocked by the move to Wayland and will put this on the back burner for now.