Gajim - 2024-08-10


  1. novice8

    Hello, I am unable to "verify" an OMEMO key. Here is the exact situation. I added account X to Gajim (Linux Manjaro if it matters). When X (in Gajim) sends an OMEMO encrypted message to Y (also in Gajim), Y can "verify" the key fine. Now, I added X to an Android (app: Pix-Art Messenger). When X in Android sends out a message, Y in Gajim can (still) verify but X in Gajim cannot verify (which is to say X cannot verify itself as residing in another device).

  2. novice8

    By "cannot," I mean that I mean that, when X in Gajim clicks the shield icon, the key fingerprint for X in Android is not listed. What I expected was to see it listed in red so that I may "verify" it.

  3. novice8

    Graphically speaking, any message sent out by X in Android shows up for X in Gajim with a red shield with an exclamation mark inside (which I believe means "unverified).

  4. novice8

    Question: How can I get the fingerprint of X in Android to show up in X in Gajim? Sorry, that was long.

  5. mittwerk

    hi all

  6. fjklp

    mittwerk: hi

  7. lovetox

    Red does not mean unverified

  8. lovetox

    Hover the icon to see what's up

  9. lovetox

    And also in the fingerprint window there is a toggle to show inactive devices

  10. novice8

    @ lovetox: "Hover the icon to see what's up" > It says, "Trust Not Decided." Thanks.

  11. novice8

    @ lovetox: When I went to see the inactive devices, I found the earlier missing fingerprint (of X in Android) has appeared and been trusted (without my doing anything further). I believe I choose "trust blindly" whenever I could, and so my Gajim may have been set to do that.

  12. novice8

    Does that (a fingerprint appearing as trusted some time later) something one might expect to see happen if certain conditions (at the servers etc.) are met? Or one of those mysterious things nobody can explain?

  13. novice8

    (By the way, new messages all have solid green shields. I.e. problem is fixed if that was not clear from the above. Thanks again.)

  14. bot

    wurstsalat pushed 1 commits to branch gajim/master fix: MessageRowActions: Make actions more robust - https://dev.gajim.org/gajim/gajim/-/commit/6780f9f5acb0586ae9309240dd8d8ad2b29fe2ca

  15. bot

    wurstsalat pushed 10 commits to branch gajim/master https://conference.gajim.org:5281/pastebin/15066fff-747d-4814-8258-7f692107ec62

  16. bot

    wurstsalat pushed 1 commits to branch gajim/master cfix: Fix import for _xmpp_query_type_handlers - https://dev.gajim.org/gajim/gajim/-/commit/cddfa51425ba8a18c6d1b08e522adff91a751111

  17. hueso

    pinpointed my MAM problems to a server issue. sorry for bothering you

  18. cal0pteryx

    hueso, thanks for the feedback

  19. hueso

    I also had a problem of repeating messages. Once in a while I receive a bunch of repeated MUC messages upon reconnecting. It might be related to the MAM issues (mnesia DB was full)

  20. lovetox

    I have this also sometimes for pm on ejabberd servers

  21. betarays

    When clicking on a channel with unread messages, is there any way to make Gajim either start at the first unread message or show a bar between read and unread messages?

  22. betarays

    Apparently it just goes to the bottom without any indication of where you were before

  23. betarays

    (note that I’m still on 1.8 as arch linux didn’t release 1.9)

  24. fjklp

    no

  25. lissine

    betarays: I think this MR does that https://dev.gajim.org/gajim/gajim/-/merge_requests/960 You can build Gajim from the MR's branch