[Changelog] Tampella 5.0.0

Announcements
#1

This post contains the detailed changelog entries of Sailfish OS update 5.0.

Changelog_from_5.0.0.5_to_5.0.0.21.md (47.0 KB)

  • This document covers the changes from the Jolla C2 factory release 5.0.0.5 to the 1st public release 5.0.0.21. Update 5.0.0.21 is targeted for the Jolla C2 community phone only.

Changelog_from_5.0.0.21_to_5.0.0.29.md (10.1 KB)

  • Rolled out for C2 only.

Changelog_from_5.0.0.29_to_5.0.0.43.md (16.2 KB)

  • Rolled out for C2 only.

Changelog_from_4.6.0.15_to_5.0.0.55.md (296.3 KB)

  • Sailfish OS 5.0.0.55 rolled out to all supported devices. Early Access.

Changelog_from_5.0.0.55_to_5.0.0.61.md (7.5 KB)

  • Sailfish OS 5.0.0.61 rolled out to all supported devices. Early Access.

The release notes are here:

11 Likes
[Release notes] Tampella 5.0.0.43 for Jolla C2
[Release notes] Tampella 5.0.0.21 for Jolla C2
[Release notes] Tampella 5.0.0.55
[Release notes] Tampella 5.0.0.29 for Jolla C2
[Release notes] Tampella 5.0.0.61
#2

No markdown in the docs app ;_;

#3

Please make a more verbose comment. Should something be fixed and how?

#4

I think he is reffering to the fact that an md file cannot be opened on SailfishOS directly. A possibility could be to add support to the Documents app.

Workaround:
While the downloaded md file has content disposition:attachment, once downloaded you can point your browser to file:///home/defaultuser/Downloads and you can use the browser to read it

4 Likes
#5

Which means you can use the browser to then save a PDF which you can read in sailfish-office/Documents. :wink:

6 Likes
#6

would still be nice to be able to save the file if you receive it as email attachment. Actually it would be nice to be able to save ANY file you receive as email attachment

2 Likes
#7

I agree, it like impossible to cover all possible use cases and how people are supposedly using their downloaded files. Hence, better would be allow downloading any email attachment.

4 Likes
#8

In 5.0.0, maybe already 4.6.0, the email attachments are saved in ~/Downloads when tapped on, no matter if there is something to open it or not.

3 Likes
#9

Md documents rendering is not supported it seems.

#10

Downloading email attachments has been possible for me? :thinking:

#11

I just tried, in 4.6 I definitely can’t download attachments with unsupported extensions. But nice that my wish is already fulfilled in 5 - just have to wait a bit

#12

I noticed that Slovenian languge was not updated again.
It seems that the last update for l10n of 5 was not imported.

1 Like
[Release notes] Tampella 5.0.0.43 for Jolla C2
#13

Pull requests welcome :slight_smile:

3 Likes
#14

Ok, so it will come when 5.0.0 will be out.

It’s still not very intuitive. For attachments that don’t have any application to use them, there is still the message that the file cannot be opened. It is saved though. I wanted to change this notification message to display that there is nothing to open the file, but that it is saved anyway, but this notification is not handled by the email application. It is triggered by the QML call openExternally() (or something like that). This call is returning a boolean, but the documentation explain that this boolean just means that the call has been succesfully sent to xdg-open or something equivalent. Not that xdg-open can actually open the file or not.

So not very easy to discover…

1 Like
#15

For markdown there is Notizen.md app (in openrepos) but don’t have support for opening markdown file from another app.

2 Likes
#16

@jovirkku, AFAICS the changelog from SailfishOS 4.6.0.15 to 5.0.0.5 is missing, correct?

I am asking, because I try to retrace changes to the package sailfish-secrets, due to a bug which seems to only occur on SailfishOS 5.0.0. But in the extant changelogs for SailfishOS 5.0.0 above, no such change is documented, although there are changes documented in Changelog_from_5.0.0.5_to_5.0.0.21.md for the packages sailfish-secrets-l10n (1.54 → 1.56.1) and sailfish-secrets-ui-l10n (1.53 → 1.53.2), from which one might conclude that there must be corresponding changes to the non-l10n (i.e. non-i18n) packages sailfish-secrets and sailfish-secrets-ui.

