Jami does not work

Jami does not work

[gfp]

[-- Attachment #1.1.1: Type: text/plain, Size: 278 bytes --]

Hi,

I wanted to use Jami,
but it does not work.
I am seeing the person's name,
but when I write to him,
he doesn't get it,
even though he is online.

What do I have to install additionally?

What prerequisites on my laptop do I need to have?

Thanks

Gottfried

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2451 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

Re: Jami does not work

[Luis Felipe]

[-- Attachment #1.1.1: Type: text/plain, Size: 1054 bytes --]

On 24/10/24 9:43, gfp wrote:
> Hi,
>
> I wanted to use Jami,
> but it does not work.
> I am seeing the person's name,
> but when I write to him,
> he doesn't get it,
> even though he is online.

I haven't use Jami for several months (maybe a year), but that often 
happened to me before when trying out Jami with people on Guix, Androids 
and Windows: some messages, and sometimes all messages, were not 
displayed. Great part of my contacts didn't continue to use Jami because 
of that; Jami's performance was subpar compared to the proprietary tools 
they're used to.

That said, a few conversations worked fine in the past, so I keep Jami 
installed hoping that it will become more reliable.

If you would like to do some testing, feel free to send test messages to 
my account (luis-felipe) or let me know if you'd like to test other 
features.

> What do I have to install additionally?
>
> What prerequisites on my laptop do I need to have?

As far as I know, you don't need anything else besides the Jami package.



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

Re: Jami does not work

[Felix Lechner via]

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

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'.

Kind regards
Felix

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

[-- Attachment #2: ResizedImage_2024-10-25_17-27-31_8485.jpg --]
[-- Type: image/jpeg, Size: 7726 bytes --]

Re: Jami does not work

[Luis Felipe]

[-- Attachment #1.1.1: Type: text/plain, Size: 2053 bytes --]

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.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

Re: Jami does not work

[Luis Felipe]

[-- Attachment #1.1.1: Type: text/plain, Size: 1417 bytes --]

On 26/10/24 15:30, Luis Felipe wrote:
> 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.

Done. In two Androids, the new contact request worked (although it took 
a couple of minutes to arrive), and they were able to talk to each other 
once the request was accepted.

:(



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]