Hi Felix, Gottfried,

On 26/10/24 0:36, Felix Lechner via wrote:
> Hi Gottfried,
>
> On October 24, 2024 2:43:20 AM PDT, gfp <gfp@posteo.at> wrote:
>
>> I wanted to use Jami,
>> but it does not work
> I run a development version of the Shepherd and when trying Jami was surprised to see the attached message on the console. Probably a Shepherd bug, though, so copying Ludo'.
>
> Ran 'jami' and 'jami --help'.

Well, I just tried communicating between Jami apps in Guix and Android 
and I think I see the same Gottfried is experiencing: you can find the 
user to talk to from both apps, you are allowed to start a conversation, 
but messages are not displayed to any of them.

Jami's daemon seems to be running alright, though (at least messages are 
logged in /var/log/messages when you interact with the Jami client).

> P.S. Jami worked between Felipe and I a year ago.

Right :)

In this case, though, I also noticed some odd things:

1. Jami used to emit a desktop notification telling me that a new user 
that is not in my contact list wants to start a conversation. That 
didn't happen this time.
2. I found 3 ".jami-real" processes running at the same time (all 
instances of "~/.guix-profile/bin/jami")
3. In /var/log/messages: jami: [ConversationModule] error loading 
syncingMetadatas_: Can't read file: 
~/.local/share/jami/4feb6fb4bf3ae927/syncingMetadatas
4. In /var/log/messages: jami: Got trust request (confirm: false) from: 
HASH_A / HASH_B. ConversationId: HASH_C

I wonder if those messages have anything to do with the problem. Maybe 
Jami is never showing the notification that allows you to trust the new 
contact, it still lets you add the contact and start a conversation with 
it, you start typing messages thinking everything is alright, but the 
messages never go through because the contact has not been marked as 
trusted in the first place (?).

I'll see if I can find another person that doesn't use Guix to check 
whether Jami apps can talk to each other in other systems.