Questions:

  1. Is it correct to assume that the package sailfish-secrets was updated from v1.54 to v1.56.1 and sailfish-secrets-ui from v1.53 to v1.53.2 between SailfishOS 4.6.0.15 to 5.0.0.21?
    These are the changes of sailfish-secrets from 0.2.38 to 0.2.41, i.e. between SailfishOS 4.6.0 to 5.0.0.
  2. Is the assumption correct, that aforementioned changes happened between SailfishOS 5.0.0.5 and 5.0.0.21 and are simply missing in the corresponding changelog?
    Likely rather happened between SailfishOS 4.6.0.15 and 5.0.0.5, correct?
  3. Is there a way to obtain some details of the changes for sailfish-secrets from v1.54 to v1.56.1 and sailfish-secrets-ui from v1.53 to v1.53.2?
    Again: These are the changes of sailfish-secrets from 0.2.38 to 0.2.41, i.e. between SailfishOS 4.6.0 to 5.0.0.
    IIRC these packages are proprietary software, so supposedly a changelog provided by Jolla is the only place where such changes would be publicly documented, right?
  4. Will the accumulated changes from SailfishOS 4.6.0.15 to 5.0.0.x be properly documented when SailfishOS 5 is released for Sony Xperias?
    Well, actually this fourth point is less a real question than asking, “please do provide all accumulated changes from SailfishOS 4.6.0.15 to 5.0.0.x, then”.

Thank you & cheers!

2 Likes
#17

While waiting for the complete changelog, I can answer some of your questions:

Is it correct to assume that the package sailfish-secrets was updated from v1.54 to v1.56.1 and sailfish-secrets-ui from v1.53 to v1.53.2 between SailfishOS 4.6.0.15 to 5.0.0.21?

No, foo-l10n packages are independant from foo packages and follow a different versioning.

Is there a way to obtain some details of the changes for sailfish-secrets from v1.54 to v1.56.1 and sailfish-secrets-ui from v1.53 to v1.53.2? IIRC these packages are proprietary software

sailfish-secrets is free software. In the upgrade from Sailfish OS 4.6 to 5.0, the tags were moved from 0.2.38 to 0.2.41. The three commits correspond to fix for compilation issues with GCC 11 and warning for deprecated OpenSSL functions.

About sailfish-secrets-ui, it’s indeed proprietary, but I think the version didn’t change from 4.6 to 5.0.

For the bug you mentioned, maybe running the secret daemon in debug mode may help to see what is going wrong ?

systemctl --user stop sailfish-secretsd
QT_LOGGING_RULES="*.debug=true" devel-su -p /usr/bin/sailfishsecretsd
3 Likes
#18

Thank you very much for the comprehensive clarifications! While these helped me to overcome my misconceptions, indeed the changes of sailfish-secrets from 0.2.38 to 0.2.41 do not appear to be even loosely related to the bug experienced by its reporters (@BohdanKoles and @eson).

For the bug you mentioned, maybe running the secret daemon in debug mode may help to see what is going wrong?

This advice is much appreciated; I will try to get it across to the reporters to try on their Jolla C2 devices.
AFAIU the whole sequence would be (correct?):

devel-su
systemctl --user stop sailfish-secretsd
export QT_LOGGING_RULES="*.debug=true"
devel-su -p /usr/bin/sailfishsecretsd
# Why not: systemctl --user start sailfish-secretsd
journalctl -lf
# Then start Storeman by clicking on its desktop icon.
3 Likes
#19

Enable multi-threaded build also for rust.

Remind me to check how this is done, in the context of Building cargo / rust software on community OBS - #5 by vlagged

#20

@jovirkku, the last bullet point currently (as of 2025-02-21) reads:

You may want to change it to …

- [[Release notes] Tampella 5.0.0.61](https://forum.sailfishos.org/t/22224) (all products)?

… so it is rendered as: