Whisperfish - The unofficial SailfishOS Signal client

Applications
#1264

Not at all. In your case, you’re just bouncing on this issue. Before I release that, there’s something else I want in. Shouldn’t take long :slight_smile:

2 Likes
#1265

You can fix it with this

How do I reset Whisperfish to be able to register again?

rm -rf ~/.local/share/harbour-whisperfish ~/.config/harbour-whisperfish ~/.local/share/be.rubdos/harbour-whisperfish ~/.config/be.rubdos/harbour-whisperfish

Frequently Asked Questions · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

1 Like
#1266

Thanks for the response!

I have cleared the folders and checked that the registration lock was off (it was, hadn’t used the official Signal client in a while anyway). I tried registering again, but got the same problem. I did capture the logs now, which you can find here: Whisperfish logs - Pastebin Service
It gives a couple of error messages with regards to local data corruption?

#1267

Should have linked this from the get-go, but you’ll have to enable verbose logging: Home · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

I think this will probably be the same issue as the linking now though, so maybe worth waiting a day or so for the next version.

1 Like
#1268

Okay, thanks, will sit it out!
I’m currently rate limited by the captcha anyway :slight_smile:

1 Like
#1269

I have chosen:

  • Enable read receipts
  • Enable generate link previews
    from my main device, Signal Android.

But those settings won’t transfer to WF. Is it my device only or is this maybe a known bug?
(my device is X10III 5.0.0.55)

Furthermore I have a feeling that WF have disabled those at some point…because I never would’ve disabled those myself…but…take that with a grain of salt, well…because it’s a feeling. Can’t put up a case for it :grin:

#1270

I’m not sure whether we ever tested that.

That… wouldn’t surprise me, could definitely be the case :face_with_peeking_eye:

Feel free to make an issue, especially for the first case!

1 Like
#1271

I start whisperfish on Xperia XA2
Salifish Version OS 4.6
I got whisperfish by curl https://openrepos.net/sites/default/files/packages/1867/harbour-whisperfish-0.6.0.beta_.33-1.aarch64.rpm -o whisperfish.rpm
I install whisperfish zypper install ./whisperfish.rpm
I start whisperfish harbour-whisperfish -v
crreate password ,
secondary device
Scan QR code with signal on iphone
and … got an error pawel.spoon

Did I not notice the solution in the posts or is the problem known?

my log
2025-02-08T10:07:43.056079Z TRACE websocket: libsignal_service::websocket: sending response WebSocketResponseMessage { id: Some(7947292989251378483), status: Some(200), message: Some(“OK”), headers: [], body: None }
2025-02-08T10:07:43.161877Z TRACE websocket: libsignal_service::websocket: decoded WebSocketMessage response msg_type=Response response.status=200 response.message=“OK” response_body_size_bytes=0 response.headers=[“X-Signal-Timestamp:1739009263104”, “Content-Length:0”] response.id=12913645714608438567
2025-02-08T10:07:43.193308Z WARN whisperfish::qtlog: QConnmanEngine: Unable to translate the bearer type of the unknown connection type: “bluetooth”
2025-02-08T10:08:01.618722Z TRACE websocket: libsignal_service::websocket: decoded WebSocketMessage request msg_type=Request request.id=7532595590934367803 request.verb=“PUT” request.path="/v1/message" request_body_size_bytes=535 request.headers=[“X-Signal-Timestamp:1739009281395”]
2025-02-08T10:08:01.618880Z TRACE websocket: libsignal_service::websocket: sending request with body
2025-02-08T10:08:01.621705Z TRACE websocket: libsignal_service::websocket: sending response WebSocketResponseMessage { id: Some(7532595590934367803), status: Some(200), message: Some(“OK”), headers: [], body: None }
2025-02-08T10:08:01.736058Z WARN websocket: libsignal_service::websocket: websocket closed code=1000 reason=“Closed”
2025-02-08T10:08:02.724985Z ERROR libsignal_service::push_service::response: failed to decode HTTP 409 status error=error decoding response body
2025-02-08T10:08:02.729690Z ERROR run: whisperfish::worker::setup: Error in registration: Service error: Unexpected response: HTTP 409
2025-02-08T10:08:02.730889Z DEBUG run: whisperfish::qtlog: qml/harbour-whisperfish-main.qml:421:expression for onClientFailed(): [FATAL] client failed
2025-02-08T10:08:02.769939Z DEBUG run: whisperfish::qtlog: qml/pages/FatalErrorPage.qml:25:onCompleted(): [FATAL] error occurred: Einrichtung des Signalclients fehlgeschlagen
I use rm -rf .local/share/be.rubdos/ .config/be.rubdos/ .cache/be.rubdos/

1 Like
#1272

For me the answer was clear: wait for fix

#1273

Okay thanks, now it is clear for me too :slight_smile:

#1274

Since SFOS 5.0.0.55, my Whisperfish cannot receive messages anymore. Whisperfish is set up as a primary device on the Xperia 10 ii.

@best-test-400 has reported a similar bug: “Updated Sony Xperia 10 II to Tampella 5.0.0.55 → Whisperfish can send messages but does not receive them any more, no matter which internet data option is selected.”

1 Like
#1275

@best-test-400 made an issue on Gitlab too, but reinstalled the whole phone, so we can’t debug it anymore.

Any chance you can try the same? Run harbour-whisperfish --verbose from CLI, and see whether it gives some interesting output?

#1276

I also have the same problem

2 Likes
#1277

I created issue #734 for this on the Gitlab.
I’m a newbie there so I hope the writings and stuff makes sense there :relaxed:

3 Likes
#1278

I want to say greetings for all the Whisperfish users and welcome all the new comers to the forum.

13 Likes
#1279

:warning: Whisperfish beta.34 :warning:

Contains two mitigations for vulnerabilities, discovered by @valldrac. Vulnerabilities will be listed as CVE-2025-24904 and CVE-2025-24903, and could practically bypass end-to-end encryption, which means that a malicious actor could, theoretically, impersonate one of your contacts. We have no knowledge of exploits in the wild.

Changes

  • Fixes for two impersonation vulnerabilities
  • Preliminary parsing and linking of geo:-urls
  • Fixes for linking and registration
13 Likes
#1280

Updated thank you very much, working fine! :blush:

1 Like
#1281

Linking did work for me :slight_smile:
Thanks !!!

1 Like
#1282

I don’t know whether the issue that @lumen mentions (gitlab #734) is the same what I experience, but: my primary device is an Xperia 10 III with AppSupport (official Signal client). WF on the Fairphone 5 is linked as secondary. Now, whenever I send a message with my secondary device, it never gets marked as read in the primary client, although recipients have read and answered my message. If I send messages with the official client, they become marked as read, if the recipient reads them.
If the issue is already mentioned in this epic thread, I am sorry for double-posting :wink:

1 Like
#1283

My guess is that we experience exactly the same thing :relaxed:

2 Likes