Skip to content
Snippets Groups Projects
New look: Off

(Git error?) causing Swarm conversation not to load (Snap package)

    • Open Issue created by ring user @ringuser

    Bug report form

    Describe your environment

    Please specify the following:

    Device 0. is not available anymore and had account A and had a connection to account B as well ad device 2.

    • OS: Ubuntu 22.04
    • Jami version: Current Snap: Eleutheria Version: 202402141827
    • What build you are using: Snap
    • EDIT: Account A.
    • OS: Android
    • Jami version: Current F-Droid: Eleutheria 20240308-01
    • What build you are using: Snap
    • EDIT: Account B.

    Steps to reproduce

    Note: Better the scenario is, better we will be able to reproduce and debug.

    • Can you reproduce the bug: at will
    • Steps:
      1. Import a backup of a Jami account A. in Jami 1. 2. Both Jami 1 and Jami 2 are online 3. I open a conversation between Jami 1. and 2. 4. I send a messages from 2. to 1.
    • Actual result: 1. If I open the conversation on device 1., I see the following message: - Sie haben die Unterhaltungsanfrage angenommen - Warten bis ## eine Verbindung herstellt, um die Unterhaltung zu synchronisieren. 2. I cannot read any messages or chat because neither the messages nor the chat text field is shown. 3. Calls are working. 4. There is no possibility to continue the conversation.
    • Expected result: 1. The conversation is synchronizing or is synchronized and I can use it. 2. The messages send are shown in Jami 1. 3. Calls are working. 4. I can continue the conversation.

    Additional information

    [1710587184.680|43502|manager.cpp             :957 ] ############## START MONITORING ##############
