GNU bug report logs - #76231
Jami 20240524.0 not working on Guix System but working on foreign distro

Previous Next

To reply to this bug, email your comments to 76231 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <giovanni <at> biscuolo.net>
To: bug-guix <at> gnu.org
Cc: SW - Andrea Rossi <andrea.rossi <at> swws.it>
Subject: Jami 20240524.0 not working on Guix System but working on foreign
 distro
Date: Wed, 12 Feb 2025 16:10:29 +0100

[Message part 1 (text/plain, inline)]

Hello,

on my two work machines (one desktop and one laptop) I use guix as
package manager on top of Debian, I installed jami on both and it works
perfectly: I'm really impressed by Jami!

I'm testing Jami on a Guix System I installed on a test machine (on the
very same network of my work machines) and it does not work... the same
jami package installed on top of Debian :-(.

I also tested Jami on two different Guix Systems of a friend of mine and
the "mode of failure" is the very same I'm observing on my test Guix
System.

First an easy fix: in Guix System I have to install
gsettings-desktop-schemas otherwise Jami does not start with this error:

--8<---------------cut here---------------start------------->8---

(jami:4825): GLib-GIO-ERROR **: 15:04:05.424: Settings schema 'org.gnome.desktop.interface' is not installed
Trace/breakpoint trap

--8<---------------cut here---------------end--------------->8---

Once I start Jami (jami in a terminal to see log messages) I can import
my account from another device [1] but:

- the list "Linked devices" shows only one device and the "Device name"
  are the first 8 chars of the device fingerprint (usually is the
  hostname of that device)

- the list of contacts shows my list of contacts and the last message
  date is 1/1/70

- I have no messages in any of my swarms (chat rooms)

It seems my Jami client on Guix System cannot connect the DHT and
sincronize data.

If you are interested below you can find a complete log I got running
"jami -d jami-debug.log"

I'm not an expert so I cannot fully understand the meaning of all debug
logs, but I guess it has something to do with this specific logs:

--8<---------------cut here---------------start------------->8---

[1739369430.679|5099|jamiaccount.cpp         :932 ] [Account aba3d9634a668ab7] Can't load proxy URL from cache: filesystem error: cannot get file time: No such file or directory [/home/g/.cache/jami/aba3d9634a668ab7/dhtproxy]

[1739369430.808|5099|conversation_module.cpp :447 ] [ConversationModule] error loading syncingMetadatas_: Can't read file: /home/g/.local/share/jami/aba3d9634a668ab7/syncingMetadatas

[1739369430.810|5099] No IGD available. Mapping will be requested when an IGD becomes available

[1739369433.137|5099] UPNP/NAT-PMP enabled, but no valid IGDs available

[1739369443.560|5099] [device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49] Already connecting, wait for ICE negotiation

--8<---------------cut here---------------end--------------->8---

Furthermore, the Jami client on Guix System freezes when trying to use
the following settings or menu options:

1. Account | Manage Account | Enable account (try to switch it off)[2]

(I see no messages in terminal)

2. Account | Customize profile | (change name and press enter)

--8<---------------cut here---------------start------------->8---

default [1739371696297][WRN][7f8a0e139f80]: qrc:/settingsview/components/CustomizeProfilePage.qml:49:13: QML Connections: Detected function "onStopBooth" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
default [1739371696303][WRN][7f8a0e139f80]: qrc:/settingsview/components/CustomizeProfilePage.qml:50: ReferenceError: settingsView is not defined
default [1739371700439][WRN][7f8964ff96c0]: QSGPlainTexture: Mipmap settings changed without having image data available. Call setImage() again or enable m_retain_image. Falling back to previous mipmap filtering mode.

--8<---------------cut here---------------end--------------->8---

3. Account | Call settings | Ringtone (try to switch it off)

(no messages in terminal)

4. Account | Advanced settings | Enable local peer discovery (try to
switch it on)

5. Account | Advanced settings | Enable proxy (try to switch it on)

There are other settings I did not try, so freezes could be more.

The very same settings on Jami installed on my work machines (foreign
distro) are working as expected.

I hope we can find a solution since IMHO Jami a very useful tool.

Happy hacking, Gio'.


[1] the "pairing" workflow works perfectly, using the PIN generated on
one of the other devices and the account password (I have encrypted my
account)

[2] but when restarting Jami the account is actually disabled, and if I
enable it it works without freezing

[jami-debug.log (text/plain, inline)]

[1739369430.499|5099] UPnPContext: starting dedicated io_context thread
[1739369430.499|5099] Creating UPnPContext instance [0x7b2b7a0]
[1739369430.499|5099] PUPnP: Creating instance [0x7f0664000b80] ...
[1739369430.499|5099|ringbuffer.cpp          :55  ] Create new RingBuffer audiolayer_id
[1739369430.500|5099|video_device_monitor_impl.cpp:150 ] udev: adding device with id Chicony_Electronics_Co.__Ltd._Sony_Visual_Communication_Camera_Sony_Visual_Communication_Camera
[1739369430.564|5099|video_device.h          :133 ] Default video settings: 640x480, 30 FPS
[1739369430.565|5099|video_device_monitor_impl.cpp:150 ] udev: adding device with id Chicony_Electronics_Co.__Ltd._Sony_Visual_Communication_Camera_Sony_Visual_Communication_Camera
[1739369430.566|5099|manager.cpp             :732 ] Not initialized
[1739369430.566|5099|manager.cpp             :732 ] Not initialized
[1739369430.668|5099|manager.cpp             :806 ] Using PJSIP version 2.13.1 for x86_64-unknown-linux-gnu
[1739369430.668|5099|manager.cpp             :807 ] Using GnuTLS version 3.8.3
[1739369430.668|5099|manager.cpp             :808 ] Using OpenDHT version 3.1.11
[1739369430.668|5099|manager.cpp             :809 ] Using FFmpeg version 6.1.1
[1739369430.668|5099|manager.cpp             :812 ] Using Libgit2 version 1.8.4
[1739369430.668|5099|sipvoiplink.cpp         :649 ] Using SIP nameserver: 10.38.2.1
[1739369430.668|5099|sipvoiplink.cpp         :647 ] Error printing SIP nameserver: ai_family not supported
[1739369430.669|5099|sipvoiplink.cpp         :743 ] SIPVoIPLink <at> 0x7b3cbe0
[1739369430.670|5099|manager.cpp             :828 ] Configuration file path: "/home/g/.config/jami/dring.yml"
[1739369430.674|5099|system_codec_container.cpp:251 ] Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU 
[1739369430.674|5099|system_codec_container.cpp:252 ] Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU 
[1739369430.674|5099] CertificateStore: loading certificates from "/home/g/.local/share/jami/aba3d9634a668ab7/certificates"
[1739369430.677|5099] CertificateStore: loaded 6 local certificates.
[1739369430.679|5099] Successfully registered controller 0x7f065c016f50
[1739369430.679|5099] Starting UPNP context
[1739369430.679|5099] [Account aba3d9634a668ab7] Refresh cache for TURN server resolution
[1739369430.679|5099|jamiaccount.cpp         :932 ] [Account aba3d9634a668ab7] Can't load proxy URL from cache: filesystem error: cannot get file time: No such file or directory [/home/g/.cache/jami/aba3d9634a668ab7/dhtproxy]
[1739369430.680|5099] PUPnP: Start search for IGD: attempt 1
[1739369430.680|5099|namedirectory.cpp       :491 ] Loaded 6 name-address mappings
[1739369430.682|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369430.684|5099|account_manager.cpp     :208 ] [Auth] checking device receipt for 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546
[1739369430.688|5099|contact_list.cpp        :526 ] [Contacts] Found account device: pioche 708e016f224f53d767ebc13a5021fff8310cde29630c6c6b6eccf515b9d9f8e1
[1739369430.690|5099|contact_list.cpp        :526 ] [Contacts] Found account device:  cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49
[1739369430.691|5099|account_manager.cpp     :256 ] [Auth] Device 708e016f224f53d767ebc13a5021fff8310cde29630c6c6b6eccf515b9d9f8e1 receipt checked successfully for account 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546
[1739369430.691|5099|jamiaccount.cpp         :1248] [Account aba3d9634a668ab7] loaded account identity
[1739369430.691|5099|ringbuffer.cpp          :55  ] Create new RingBuffer urgentRingBuffer_id
[1739369430.691|5099|audiolayer.cpp          :60  ] [audiolayer] AGC: 1, noiseReduce: auto, VAD: 1, echoCancel: auto, audioProcessor: webrtc
[1739369430.692|5099|pulselayer.cpp          :69  ] [audiolayer] created pulseaudio layer
[1739369430.692|5099|audiolayer.cpp          :169 ] [audiolayer] setHasNativeNS: 0
[1739369430.726|5099|pulselayer.cpp          :146 ] Waiting....
[1739369430.727|5099|pulselayer.cpp          :146 ] Waiting....
[1739369430.728|5099|pulselayer.cpp          :146 ] Waiting....
[1739369430.729|5099|pulselayer.cpp          :150 ] Connection to PulseAudio server established
[1739369430.729|5099|pulselayer.cpp          :180 ] Updating PulseAudio sink list
[1739369430.729|5099|pulselayer.cpp          :197 ] Updating PulseAudio source list
[1739369430.729|5099|pulselayer.cpp          :214 ] Updating PulseAudio server infos
[1739369430.729|5099|pulselayer.cpp          :685 ] PulseAudio server info:
    Server name: pulseaudio
    Server version: 16.1
    Default Sink alsa_output.pci-0000_00_1b.0.analog-stereo
    Default Source alsa_input.pci-0000_00_1b.0.analog-stereo
    Default Sample Specification: s16le 2ch 44100Hz
    Default Channel Map: front-left,front-right

[1739369430.729|5099|audiolayer.cpp          :73  ] Hardware audio format available : {s16, 2 channels, 44100Hz} 0
[1739369430.732|5099] PUPnP: Web-server is enabled. Disabling
[1739369430.732|5099] PUPnP: Web-server successfully disabled
[1739369430.732|5099] PUPnP: Initialized on 10.38.2.58:49152 | fe80::aed5:c1cc:83a7:74d:49152
[1739369430.732|5099] PUPnP: Successfully registered client
[1739369430.732|5099] PUPnP: Send IGD search request
[1739369430.749|5099] Connection to 92.222.89.217 ready
[1739369430.749|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369430.802|5099] [Account aba3d9634a668ab7] Refresh cache for TURN server resolution
[1739369430.802|5099|jamiaccount.cpp         :932 ] [Account aba3d9634a668ab7] Can't load proxy URL from cache: filesystem error: cannot get file time: No such file or directory [/home/g/.cache/jami/aba3d9634a668ab7/dhtproxy]
[1739369430.804|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369430.805|5099|account_manager.cpp     :208 ] [Auth] checking device receipt for 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546
[1739369430.807|5099|contact_list.cpp        :526 ] [Contacts] Found account device: pioche 708e016f224f53d767ebc13a5021fff8310cde29630c6c6b6eccf515b9d9f8e1
[1739369430.808|5099|contact_list.cpp        :526 ] [Contacts] Found account device:  cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49
[1739369430.808|5099|account_manager.cpp     :256 ] [Auth] Device 708e016f224f53d767ebc13a5021fff8310cde29630c6c6b6eccf515b9d9f8e1 receipt checked successfully for account 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546
[1739369430.808|5099|jamiaccount.cpp         :1248] [Account aba3d9634a668ab7] loaded account identity
[1739369430.808|5099|jamiaccount.cpp         :1624] [Account aba3d9634a668ab7] Starting account..
[1739369430.808|5099|conversation_module.cpp :447 ] [ConversationModule] error loading syncingMetadatas_: Can't read file: /home/g/.local/share/jami/aba3d9634a668ab7/syncingMetadatas
[1739369430.808|5099|conversation_module.cpp :1518] [Account aba3d9634a668ab7] Start loading conversations…
[1739369430.809|5099|jamiaccount.cpp         :2414] [Account aba3d9634a668ab7] connecting…
[1739369430.809|5099|jamiaccount.cpp         :1530] [Account aba3d9634a668ab7] UPnP: attempting to map ports
[1739369430.809|5099] Desired port is not set, will provide the first available port for [UDP]
[1739369430.810|5099] No IGD available. Mapping will be requested when an IGD becomes available
[1739369430.810|5099|jamiaccount.cpp         :1548] [Account aba3d9634a668ab7] DHT UPNP mapping changed to JAMI-UDP:20825 (state=PENDING, auto-update=YES)
[1739369430.810|5099|jamiaccount.cpp         :1588] [Account aba3d9634a668ab7] Mapping request is in PENDING state: starting the DHT anyway
[1739369430.814|5099|jamiaccount.cpp         :1651] [Account aba3d9634a668ab7] Bootstrap node: bootstrap.jami.net
[1739369430.814|5099|jamiaccount.cpp         :1913] [Account aba3d9634a668ab7] Dht status: IPv4 connecting; IPv6 disconnected
[1739369430.815|5099|jamiaccount.cpp         :1667] [Account aba3d9634a668ab7] Track presence for 25e63ac76d9d00d9bdc6363a2b7115eab2dba2ec
[1739369430.815|5099|jamiaccount.cpp         :1667] [Account aba3d9634a668ab7] Track presence for 2fe5631fdb784bda1b61ccd52883b8f9685270da
[1739369430.815|5099|jamiaccount.cpp         :1667] [Account aba3d9634a668ab7] Track presence for 8fe49423baa876355d4c660bfe6b7f16cb813198
[1739369430.817|5099|manager.cpp             :2699] Set accounts order : aba3d9634a668ab7/
[1739369430.817|5099|manager.cpp             :1793] Saving Configuration to XDG directory /home/g/.config/jami/dring.yml
[1739369430.872|5099] Connection to 51.254.39.157 ready
[1739369430.872|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369430.923|5099|jamiaccount.cpp         :1913] [Account aba3d9634a668ab7] Dht status: IPv4 connected; IPv6 disconnected
[1739369430.923|5099|jamiaccount.cpp         :2409] [Account aba3d9634a668ab7] connected
[1739369430.923|5099] [Account aba3d9634a668ab7] Refresh cache for TURN server resolution
[1739369430.936|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369430.936|5099] Store DHT public IPv4 address: 93.56.171.185
[1739369430.936|5099] Setting the known public address to 93.56.171.185
[1739369430.974|5099|jamiaccount.cpp         :1913] [Account aba3d9634a668ab7] Dht status: IPv4 connected; IPv6 connecting
[1739369430.992|5099] Connection to 92.222.89.217 ready
[1739369430.992|5099] [Account aba3d9634a668ab7] Cache refreshed for TURN resolution
[1739369433.137|5099] UPNP/NAT-PMP enabled, but no valid IGDs available
[1739369439.638|5099|archive_account_manager.cpp:523 ] Building device sync from 708e016f224f53d767ebc13a5021fff8310cde29630c6c6b6eccf515b9d9f8e1
[1739369439.638|5099|archive_account_manager.cpp:535 ] sending device sync to  cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49
[1739369441.460|5099] [device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49] Received request
[1739369441.462|5099] Found peer device: cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49 account:05a8aca67ce08acc8b6e15ff32dcb3fb00a25546 CA:0cb0cbe6a8d6b1148197af2b6c0e6333ac0282d0
[1739369441.462|5099] [device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49] New connection request
[1739369441.464|5099|account_manager.cpp     :431 ] Found peer device: cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49 account:05a8aca67ce08acc8b6e15ff32dcb3fb00a25546 CA:0cb0cbe6a8d6b1148197af2b6c0e6333ac0282d0
[1739369441.464|5099] %s
[1739369441.464|5099|account_manager.cpp     :473 ] [Auth] Discarding message from unauthorized peer 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546.
[1739369441.465|5099|jamiaccount.cpp         :2002] Discarding ICE request from 0000000000000000000000000000000000000000
[1739369441.465|5099] [device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49] Refusing connection
[1739369443.138|5099] PUPnP: Start search for IGD: attempt 2
[1739369443.138|5099] PUPnP: Send IGD search request
[1739369443.519|5099|jamiaccount.cpp         :1906] Query for local certificate store: a2150dc3c13981b20806a652d36b8b15da106246: 0 found.
[1739369443.520|5099|jamiaccount.cpp         :1906] Query for local certificate store: e916fd591a29bc8fac0cb5d66007ee9b1480c5af: 0 found.
[1739369443.556|5099|jamiaccount.cpp         :3496] [Account aba3d9634a668ab7] Request SIP connection to peer 05a8aca67ce08acc8b6e15ff32dcb3fb00a25546 on device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49
[1739369443.556|5099|jamiaccount.cpp         :3522] [Account aba3d9634a668ab7] Ask cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49 for a new SIP channel
[1739369443.557|5099] Store DHT public IPv4 address: 93.56.171.185
[1739369443.558|5099] [ice:0x7f062c1024f0] Creating IceTransport session for ""
[1739369443.558|5099] [ice:0x7f062c1024f0] Initializing the session - comp count 1 - as a slave
[1739369443.558|5099] [ice:0x7f062c1024f0] Add srflx reflexive candidates [10.38.2.58:9 : 93.56.171.185:9] for comp 1
[1739369443.558|5099] added turn server '92.222.89.217', port 3478
[1739369443.560|5099] [device cc3646a4fcc88a3553e11d981dad2a84edfe5aaf80f4dd0c33fc7b0a15de5a49] Already connecting, wait for ICE negotiation
[1739369465.548|5099] PUPnP: Start search for IGD: attempt 3
[1739369465.549|5099] PUPnP: Send IGD search request
[1739369497.956|5099] PUPnP: Setup failed after 3 trials. PUPnP will be disabled!
[1739370870.605|5099] Successfully unregistered controller 0x7f065c016f50
[1739370870.605|5099] Stopping UPnP context
[1739370870.605|5099] PUPnP: Successfully unregistered client
[1739370870.606|5099|jamiaccount.cpp         :896 ] Saved account config to /home/g/.local/share/jami/aba3d9634a668ab7/config.yml
[1739370870.606|5099|jamiaccount.cpp         :2359] [Account aba3d9634a668ab7] unregistering account 0x7f065c000da0
[1739370870.606|5099|jamiaccount.cpp         :281 ] [Account aba3d9634a668ab7] Shutdown connections

[Message part 3 (text/plain, inline)]

-- 
Giovanni Biscuolo

«Si può sperare
 Che il mondo torni a quote più normali».

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Divya Ranjan <divya <at> subvertising.org>
To: Giovanni Biscuolo <giovanni <at> biscuolo.net>
Cc: 76231 <at> debbugs.gnu.org,
 Jan Wielkiewicz <tona_kosmicznego_smiecia <at> interia.pl>,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 SW - Andrea Rossi <andrea.rossi <at> swws.it>
Subject: Re: bug#76231: Jami 20240524.0 not working on Guix System but
 working on foreign distro
Date: Thu, 13 Feb 2025 13:18:34 +0000

Hello again Giovanni,

I’ll just go ahead and CC some old developers from Guix who were initially part of bringing Jami to Guix. Found them by searching down the mailing list[0].

Hopefully y’all can guide us a bit with regards to where things are going wrong.

[0]: https://yhetil.org/guix/?q=maintaining+jami

Regards,
-- 
Divya Ranjan,
Philosophy, Mathematics, Libre Software.

PGP Fingerprint: F0B3 1A69 8006 8FB8 096A  2F12 B245 10C6 108C 8D4A

Message #13 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Luis Felipe <sirgazil <at> zoho.com>
To: 76231 <at> debbugs.gnu.org
Subject: Jami 20240524.0 not working on Guix System but working on foreign
 distro
Date: Thu, 13 Feb 2025 17:58:28 +0000

[Message part 1 (text/plain, inline)]

Hello, just to confirm that using

  guix system 4fccad8
  Jami 20240524.0

I see the same errors:

  [1739460365.258|6114|jamiaccount.cpp         :932 ] [Account 
4feb6fb4bf3ae927] Can't load proxy URL from cache: filesystem error: 
cannot get file time: No existe el fichero o el directorio 
[/home/yo/.cache/jami/4feb6fb4bf3ae927/dhtproxy]

  [1739460365.309|6114|conversation_module.cpp :447 ] 
[ConversationModule] error loading syncingMetadatas_: Can't read file: 
/home/yo/.local/share/jami/4feb6fb4bf3ae927/syncingMetadatas

In my case, Jami is not working in the sense that I'm not able to 
contact anyone, and nobody is able to contact me (see 
https://lists.gnu.org/archive/html/help-guix/2024-10/msg00075.html). 
Sometimes I can see contact requests only if I restart Jami (by 
finishing the .jami-real process and starting Jami again), but from 
there on Jami can't identify when accepted contacts are online. So it 
sure looks like synchronization problems.

But the jami client does start normally for me though. Maybe in my case 
the missing dependency that Giovanni had to install is already satisfied 
because I use the GNOME desktop.

-- 
Luis Felipe López Acevedo

[OpenPGP_0x0AB0D067012F08C3.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Message #16 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Divya Ranjan <divya <at> subvertising.org>
Cc: 76231 <at> debbugs.gnu.org,
 Jan Wielkiewicz <tona_kosmicznego_smiecia <at> interia.pl>,
 SW - Andrea Rossi <andrea.rossi <at> swws.it>,
 Giovanni Biscuolo <giovanni <at> biscuolo.net>
Subject: Re: bug#76231: Jami 20240524.0 not working on Guix System but
 working on foreign distro
Date: Sat, 15 Feb 2025 22:32:41 +0900

Hi Divya,

Divya Ranjan <divya <at> subvertising.org> writes:

> Hello again Giovanni,
>
> I’ll just go ahead and CC some old developers from Guix who were
> initially part of bringing Jami to Guix. Found them by searching down
> the mailing list[0].
>
> Hopefully y’all can guide us a bit with regards to where things are going wrong.

I'm guessing it's simply getting a bit dated?  In my experience, as soon
as you fall one on a few stable releases behind, you start experimenting
more problems.  I'm not sure if Jami is supposed to be backward
compatible with previous versions, but even if it was, it's probably not
super well tested.

I'd suggest updating it (but as you noted, that's sadly often not
trivial).  I could provide some assistance if you'd like to pick up its
maintenance.

-- 
Thanks,
Maxim

Message #19 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <g <at> xelera.eu>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 76231 <at> debbugs.gnu.org
Subject: Re: bug#76231: Jami 20240524.0 not working on Guix System but
 working on foreign distro
Date: Sat, 15 Feb 2025 16:45:09 +0100

[Message part 1 (text/plain, inline)]

Hello Maxim,

thank you for your interest in this bug report.

First of all: please are you succesfully running Jami on a Guix System
and if yes what's its version?

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Divya Ranjan <divya <at> subvertising.org> writes:
>
>> Hello again Giovanni,
>>
>> I’ll just go ahead and CC some old developers from Guix who were
>> initially part of bringing Jami to Guix. Found them by searching down
>> the mailing list[0].
>>
>> Hopefully y’all can guide us a bit with regards to where things are going wrong.
>
> I'm guessing it's simply getting a bit dated?

I guess you are guessing the Jami I'm running is a little bit dated: I'm
using the last available package in guix, please see the subject.

Or are you guessing that 20240524.0 packaged in Guix is a little bit
dated?

Anyway...

> In my experience, as soon as you fall one on a few stable releases
> behind, you start experimenting more problems.  I'm not sure if Jami
> is supposed to be backward compatible with previous versions, but even
> if it was, it's probably not super well tested.

As I reported in the first message of this bug report thread, the issue
I'm [1] experiencing it's _only_ when running Jami 20240524.0 on a Guix
System, the very same version - installed via guix as package manager -
is running (very) well on Debian.

Maybe it's just some missing dependency in the package definition that
luckily is installed in on my Debian sistems?

I'd like to help finding what is making running Jami problematic on a
Guix System but I don't know what to do except reporting the logs I
found (see my first message in the bug report)

> I'd suggest updating it (but as you noted, that's sadly often not
> trivial).  I could provide some assistance if you'd like to pick up its
> maintenance.

I agree that updating the Guix Jami package is useful but I'd like to
understand what is preventing 20240524.0 from running on a Guix System
but not on a foreign distro.

Thanks, Gio'


[1] and others, i.e. Luis Felipe as he confirmed


-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Giovanni Biscuolo <g <at> xelera.eu>
Cc: 76231 <at> debbugs.gnu.org
Subject: Re: bug#76231: Jami 20240524.0 not working on Guix System but
 working on foreign distro
Date: Sun, 16 Feb 2025 10:57:47 +0900

Hi Giovanni,

Giovanni Biscuolo <g <at> xelera.eu> writes:

> Hello Maxim,
>
> thank you for your interest in this bug report.
>
> First of all: please are you succesfully running Jami on a Guix System
> and if yes what's its version?

It's been a while I've tried to make actual calls, with my last
experience (perhaps 2 months ago) was not successful in establish calls
to another Guix System user.  I've definitely used it successfully in
the past.

> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> Divya Ranjan <divya <at> subvertising.org> writes:
>>
>>> Hello again Giovanni,
>>>
>>> I’ll just go ahead and CC some old developers from Guix who were
>>> initially part of bringing Jami to Guix. Found them by searching down
>>> the mailing list[0].
>>>
>>> Hopefully y’all can guide us a bit with regards to where things are going wrong.
>>
>> I'm guessing it's simply getting a bit dated?
>
> I guess you are guessing the Jami I'm running is a little bit dated: I'm
> using the last available package in guix, please see the subject.
>
> Or are you guessing that 20240524.0 packaged in Guix is a little bit
> dated?

The later, yes.  The latest stable release 20241126, and there are
recent nightlies as well.

> Anyway...
>
>> In my experience, as soon as you fall one on a few stable releases
>> behind, you start experimenting more problems.  I'm not sure if Jami
>> is supposed to be backward compatible with previous versions, but even
>> if it was, it's probably not super well tested.
>
> As I reported in the first message of this bug report thread, the issue
> I'm [1] experiencing it's _only_ when running Jami 20240524.0 on a Guix
> System, the very same version - installed via guix as package manager -
> is running (very) well on Debian.
>
> Maybe it's just some missing dependency in the package definition that
> luckily is installed in on my Debian sistems?

I wouldn't expect something missing, but perhaps some service component
is Debian is behaving differently/e.g. NetworkManager, which Jami uses
to detect connection changes.  I'm not sure.  Or our nss-certs
certificates used on Guix System may be too old.

> I'd like to help finding what is making running Jami problematic on a
> Guix System but I don't know what to do except reporting the logs I
> found (see my first message in the bug report)

Oh, apologies for missing that earlier; I thought you were comparing
different versions of Jami.  That's indeed very curious/interesting that
the same Guix jami package would work on better on a foreign
distribution than on Guix System.  I'm not sure how you could go to
debug this...

Perhaps you could compare their strace captures?  You may find a hint of
a notable difference there.  I use 'emacs-strace-mode' to open .strace
files I've generated with e.g.

--8<---------------cut here---------------start------------->8---
$ strace -f -s600 -ojami.strace jami -d
--8<---------------cut here---------------end--------------->8---

-- 
Thanks,
Maxim

Message #25 received at 76231 <at> debbugs.gnu.org (full text, mbox):

From: Divya Ranjan <divya <at> subvertising.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 76231 <at> debbugs.gnu.org,
 Jan Wielkiewicz <tona_kosmicznego_smiecia <at> interia.pl>,
 SW - Andrea Rossi <andrea.rossi <at> swws.it>,
 Giovanni Biscuolo <giovanni <at> biscuolo.net>
Subject: Re: bug#76231: Jami 20240524.0 not working on Guix System but
 working on foreign distro
Date: Mon, 17 Feb 2025 11:43:42 +0000

Hello Maxim,

> I'm guessing it's simply getting a bit dated?  In my experience, as soon
> as you fall one on a few stable releases behind, you start experimenting
> more problems.  I'm not sure if Jami is supposed to be backward
> compatible with previous versions, but even if it was, it's probably not
> super well tested.

Right, make sense. I check the logs and realized it’s actually packaging an old commit.

> I'd suggest updating it (but as you noted, that's sadly often not
> trivial).  I could provide some assistance if you'd like to pick up its
> maintenance.

Well, to be honest, I don’t exactly piece together how Jami gets packaged on Guix? Also, why do we need to package ffmpeg-jami separately? Can you give a brief idea of how it is packaged currently, and what are the caveats? I have a hunch that it should/can be done better, but not sure how exactly.


Regards,
-- 
Divya Ranjan,
Philosophy, Mathematics, Libre Software.

PGP Fingerprint: F0B3 1A69 8006 8FB8 096A  2F12 B245 10C6 108C 8D4A

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.