[BUG] Unable to start Camera/Email/Browser after OS update to 4.3.0 with patchmanager 3.1.0

[b100dian]

(From @branja6 on Telegram)

SailfishOS VERSION (Settings → About product → Build): 4.3.0.12 EA
HARDWARE (Settings → About product → Manufacturer & Product name):
PATCHMANAGER VERSION (Settings → Patchmanager → [Top pulley] About): 3.1.0

BUG DESCRIPTION

Updating from SFOS 4.2.0 to SFOS 4.3.0 then PM 3.1.0 to PM 3.1.1 with the following patches enabled makes Email/Browser/Camera not start anymore.

Unapplying all patches solves this.

STEPS TO REPRODUCE

Apply the above three patches on SFOS 4.2.0 with PM 3.1.0 Upgrade to SFOS 4.3.0 Upgrade to PM 3.1.1 Launch Email -

ADDITIONAL INFORMATION

The day of the upgrade PM 3.1.1 was released and updated.

After Unapply all patches and re-applying them - all good

[Olf0]

Sounds really strange to me, even more "After Unapply all patches and re-applying them - all good". Camera app not starting is something a couple of people report for SFOS 4.3.0.12 at FSO. The issue with this issue is: "all good" now, no logs, hence nothing to analyse.

[branja6]

patchmanager.log

Here's the log. I hope it helps. If there's anything else you'd like me to do, just give me a shout on Telegram.

[b100dian]

I think for now we can all see if we can reproduce this after upgrading to 4.3.0 when is out of EA. I haven't had issues with Xperia 10 and 4.3.0 EA, but there are at least two more devices by @Olf0 or @nephros that could encounter the bug. Of course we can close it in the mean while, since the problem is itself solved for @branja6

[Olf0]

I think for now we can all see if we can reproduce this after upgrading to 4.3.0 when is out of EA. I haven't had issues with Xperia 10 and 4.3.0 EA, but there are at least two more devices by @Olf0 or @nephros that could encounter the bug.

Do not expect me to upgrade soon, even when SFOS 4.3.0 is out of EA.

Of course we can close it in the mean while, since the problem is itself solved for @branja6

I would rather leave it open for a while (some weeks), because it is easier to find for others who may encounter similar issues. But "Yes", if no other reports show up, I think we should close it without further ado.

[nephros]

@branja6 Can you tell us which version of PM you had installed before 3.1.1? I seem to remember from your original report on Telegram it was the latest one from Coderus' Openrepos repo, i.e 3.0.65, and not 3.1.0 from our repo?

Because: 3.0.65 did not contain the fix for sandboxed applications, so while patches might have been applied, they never affected those (sandboxed) applications. With 3.1+ they do now.

[branja6]

I've used the latest version from your repo on Openrepo because Coderus doesn't update his apps anymore (I don't even have his repos enabled in Storeman).

[Olf0]

@branja6, @b100dian, @nephros, any new insights? Or did this issue ever re-occur, either to one of you or documented somewhere?

If not, I suggest to remove the label "bug" and to close this issue.

[b100dian]

Let's close this. Feel free to re-open on new info.