Sorry for responding late.
So running sailtrix from terminal only gives me this:
[defaultuser@JollaC2 ~]$ /usr/bin/harbour-sailtrix
[D] unknown:0 - Opening existing instance
[D] unknown:0 - Sending open signal
[defaultuser@jollaC2 ~]$
Basically I know how piping works, but where do I get logs from?
Could I get another hint here?
And another question that came up is:
Messages are all encrypted when I reopen Sailtrix.
Sometimes messages get encrypted even while the app is active. Being suddenly not able to read what was written before is pretty annoying.
Why is that? And can I do something about it?
Yes, at least research where its source code repository is and report issues with it there (or as a worse alternative, at OpenRepos in the comments).
This forum (FSO) is only suitable for reporting issues with software from Jolla, except for the few apps whose maintainers offer a support thread here at FSO (Patchmanager, µTube etc.); but even for these it is much better to use their original issue tracker (though less convenient for you).
“Piping” was a bit misleading here, unfortunately, the correct term is “output redirection” (that is, either to a file [handle] or another command): [defaultuser@JollaC2 ~]$ /usr/bin/harbour-sailtrix > ~/sailtrix_$(date +%F_%H-%M-%S).log.txt
This would have done the job, but will simply record what you saw on the screen (which does not appear to be relevant).
If you want to achieve both, seeing the output on the screen and record it in a file, do pipe (“really”, here) through tee (still as regular user, i.e. not root): harbour-sailtrix | tee ~/sailtrix_$(date +%F_%H-%M-%S).log.txt
Hello folks and thank you for still using this app. I think I will have some time in the next one or two months, and I’m starting to look at the verification issues. So right now, I follow this procedure to do the verification, and I haven’t seen it fail, so I’m somewhat confused on why there seem to be so many issues.
Open sailtrix on the Rooms tab
In element, initiate the verification
The emojis pop up on both ends
I confirm on both devices in any order
I see the green checkmark in element
Please let me know if you are trying a different way, or the same way…
Sorry, this is a repost from the Sailtrix matrix room, but I wish to get as much data as possible on this, because I’m having a lot of trouble reproducing the issues right now.
First of all, thank you so much for this great application! I have a short question. I am getting hundreds of messages in my chat history of the kind:
“Unable to decrypt: Repeated message_index detected, possible replay attack“
But I can see in between the real messages decrypted. Any hint what could be the reason and how it can be solved? Restarting the application does not help.
Edit: Verification works for me as in the described procedure
Not directly related, but since the last update (1.4.2-1) on my C2 Sailtrix freezes immediatly after startup. The only thing I can do is long press in the app overview and close it from there.
I’m using Hydrogen right now but would like to return…
Are there possibly state events (i.e. members joined, left, changed name, etc) between? Those may be the ones unable to be decrypted. But if you like, I can implement a way to hide those.
Just for the context: I am using direct messages, no rooms.
There may be some state events, I cannot say for sure, but I don’t think so. There are too many of those “"Unable to decrypt” messages and from the turn-taking pattern of their occurrence, it looks like it tries to reproduce the chat behavior.
If I view the source of those messages it says “type”: “m.room.message”. All have date 1st Jan 1970.
Can you (or someone else) see those as well in their chat histories? If you would hide those in Sailtrix, is this problematic in terms of security for others?
I also have all messages encrypted, as soon as I enter a room or chat with another app (no matter if same device (hydrogen) or other device (e.g. Element)).
Even messages I wrote with Sailtrix are encrypted and not accessable any more by Sailtrix. All other apps/devices can access the messages at any time.
