I was affected by this too, but I’m not using encryption:

# sudo -u www-data php occ encryption:status
  - enabled: false
  - defaultModule: OC_DEFAULT_MODULE

The server log just showed ServerNotAvailableException:"Could not decrypt key" for any connection attempts after 19->20 upgrade.

I have another instance where I am using encryption, and there I was able to log in just fine. I did some diffing and found the working installation (with encryption enabled) had 'encryption.legacy_format_support' => true,, while the non-working installation (with encryption disabled) didn’t. Adding that to my config.php alone didn’t fix the issue, so I also added 'encryption.key_storage_migrated' => false, and after that I was able to log in again.

According to documentation, starting with version 20 the legacy encryption is off by default. occ encryption:scan:legacy-format is supposed to tell whether you can disable the compatibility mode, but for the instance without encryption it seems to produce a false positive (complete with a typo):

All scanned files are propperly encrypted. You can disable the legacy compatibility mode.

For the admin user, the now otherwise working, unencrypted instance also shows a ”Please enable server side encryption in the admin settings in order to use the encryption module” notification in the web UI, for every page load (i.e. even after dismissal it just pops back up whenever I navigate in the UI).

The errors reported by app:check-code encryption are probably unrelated, as the same errors are reported for both my instances.

The version I’m using:

yle-dl 20200807 with wget 1.20.3 (in Ubuntu 20.04)

Steps to reproduce:

$ /usr/local/bin/yle-dl -qq --backend wget --wget /usr/bin/wget https://areena.yle.fi/1-50636796

What I expect to happen:

For the download to complete without any output in the terminal.

What happens instead:

The command outputs this line (which to me seems like is from wget):

2020-09-25 17:25:27 URL:https://ylekaod-a.akamaihd.net/s/p/1955031/sp/195503100/serveFlavor/entryId/1_ldivkmki/v/11/ev/2/flavorId/1_b6wtzy8f/name/a.mp3?__hdnea__=st=1601043921~exp=1601058321~acl=/s/p/1955031/sp/195503100/serveFlavor/entryId/1_ldivkmki/v/11/ev/2/flavorId/1_b6wtzy8f/name/a.mp3*~hmac=bddcd801a98d3560990842beccee528da3861e588cf3438880642267aab03dc4 [21436961/21436961] -> "Kaverin puolesta kyselen: Koppuraiset kalsarit ja muita deittimokia-2020-09-25T06:45.mp3" [1]

This is still an issue; a newer (and still open, as of writing this) issue number for reference: #4312

Sure, that sounds doable. 👍

I’m up for testing those packages. Would Github allow you to attach a deb to a comment here (perhaps wrapped in a Zip file)?

Yup, it’s working now, thanks @ivaradi! Installed the -dbgsym packages and reproduced the segfault, here’s the gist.

(TBH, I’m just cargo culting from the wiki here, so I have no idea if this result is useful, but I do have a fairly solid way of triggering the issue, so just let me know if I should do something differently.)

I tried enabling the main/debug component for the PPA, but it just results in a bunch of ”repository […] doesn’t have the component ’main/debug'” errors when I run apt update. Should I open a separate issue about it?

This hasn’t manifested itself in ages anymore, so it’s probably fixed.

Summary

Mobile devices receive ”ghost” notifications for already read messages, when set to receive notifications ”when Away or offline”, and receiving user is set to be Away.

Steps to reproduce

1. Set ”Mobile Push Notifications” to ”Trigger push notifications when”: ”Away or offline” (and send ”For all activity”)
2. Using web interface on desktop, set your status to Away
3. (Still in the web interface) receive a message in the currently open channel (which immediately marks it read)

Expected behavior

Nothing happens on the mobile device (no notification).

Observed behavior (that appears unintentional)

The mobile device receives a notification about the already read message. The notification immediately disappears. If you weren’t looking at the device, you’re left wondering why it alerted you.

Other info

If your status is set to Online instead of Away (at step 2), the mobile device receives no notification (as expected). If ”Trigger push notifications when” is set to ”Online, away or offline” (at step 1), the mobile device receives no notification irrespective of your Online/Away status (also as expected).

Environment Information

I’m self-hosting Mattermost 5.26.1 with self-hosted MMPNS 5.22.4. Mattermost Mobile is at version 1.34.0. My mobile devices have Android 10 (Samsung) and Android 7.1.2 (LineageOS 14.1).

I don’t know if this is an issue with the client or the server; I can re-report against the latter if appropriate.

Updated client to 3.0.1 and the issue persists.