Tails

#2 Updated by sajolida 2018-05-05 15:58:11

• Description updated

#3 Updated by sajolida 2018-05-05 16:02:30

• Subject changed from No feedback when opening desktop launchers (especially documentation) to No feedback when opening an application

I’m making the scope of this ticket broader because there is not feedback either when opening an app from the Applications menu.

#4 Updated by emmapeel 2018-05-07 07:19:10

• related to Bug #15528: Additional Software gets opened multiple times added

#5 Updated by sajolida 2018-05-31 18:44:37

• Subject changed from No feedback when opening an application to No feedback when opening some applications
• Description updated
• Assignee changed from cbrownstein to intrigeri
• QA Check set to Info Needed
• Type of work changed from Test to Research

I followed up on this on the GNOME bug tracker. While doing more tests I realized that some applications provide feedback while some other don’t. See the video on https://gitlab.gnome.org/GNOME/mutter/issues/166.

intrigeri: Can you have a look at https://gitlab.gnome.org/GNOME/mutter/issues/166#note_174996 and tell me:

• If I should close the upstream GNOME bug
• What it would take to fix the launching of some of our applications. For example, the Tails documentation launcher on the desktop or the opening of Additional Software from the persistence settings.

#6 Updated by intrigeri 2018-06-02 09:31:20

• Assignee changed from intrigeri to sajolida
• QA Check changed from Info Needed to Dev Needed

> * If I should close the upstream GNOME bug

Yes, this does not seem to be a bug in GNOME.

> * What it would take to fix the launching of some of our applications. For example, the Tails documentation launcher on the desktop or the opening of Additional Software from the persistence settings.

I’m no expert in this field but I think it may depend on the application. In many cases adding a (correct) StartupWMClass= field in the .desktop file should be enough (examples; I bet the two examples you’re providing fall into this category. To test this, use xprop to get the WM_CLASS of the main app window, set StartupWMClass= in the .desktop file to this value, and retry launching the app from the launcher.

In some rarer cases some coding may be needed.

#7 Updated by sajolida 2018-06-03 16:37:09

• related to Feature #14544: Spend software developer time on smallish UX improvements added

#8 Updated by sajolida 2018-06-03 16:37:22

• Subject changed from No feedback when opening some applications to Add feedback when opening desktop launchers
• Assignee deleted (sajolida)
• QA Check deleted (Dev Needed)
• Type of work changed from Research to Code

Thanks for the additional information!

Here is what I tried:

• Edit ~/Desktop/tails-documentation.desktop
• Changed Exec= to localc
• Added StartupWMClass=libreoffice-calc as per the examples in codesearch.debian.org and the info I get from xprop

But I still get no spinner when clicking on “Tails documentation” on the desktop (unlike when I click “Home” or “Trash” on the desktop).

I don’t want to dive into this deeper myself but I’m renaming this ticket to narrow its scope.

#10 Updated by intrigeri 2018-07-06 08:37:22

• Assignee set to sajolida
• QA Check set to Info Needed

I felt the need to fix the startup notification for Tor Browser while working on Feature #15023 (I believed it was a regression, and then noticed that even on Tails 3.8 there’s no feedback when starting the browser, oh my) and while I was at it I’ve fixed it for the desktop launchers too. Now I’m not sure how to update the metadata here: I’m confused by the repeated changes of scope of this ticket. Is is on purpose that it’s currently only about the desktop launchers?

#11 Updated by intrigeri 2018-07-06 08:40:21

• Status changed from Confirmed to In Progress

#12 Updated by sajolida 2018-07-17 16:51:53

• Assignee changed from sajolida to intrigeri

Yeap. Let’s say that this ticket is only about the desktop launchers.

I created Bug #15738 to test the stuff we have in the Applications menu.

#13 Updated by intrigeri 2018-07-28 05:07:19

• related to Bug #15738: Test feedback when opening applications from the Applications menu added

#14 Updated by intrigeri 2018-07-28 05:08:03

• Description updated

#15 Updated by intrigeri 2018-07-28 05:09:38

• Status changed from In Progress to Resolved
• Assignee deleted (intrigeri)
• Target version set to Tails_3.9
• % Done changed from 0 to 100
• Parent task changed from Feature #14548 to Feature #15023
• QA Check deleted (Info Needed)

#16 Updated by intrigeri 2018-07-28 05:09:53

• blocks Feature #14548: Fix issues identified in the expert review done by jaster on our installation instructions added

#17 Updated by intrigeri 2018-07-28 05:10:27

• Description updated

#18 Updated by intrigeri 2018-07-28 05:19:41

• blocked by deleted (Feature #14548: Fix issues identified in the expert review done by jaster on our installation instructions)

#19 Updated by intrigeri 2018-07-28 05:20:08

• Status changed from Resolved to In Progress
• Assignee set to intrigeri
• Parent task changed from Feature #15023 to Feature #14548
• QA Check set to Pass

#20 Updated by intrigeri 2018-07-28 05:20:24

• blocked by Feature #15023: Upgrade to Tor Browser based on Firefox ESR60 added

#21 Updated by Anonymous 2018-08-07 13:58:29

• related to Feature #15546: Feedback needed when clicking on Persistence wizard → configure ASP gear button added

#22 Updated by intrigeri 2018-08-14 06:02:57

• Status changed from In Progress to Fix committed
• Assignee deleted (intrigeri)
• Feature Branch set to feature/15023-tor-browser-8

#23 Updated by intrigeri 2018-09-05 16:22:04

• Status changed from Fix committed to Resolved

#24 Updated by intrigeri 2019-08-30 18:17:22

• related to Feature #15855: Notify that Tor Browser is Starting added