3 ms·
The first issue was fixed and just closed, and seems like it was very difficult to track down.
by bakoo 5y ago
The first issue was fixed and just closed, and seems like it was very difficult to track down.
- FabHK 5y agoIt was closed 4 minutes ago; when was it fixed? ETA: Ah, 4 days ago (more than half a year after it was opened).
- johnchristopher 5y agoIt's fixed in 5.17 and this is the release number I see on the Google playstore. Unfortunately for my ubuntu 18.04 LTS and this is in no way Signal's fault (but maybe the desktop version doesn't have that bug ?): $ apt-cache policy signal-desktop signal-desktop: Installé : 5.10.0 Candidat : 5.10.0 Table de version : *** 5.10.0 500 500 https://updates.signal.org/desktop/apt xenial/main amd64 Packages 100 /var/lib/dpkg/status 5.9.0 500 500 https://updates.signal.org/desktop/apt xenial/main amd64 Packages 5.8.0 500 500 https://updates.signal.org/desktop/apt xenial/main amd64 Packages
- maqp 5y agoWould rolling into the beta help here? https://support.signal.org/hc/en-us/articles/360007318471-Signal-Beta https://support.signal.org/hc/en-us/articles/360007318471-Si...
- johnchristopher 5y agoI don't think so: $ apt-cache policy signal-desktop-beta signal-desktop-beta: Installé : (aucun) Candidat : 5.11.0-beta.1 Table de version : 5.11.0-beta.1 500 500 https://updates.signal.org/desktop/apt xenial/main amd64 Packages