Whisperfish - The unofficial SailfishOS Signal client

Yes. Storeman.

sorry…cannot read…missed that the repo hadn’t been added…

1 Like

Molly is fine, we support linking to Molly. I consider @valldrac a friend of mine :slight_smile:

But I can’t help you without some logs!

1 Like

Hehe, we all have such things. Happy you’re back in the game!

1 Like

Hi all,
I’ve just joined a group here and ppl have been sending multiple photos in one post. More than 12. I can’t seem to see more than the initial group. Is this a current limitation?
Xperia 10 III

Yeah, the UI supports only five attachments at the moment. IIRC the attachments are downloaded in the attachments directory anyway so you can look for the attachments received. The easiest way is running ls -lt | grep "Jan 25" (or whichever date it is) to see the 12 attachments that arrived at the same time or near it. Then you can copy them to Pictures and see them in Gallery.

Better attachments viewer page is on the list but sadly there hasn’t been any progress on it for some time. But it’s coming, at some point :wink:

5 Likes

Registering Whisperfish as a primary device is not currently working for me. I am getting the following error in the process:

This occurs right after I successfully complete the captcha.

Same here, Xperia X10 II, tried several times and according to the wiki I have to wait 7 days before I can try again.

hi,
i did try to install whisperfish as secondary device on my c2 and get the same result

can you point me to the 7day information please ?

There is indeed currently a known issue during linking.

Possibly, you may have to erase the data directories before trying again though. You should see a fix coming this weekend.

@sailor28, could you try wiping (see link above) and capturing the logs during the registration? If you indeed come from Android/iOS, you may want to disable the registration lock before trying again, or indeed wait 7 days with the previous account untouched/uninstalled.

@pawel.spoon: Frequently Asked Questions · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab (but this is not applicable to secondary devices; your problem is the one that’s about to be fixed!)

4 Likes

thanks for the quick answer (as always :slight_smile: )
i have checked the register-lock. it is off
yes i do cleaning before retries. (took me a while to find the folders after the months on volla)

do you think there is an issue running primary and secondary (whisperfish) on same phone ? beside the fact that you need something to copy the qr code ?

1 Like

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

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

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?

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

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

1 Like

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:

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

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

For me the answer was clear: wait for fix