Gajim - 2025-04-19


  1. bot

    lovetox pushed 2 commits to branch python-nbxmpp/master cfix: Retraction: Fix tests - https://dev.gajim.org/gajim/python-nbxmpp/-/commit/d17a701b8d1a3af0cada8754e84f98661c1a1980 ci: Run unittests in CI - https://dev.gajim.org/gajim/python-nbxmpp/-/commit/66caec1241047283186280e602dd506ec462b18c

  2. bot

    lovetox pushed 1 commits to branch python-nbxmpp/master ci: Print verbose unittest results - https://dev.gajim.org/gajim/python-nbxmpp/-/commit/70c06bc0f738b4318ebde6932600201b092067ba

  3. AsyncTh

    I have some kind of weird issue with Gajim not being able to connect to the server I'm using (Conversations connects to it fine). Any ideas how I can try to figure out the reason? I tried looking at the terminal output and at the debug console, I'm not seeing anything relevant there.

  4. lovetox

    Start gajim with -v and show us the output

  5. AsyncTh

    I think I actually figured out that this issue only happens with Direct TLS and curl doesn't seem to be able to perform a TLS handshake either

  6. lovetox

    Then report it to the server admin

  7. AsyncTh

    But anyway, from the output: TCPState is set to CONNECTED and the StreamState is also set to CONNECTED, then "Start TLS negotiation" and "Start stream" messages, then StreamState is set to WAIT_FOR_STREAM_START, a stream header is sent, messages for signals data-sent and stanza-sent - all from Account Wizard.

  8. AsyncTh

    Should I try to copy the output? It's just that I'm typing on the phone, but I'm trying to log in on PC

  9. AsyncTh

    Well I tried it one more time and this time the client received the response stream header, but no response to auth XML element

  10. AsyncTh

    https://paste.debian.net/hidden/a486d3ab/ This was the first output

  11. lovetox

    Looks fine and what happens afterwards

  12. AsyncTh

    The first time nothing happened after that

  13. AsyncTh

    The second time, it got until the point of auth XML element being sent, then nothing was happening except keep alives

  14. lovetox

    Sounds like a server issue

  15. lovetox

    Maybe ask the admin to look into server logs