[1710587184.680|43502|manager.cpp             :958 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1710587184.680|43502|manager.cpp             :959 ] Using GnuTLS version 3.8.2
[1710587184.680|43502|manager.cpp             :960 ] Using OpenDHT version 3.1.7
[1710587184.680|43502|manager.cpp             :967 ] Opened files: 106
[1710587184.680|43502] ConnectionManager current status:
[1710587184.680|43502] ConnectionManager end status.
[1710587184.680|43502|manager.cpp             :976 ] ############## END MONITORING ##############
[1710587196.589|43915] [device ###] Received request answer
[1710587196.589|43915] [device ###] Respond received, but cannot find request

    For retrieving logs, cf this page.

    Edited

    Designs

      Child items ...

      2. Activity

      • ovari
        ovari @ovari ·

        Have experienced no chat history with Linux Mint. Hopefully the chat will show after a day for you. Perhaps a restart can help too.

        Fortunately the Place audio call button is available while the chat is synchronizing.

        • ring user
          ring user @ringuser ·
          Author

          For me. no buttons are available. Only the <-- button at the upper left, the search button and the message Sie haben die Unterhaltungsanfrage angenommen - Warten bis ## eine Verbindung herstellt, um die Unterhaltung zu synchronisieren. I can place an audio call with the context menu of the chat available with the right mouse button click at the list entry at the left. The call is working - but the chat window remains empty. 0001

          EDIT: English Translation of the message: You have accepted the conversation request - waiting until ## makes a connection to synchronize the conversation

          Edited by ring user
        • ovari
          ovari @ovari ·

          Yes, you are correct. Can only make a call by the right-click context menu. jami-client-qt#1123

          Fortunately there was a patch that was abandoned to remove the Start video call and Start audio call in the right-click context menu. This has enabled calling to still be possible due to the bug which stops the chat synchronizing. jami-client-qt#1123 (comment 43226) https://review.jami.net/c/jami-client-qt/+/24704

          It would be beneficial if the Place audio call and Place video call buttons were added to the top right even when the chat is synchronizing to make the feature discoverable without using a right-click. jami-client-qt#1123

          Edited by ovari
        • Please register or sign in to reply
      • ring user changed the description

        changed the description

      • ovari
        ovari @ovari ·

        Perhaps this issue is related to jami-client-qt#1223 (closed)

        Thank you

      • ovari mentioned in issue jami-client-qt#1223 (closed)

        mentioned in issue jami-client-qt#1223 (closed)

      • ovari
        ovari @ovari ·

        A workaround that may work to for all people in a chat to Remove conversation and then re-add that conversation. Note that all the chat history will be lost.

      • ovari
        ovari @ovari ·

        Issue request to showing call buttons when the chat is synchronizing: jami-client-qt#1123

        • Sébastien Blin
          Sébastien Blin @sblin ·
          Owner

          "Back up" only exports key and some data, but not the conversations.

          Is any other device with the conversations available?

        • ring user
          ring user @ringuser ·
          Author

          Yes, device 2. with account B. has the whole conversation and is connected to device 1. and account A.

        • ring user
          ring user @ringuser ·
          Author

          So in my opinion, device 1. should get the history from device 2.

        • ring user
          ring user @ringuser ·
          Author

          The message at the screen says that Jami is waiting for account B to connect so the history can be synchronized. But although the device 2. is online, this never happens.

        • Sébastien Blin
          Sébastien Blin @sblin ·
          Owner

          Do you have logs from both devices when linking?

        • ring user
          ring user @ringuser ·
          Author

          Linux:

          [1711809837.267|19265|manager.cpp             :957 ] ############## START MONITORING ##############
[1711809837.267|19265|manager.cpp             :958 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1711809837.267|19265|manager.cpp             :959 ] Using GnuTLS version 3.8.2
[1711809837.267|19265|manager.cpp             :960 ] Using OpenDHT version 3.1.7
[1711809837.268|19265|manager.cpp             :967 ] Opened files: 107
[1711809837.268|19265] ConnectionManager current status:
[1711809837.268|19265] ConnectionManager end status.
[1711809837.268|19265|manager.cpp             :976 ] ############## END MONITORING ##############
[1711809837.825|19265] [ice:0x7########] ICE transport is not running
[1711809838.807|19265] [ice:0x7########] ICE transport is not running
[1711809839.825|19265] [ice:0x7########] ICE transport is not running
[1711809840.826|19265] [ice:0x7########] ICE transport is not running
[1711809841.826|19265] [ice:0x7########] ICE transport is not running
[1711809842.825|19265] [ice:0x7########] ICE transport is not running
[1711809843.825|19265] [ice:0x7########] ICE transport is not running
[1711809844.826|19265] [ice:0x7########] ICE transport is not running
[1711809845.825|19265] [ice:0x7########] ICE transport is not running
[1711809846.825|19265] [ice:0x7########] ICE transport is not running
[1711809847.826|19265] [ice:0x7########] ICE transport is not running
[1711809848.825|19265] [ice:0x7########] ICE transport is not running
[1711809849.637|19415] PUPnP: Start search for IGD: attempt 3
[1711809849.637|19415] PUPnP: Send IGD search request
[1711809849.825|19265] [ice:0x7########] ICE transport is not running
[1711809850.825|19265] [ice:0x7########] ICE transport is not running
[1711809851.826|19265] [ice:0x7########] ICE transport is not running
[1711809852.430|19415] NAT-PMP: Trying to initialize IGD
[1711809852.440|19415] NAT-PMP: Initialized on gateway 192.168.178.1
[1711809852.470|19415] NAT-PMP: Read response on IGD 192.168.178.1 failed - UNSUPPORTEDVERSION
[1711809852.470|19415] NAT-PMP: Start search for IGDs. Attempt 3
[1711809852.889|19265] [ice:0x7########] ICE transport is not running
[1711809853.825|19265] [ice:0x7########] ICE transport is not running
[1711809854.825|19265] [ice:0x7########] ICE transport is not running
[1711809855.825|19265] [ice:0x7########] ICE transport is not running
[1711809856.755|19418] [device <DeviceID>] no response from DHT to ICE request.
[1711809857.255|19434] [ice:0x7########] Destroying ice_strans 0x7########


[1711809837.267|19265|manager.cpp             :957 ] ############## START MONITORING ##############
[1711809837.267|19265|manager.cpp             :958 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1711809837.267|19265|manager.cpp             :959 ] Using GnuTLS version 3.8.2
[1711809837.267|19265|manager.cpp             :960 ] Using OpenDHT version 3.1.7
[1711809837.268|19265|manager.cpp             :967 ] Opened files: 107
[1711809837.268|19265] ConnectionManager current status:
[1711809837.268|19265] ConnectionManager end status.
[1711809837.268|19265|manager.cpp             :976 ] ############## END MONITORING ##############
[1711809837.825|19265] [ice:0x7########] ICE transport is not running
[1711809838.807|19265] [ice:0x7########] ICE transport is not running
[1711809839.825|19265] [ice:0x7########] ICE transport is not running
[1711809840.826|19265] [ice:0x7########] ICE transport is not running
[1711809841.826|19265] [ice:0x7########] ICE transport is not running
[1711809842.825|19265] [ice:0x7########] ICE transport is not running
[1711809843.825|19265] [ice:0x7########] ICE transport is not running
[1711809844.826|19265] [ice:0x7########] ICE transport is not running
[1711809845.825|19265] [ice:0x7########] ICE transport is not running
[1711809846.825|19265] [ice:0x7########] ICE transport is not running
[1711809847.826|19265] [ice:0x7########] ICE transport is not running
[1711809848.825|19265] [ice:0x7########] ICE transport is not running
[1711809849.637|19415] PUPnP: Start search for IGD: attempt 3
[1711809849.637|19415] PUPnP: Send IGD search request
[1711809849.825|19265] [ice:0x7########] ICE transport is not running
[1711809850.825|19265] [ice:0x7########] ICE transport is not running
[1711809851.826|19265] [ice:0x7########] ICE transport is not running
[1711809852.430|19415] NAT-PMP: Trying to initialize IGD
[1711809852.440|19415] NAT-PMP: Initialized on gateway 192.168.178.1
[1711809852.470|19415] NAT-PMP: Read response on IGD 192.168.178.1 failed - UNSUPPORTEDVERSION
[1711809852.470|19415] NAT-PMP: Start search for IGDs. Attempt 3
[1711809852.889|19265] [ice:0x7########] ICE transport is not running
[1711809853.825|19265] [ice:0x7########] ICE transport is not running
[1711809854.825|19265] [ice:0x7########] ICE transport is not running
[1711809855.825|19265] [ice:0x7########] ICE transport is not running
[1711809856.755|19418] [device <DeviceID>] no response from DHT to ICE request.
[1711809857.255|19434] [ice:0x7########] Destroying ice_strans 0x7########
        • ring user
          ring user @ringuser ·
          Author

          The Android log is too big to remove private information - can I send them in a PM somehow?

        • ring user
          ring user @ringuser ·
          Author

          I found a solution for private sharing: https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1606

        • Please register or sign in to reply
      • ring user changed the description

        changed the description

      • ring user
        ring user @ringuser ·
        Author

        After some updates on both devices, Jami (snap) now shows the whole user interface with all functions available for this chat. But still, it is not in sync, there are no messages or something else shown and a strange date (or something like that) is displayed: 01.01.70 (German locals. 70=1970).

        01.01.70

      • Sébastien Blin moved from jami-client-qt#1600 (moved)

        moved from jami-client-qt#1600 (moved)

      • Sébastien Blin added BacklogHigh swarm labels

        added BacklogHigh swarm labels

        • Sébastien Blin
          Sébastien Blin @sblin ·
          Owner

          Hi

          Sorry for the long delay to answer, I'm not on Jami anymore, but I get more information and log is useful. Here is the interesting part for the developer that will work on this:

          [1712647812.231|31702|conversationrepository.cpp:2605] Error when retrieving remote conversation: failed open - '/etc/gitconfig' is locked: Permission denied /home/XXXXXXXX/snap/jami/299/.local/share/jami/542f4be0b29ec323/conversations
[1712647812.231|31702|conversation_module.cpp :813 ] Something went wrong when cloning conversation: Couldn't clone repository

          I don't know what can cause this and why the heck /etc/gitconfig is opened. But that's why it doesn't sync on your device for sure

        • ring user
          ring user @ringuser ·
          Author

          My guess: The library you are including in Jami to "speak git" is doing this by default - even if this system configuration file has nothing to do with Jamis usage of git repos. So you should review how you include your git library and how to make sure it does not load or write config files at locations that are outside of Jamis config folders - like it would do likely if it would be used for normal source code versioning.

          In this case I am glad that I am using a sandboxed version of Jami because this does likely cause the inaccessibility of the /etc/gitconfig file and reading this file should not be done by a messenger of any kind. So the sandbox seems to be blocking the access to files that are non of Jamis business.

        • Please register or sign in to reply
        • Sébastien Blin
          Sébastien Blin @sblin ·
          Owner

          What gives ls -la /etc/gitconfig*?

        • ring user
          ring user @ringuser ·
          Author

          I am using the Snap package and Snap has a sandbox - so I do not know if this will help. But if i run $ ls -la /etc/gitconfig* on my Linux system (without Snaps sandbox) I get

          -rw-r--r-- 1 root root 126 ################  2023 /etc/gitconfig
        • Please register or sign in to reply
      • ring user
        ring user @ringuser ·
        Author

        A new test with the same result:

        1. I've created a swarm at my Android device (Account B) and invited my Linux device (Account A).
        2. I've accepted the invitation (account A)
        3. I get an empty conversation view without text entry box and the same error message as before: (Translated to EN) You have accepted the conversation request - waiting until ## makes a connection to synchronize the conversation
      • ring user changed title from Swarm conversation does no load after restoring account backup to Git error causing Swarm conversation not to load (Snap package)

        changed title from Swarm conversation does no load after restoring account backup to Git error causing Swarm conversation not to load (Snap package)

      • ring user changed the description

        changed the description

      • ring user
        ring user @ringuser ·
        Author

        New logs for the new test with the same result: https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1606

      • ring user changed title from Git error causing Swarm conversation not to load (Snap package) to (Git error?) causing Swarm conversation not to load (Snap package)

        changed title from Git error causing Swarm conversation not to load (Snap package) to (Git error?) causing Swarm conversation not to load (Snap package)

      • ring user
        ring user @ringuser ·
        Author

        The new log does not contain the gitconfig part anymore - but maybe, Jami's data are already broken enough so the error persists - or collection logs itself has an error.

      • ring user
        ring user @ringuser ·
        Author

        Maybe related info from the logs: NAT-PMP: Read response on IGD failed - UNSUPPORTEDVERSION

      Please register or sign in to reply