Whisperfish - The unofficial SailfishOS Signal client

Great! Please also ask him if he can add a simple ‘copy’ button to the device link code, for people like us who want to run Molly on the same device as the primary instance. (Although, come to think of it, the Android clipboard isn’t shared with the Sailfish clipboard, so perhaps it wouldn’t be of much help in this case.)

I added Molly as a secondary on tablet, with primary android, and it seems to be working fine, after a while it started syncing properly.

But when I tried to install Molly on phone for maybe be used as a primary, I can’t even add repo to F-droid. Had no problem adding repo on tablet F-droid.

Hey there, everyone! Glad to see all the interest in Molly. I’ve just created an account to drop a couple of comments.

First, thanks for reporting the bugs. We have our own issue tracker on GitHub, and it would be awesome if you could submit the reports there, to keep this thread on-topic. Submitting bug reports really helps me to track issues, especially when my thoughts are a bit scattered. We also have support@molly.im, but the most important thing is to attach the debug logs (you can find them in the menu: Settings > Help > Debug log), because without those, I wouldn’t even know where to start. To access the debug log, you can also tap any element on the registration screen ten times. Don’t worry, they’re safe to share since they’re redacted to remove any personal information.

On another note, I’m a big fan of Whisperfish. If there’s anything I can do to improve compatibility between both apps, feel free to reach out. I’ll do my best to help.


He, thank you so much for joining here, @valldrac! This is a bug in both Molly and a separate one in Whisperfish, so we’ll have to collaborate a bit to get both fixed :slight_smile:

If we have the crash log of Molly, we can also infer what Whisperfish’ wrong behaviour is, and we can probably fix the linking with Flare too… all in one go!


As Whisperfish crashes once in a while (which does not make girlfriend happy when I don’t reply) I was wondering if there was a simple command to restart it with situations on the background, without the app actually popping up. I think that a refresh cover action would also be a good idea.

@turmelus1 I understand your reasoning, but I would then rather spend my time into catching and fixing the crashes (I also have them) than to work on a workaround.

Small vulnerability announcement

I have filed for CVE - CVE-2023-42444 and CVE - CVE-2023-42447. These are denial-of-service related vulnerabilities that are exploitable in Whisperfish (and other software too). Those vulnerabilities are fixed upstream (libraries maintained by the broader Whisperfish team), but both fixes require a more recent Rust compiler than what we currently use in CI. The next SDK that gets released will have Rust 1.62, and we’ll be able to incorporate these (and many more) fixes.

Jist of the story is: these will not get exploited in practice. Either your contacts (case of the blurhash bug) or Signal themselves (case of the phonenumber bug) should be considered the attackers in this scenario, and that’s quite a weird threat model. Just wanted to be in front of the news with this announcement.


One of the Rust’s downside… :-/

I reinstalled SFOS (from to and did a manual migration of whisperfish by copying whisperfish data (in .config and .local/share) from my backup. After doing this I can see old messages and attachments but I cannot see new received attachments or send messages.

Is it possible to reset data/history without having to register again?

Can you open an issue with censored logs, or contact me with logs by email? Difficult to debug here. Restoring data after registration is currently not possible. Resetting data without registering is also not possible.


It seems I now can send messages. Perhaps it was some timeout from signal servers (I reinstalled last Saturday)?

I can however still not see attachments. I have created an issue and attached the log.

1 Like

Whisperfish 0.6.0-beta.21 :partying_face:

Several small fixes

Changes :twisted_rightwards_arrows:

  • Embedded QR code scanner for device linking on Sailfish 4 and higher.
  • More relaxed parsing of SMS-based confirmation codes
  • Don’t close keyboard when using send or enter
  • Detect and handled deleted contacts in groups
  • Some fixes relating to attachment fetching, including a crash
  • Update blurhash decoding, should be a lot faster
  • More correct message for empty session view
  • Disable sending messages in UI for unregistered contacts
  • Fix marking of unregistered contacts
  • Hide archived conversations in cover page
  • Add cargo-deny to catch CVE’s in the future
  • Add setting to hide recipient phone number in conversation page
  • Fix relating to profile fetching
  • Correctly handle nullable E164’s and other nullable fields
  • Vendor OpenSSL: no more separate build for SailfishOS 3!
  • Fix reaction UI not updating, among other UI fixes to reactions

Important note to Sailfish 3 users :warning:

The builds for Sailfish 3 and Sailfish 4 are now the same package again. This was required because the pending update to Rust 1.61 (maybe even 1.64 and 1,72 :pray:).
You may need to tinker with the OpenRepos app in order to update. Worst case, you can uninstall the sf3 build manually, and install the unified application. You can check whether the update worked by opening Whisperfish and opening the about menu: it should show beta 21 or newer.


Nice update, its working a lot better than when i last used it. One quick question though, i set Whisperfish up as a primary device but when i try to link with the desktop app so i can changed my profile picture it says:

“Something went wrong! - An unexpected error occurred, please try again.”

I’m currently using Solus OS, which is a Linux distro. I have tried their own packaged version and the flatpak version of signal-desktop but both had the same result. So just wanted to see if this is a known problem or if i should try another distro and see if that fixes it?


Good to hear that it works well!

The secondary device linking is indeed broken currently. It’s a known issue and quite a nuisance indeed…

1 Like

yup, tried to relink whisperfish as secondary, due to laptop change and can confirm that it does not work :smiley:


@direc85 and Gabriel Féron are actively working on getting it fixed! :slight_smile:

Meanwhile, I’ve started another huge refactoring work that should enable a lot of new features in the near and far future.


It seems, that the problem with the invisible pictures are also solved.
I did not have the problem after update with new pictures.
But the old invisible pictures are still not shown (may be a cache issue) …


I’m sure this has been discussed many times before, so apologies (I didn’t have the stamina to check all… deep breath… 976 posts in the thread!). Could anyone provide advice with getting added to a Group? I understand I need to be added not invited for V2 groups. But after I asked the Group owner to do this, it still didn’t get me in. Is there anything else that I might be missing? I have a desktop client linked to my Whisperfish (v0.6.0-beta.21) account, but that’s also throwing errors. In the logs I see:

2023-11-09 12:16:27.466 [WARN] We're not handling raw group changes yet. Let's trigger a group refresh for now.
2023-11-09 12:16:27.484 [WARN] Received an unsealed message from ServiceAddress { uuid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx }.       
1 Like

Hey @flypig, those two warnings shouldn’t inhibit you from joining the group. Do you have more logs than that? Feel free to contact me off the forum too. This doesn’t seem right, and seems like a new issue.


If the group exists in Whisperfish, you could do manual refresh of the group by enabling debug mode in settings, then go to the group info sub-page and select group refresh from the pulley menu. If it doesn’t exist, then indeed more logs are needed…


Thank you both! I do have more logs and would be happy to share them; and will also give the debug group refresh a go too. But just before going down that route, it looks like the person adding me is still sending invitations. Assuming that’s the case, so you know of any good walkthroughs for how to add someone, rather than invite them? Is this the correct process?

1 Like