Launcher activates wrong application

Bug Reports
, ,
1

REPRODUCIBILITY: 50% (sometimes)
OSVERSION: 5.2.0.13
HARDWARE: Jolla Phone (2026) - jp2601 - jp2601 - 1.0.0.10 - aarch64
UI LANGUAGE: English (UK) (user: en_GB, os: en_GB.utf8)
REGRESSION: yes (since: 5.1.0.11 - aarch64)

DESCRIPTION:

When launching an app another is put to the foreground, and the launched app does not open.

This does not happen all the time (hence 50% reproducibility).

PRECONDITIONS:

It appears to only happen with “Pure QML” applications, i.e. those using sailfish-qml (or more generally a “wrapper” binary).

STEPS TO REPRODUCE:

  1. Have a sailfish-qml launched app running
  2. Tap an icon of another sailfish-qml app

I can reproduce with “harbour-sfos-forum-viewer” running, and tapping either of these (list updated as I discover more):

  • harbour-maelstrom
  • harbour-lonewolf
  • harbour-automagic

Those seem to have in common that the Exec= key uses sailfish-qml appname without path.

EXPECTED RESULTS:

Tapped application should launch

ACTUAL RESULTS:

It does not, another, running app goes into foreground.

ADDONS:

  • AAS Bluetooth Bridge: yes

MODIFICATIONS:

  • Patchmanager: yes
  • OpenRepos: yes
  • Chum: yes
  • Other: Using Partnerspace

ADDITIONAL INFORMATION:

Device Owner User: nemo
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.18+git1
9 Likes
2

That’s interesting, sounds like Launcher opens wrong app , but not for Android apps

2 Likes
3

And this [4.0.1.45] Launching QML-only app fails, other app is focused (solved)

I could not immediately reproduce though.

2 Likes
4

Oh, amazingly similar, yes! :slight_smile:

@jovirkku do you remember what the reason/fix was?

Tagging @tomin as well, you seem to have done changes on mapplauncherd mostly.

2 Likes
5

This sounds like a lipstick bug to me.

I’m enjoying a bit of summer this week but @pvuorela would know who to ask.

8 Likes
6

If you need only two qml-only apps you can edit second app’s .desktop file to use qmlscene instead (replace ‘sailfish-qml appname’ with 'qmlscene /usr/share/{appname}/qml/{appname}.qml), but qmlscene suffers from the same issue if you try to launch more than one app this way, weirdly enough launching from terminal works fine, but yeah annoying af

7

I have same issue if i have open 2-3 jolla apps it keeps opening the last opend app not selected app

8

I’m on vacation mode as well, but indeed sounds like lipstick getting confused on same executable. I’ll make a note to check later.

5 Likes
9

I have something similar on Jolla2. It happens with certain apps. Example: I visit NedNieuws, a Dutch nieuws app for Sailfish. After swiping away NedNieuws from bottom to top as usual, I want to visit the Sailfish Forum app, but I am brought to the NedNieuws app again. The forum app does appear in the launch screen, but the wheel keeps turning. The same with Guardfish and vice versa with all three.

10

Did someone check what’s in the corresponding .desktop files in the line beginning with Exec= of the affected apps?
in /usr/share/applications/ ?

11

Definitely sailfish-qml!

1 Like
12

Thanks @nephros for filing this bug report. I was about to file one of the same issue as well. For me the app launcher behaves totally off only for a few native apps when they are opened:

  1. trying to open Hafenschau app while SFOS-Forum is open results in opening SFOS-Forum again.
  2. trying to open gPodder app while SFOS-Forum is open results in opening SFOS-Forum again.
  3. trying to open SFOS-Forum while Hafenschau app is open results in opening Hafenschau app again.
  4. trying to open Hafenschau app while gPodder is open results in opening gPodder again.
  5. trying to open Audiothek app while gPodder is open results in opening gPodder again and vise versa
  6. Some apps don’t open at all: MeeCast,… but this could be an issue with MeeCast issue (latest Chum version) and not being compatible with.

I’m also at holiday-mode with limited internet con., so didn’t have time to install a lot but most important ones for me.

1 Like
13

Checked the mentioned apps, and yes all of them have a similar Exec= line.

14

When checking defaults with SDK app creation the app loading is done without path:

[Desktop Entry]

Type=Application

X-Nemo-Application-Type=silica-qt5

Icon=untitled2

Exec=sailfish-qml untitled2

Name=untitled2

# translation example:

# your app name in German locale (de)

#

# Remember to comment out the following line, if you do not want to use

# a different app name in German locale (de).

Name[de]=untitled2
15

It’s totally fine this way. Harbour Validator even demands it I think.

It’s a bug in the current sailfish somewhere, the apps are innocent.

1 Like
16

I experience this behaviour with the following apps:

  • SFOS Forum Viewer
  • GPodder
  • Audiothek
  • Tidal Player
  • German Weather

When starting one of these Apps while another one of these Apps is already open, the second startet App does not open. Instead the already running App opens and the home screen widget of the App, i wantet to start, shows a spinning circle for some time, than it crashes. So everyone of these Apps can basically be started, but they can not be simultaniously kept on the homescreen.

17

Same with :

  • Imageworks
  • Storeman (maybe)