Gajim - 2024-06-02


  1. lovetox

    meson, apart from the one string i marked, is anything open with the voice message MR?

  2. lovetox

    otherwise i would merge it

  3. cal0pteryx

    One last confirmation that it works on Windows, I guess

  4. debacle

    I don't know how you handle plugin versioning, but for me it would be nice, if minor versions get bumped, if a new version is needed for compatibility with Gajim 1.9.0. E.g. for openpgp 1.5.x β‡’ 1.6.x. Thanks for considering!

  5. lovetox

    yes we do this

  6. lovetox

    but only after gajim is released

  7. lovetox

    not before

  8. hermann

    Hi all, is there a way to make emoji's larger?

  9. lovetox

    No

  10. hermann

    thx lovetox, I just found out I can increase the font size and that also increases the emoji size. That's at least something. The default Emoji's are way to small for my eye's πŸ™„οΈ, even though I can read the text just fine If that is an FAQ, maybe it's worth mention it in the Gajim FAQ or Tipps page. I couldn't find this info there.

  11. meson

    > One last confirmation that it works on Windows, I guess Exactly :)

  12. cal0pteryx

    hermann: next version has that

  13. hermann

    cal0pteryx, great, thanks

  14. meson

    elfchen, once you are on your Mac, could you please test for me if ` gst-launch-1.0 autoaudiosrc ! wavenc ! filesink location=audio.wav` picks the right microphone and writes the stream into a file or if the osxaudiosrc plugin is needed, s.t. it reads ` gst-launch-1.0 osxaudiosrc ! wavenc ! filesink location=audio.wav` On Windows `autoaudiosrc` didn't work as hoped, it required `wasapisrc` instead.

  15. Link Mauve

    meson, note that in flatpak (amongst other sandboxing solutions) you might need to use the XDG desktop portal instead of assuming direct access to a capture device, that way it also integrates better with the user’s desktop environment and its permissions system.

  16. meson

    Link Mauve, good point, thanks.

  17. elfchen

    . meson πŸ‘πŸ»

  18. elfchen

    meson πŸ‘πŸ»

  19. meson

    lovetox, should the portal stuff go to gajim/common/dbus? I assume it could be shared with the A/V calls feature later. The only reference in Gajim's code basis to desktop portals I've found in `common/dbus/system_style.py`

  20. meson

    lovetox, should the portal stuff go to gajim/common/dbus? I assume it could be shared with the A/V calls feature later. ~The only reference in Gajim's code basis to desktop portals I've found in `common/dbus/system_style.py`~ I didn't look right.

  21. lovetox

    meson, we can look into how that works with flatpak later

  22. meson

    Alright :) I was afraid it would be a requirement for merging

  23. meson

    Already built the flatpak for testing :D

  24. bot

    lovetox pushed 1 commits to branch gajim/master imprv: AdHocCommands: Display note type icon - https://dev.gajim.org/gajim/gajim/-/commit/181a60da24c3805237789f6dba5d8941760a3709

  25. meson

    cal0pteryx, weird, I must have messed up with git b/c all these print statements etc. I already had removed once. Doing it again. ;)

  26. hbar

    Hello

  27. hbar

    I haven't been able to connect to for past 2hour

  28. hbar

    Iv checked the server and its operational

  29. hbar

    Does not even show an error message.

  30. hbar

    I checked out the XML console and it returns " incoming failure"

  31. hbar

    After "scram-sha1" on the next paragraph of code it says "abort xmlns=" .......

  32. bot

    lovetox pushed 4 commits to branch gajim/master cq: Typings: Fix syntax error - https://dev.gajim.org/gajim/gajim/-/commit/39ecc5a9df4ad24e4aa365f4d114538890a78e5c other: Name all excluded pyright files - https://dev.gajim.org/gajim/gajim/-/commit/07b7b0361e1e7efbfa2cf6d0bd6fad7e484b9d0d cq: Remove obsolete pyright ignore comments - https://dev.gajim.org/gajim/gajim/-/commit/3e528139e5249f31f6eafd60a0f37e1c4caeddd7 ci: Update pyright to 1.1.365 - https://dev.gajim.org/gajim/gajim/-/commit/f560a69e48b5b33a884ae3289cf3bce0d317121f

  33. lovetox

    hbar, seems your password is probably wrong

  34. lovetox

    or the server locked you out for some reason

  35. lovetox

    but you would need to show us more than that

  36. hbar

    I just removed account from gajim and signed in again and it worked. Didn't think of that... lovetox: However on the wrong password point, I logged in, then quit gajim, then opened gajim again, usually when I do so it never has such issues it normally syncs and connects automatically as per my configuration. Probably a bug.

  37. hbar

    Thank you for your assistance. lovetox

  38. cal0pteryx

    "Probably a bug" would have meant: we need more logs to investigate ;)

  39. hbar

    Question. Why doesn't tor hidden services servers connect to conversations.im or any other server for that matter that I have tried.

  40. meson

    I wanted to build a flatpak from the current checked out git branch and I followed the instructions here: https://dev.gajim.org/gajim/gajim/-/blob/master/flatpak/README.md#install-from-source Somehow no matter if I choose `org.gajim.Gajim.yaml` or `org.gajim.Gajim.Devel.yaml`, it always picks version 1.8.4 What do I likely miss?

  41. meson

    I wanted to build a flatpak from the current checked out git branch and I followed the instructions here: https://dev.gajim.org/gajim/gajim/-/blob/master/flatpak/README.md#install-from-source Somehow no matter if I choose `org.gajim.Gajim.yaml` or `org.gajim.Gajim.Devel.yaml`, it always picks version 1.8.4 What do I likely miss? What do I need to further adjust, which isn't written in the readme?

  42. lovetox

    the version will always be 1.8.4

  43. lovetox

    thats the current version of gajim

  44. lovetox

    you need to take the devel

  45. lovetox

    hm the devel yaml takes the code from gitlab

  46. lovetox

    no idea how you can point it to your own repo

  47. ong

    u can do file or directory: instead of url: for git repos on flatpak

  48. meson

    yep, it worked + add a branch property to git repo

  49. meson

    yep, it worked + added a git branch property

  50. cal0pteryx

    meson: if you do further changes, please do then in another branch

  51. cal0pteryx

    Otherwise we won't finish this MR

  52. cal0pteryx

    It's okay to merge and improve things afterwards :)

  53. meson

    cal0pteryx, alright, I won't touch it anymore :P

  54. meson

    Interestingly recording just works with the built flatpak, and I haven't even given it access to the mic according to flatseal. I don't understand it completely, but yeah.

  55. meson

    apparently it uses the pulseaudio sound server for it. Taking its access to it, yields recording silence and trying to stop the recording makes it freeze >_<. Aw

  56. bot

    lovetox pushed 1 commits to branch gajim/master cq: Ignore some pyright errors - https://dev.gajim.org/gajim/gajim/-/commit/8d3051aaff8003be5f481ec1fb030a8bf7ff68d1

  57. meson

    > apparently it uses the pulseaudio sound server for it. Taking its access to it, yields recording silence and trying to stop the recording makes it freeze >_<. Aw I eased it by handling the error, though it shows now the player on start, which is not supposed to happen. But anyway, it doesn't crash any more and shows an error text instead

  58. lovetox

    you can simply disable the recording on flatpak for now

  59. lovetox

    check app.is_flatpak()

  60. meson

    Ok, let's do that then.

  61. Link Mauve

    meson, the right way to do that is to use pipewire directly, that way there is no need to poke holes in the sandbox, nor to disable anything.

  62. Link Mauve

    It should just work.

  63. meson

    Link Mauve, I guess that's why it just worked: autoaudiosrc just picked pipewire

  64. meson

    I wanted to see what happens if the user takes away access to pulseaudio/pipewire via flatseal. Though that is likely an unlikely scenario

  65. lovetox

    so what now, does it work now or not

  66. lovetox

    users dont play with flatpak config, and if they do they are on their own

  67. meson

    it works and fails gracefully if yo take away the access to pulseaudio/pipewire via flatseal

  68. meson

    then we are fine

    πŸ‘ 1
  69. meson

    > meson, the right way to do that is to use pipewire directly, that way there is no need to poke holes in the sandbox, nor to disable anything. Since this probably means it won't work for people who use flatpak _but not_ pipewire, we need to look into poking holes for pulseaudio / alsa / jack users, later, right Link Mauve?

  70. Link Mauve

    meson, these holes would be huge, I think you can leave that to flatseal.

  71. Link Mauve

    Whereas pipewire requires no special hole whatsoever.

  72. meson

    great, less work!

  73. Link Mauve

    One of the main reasons to write pipewire was to actually do permissions right this time.

  74. meson

    :)

  75. Neustradamus

    Link Mauve: I search the Omnipresence source, used by https://presence.jabberfr.org/. Can you help me because badly CodingTeam is dead since a moment? Thx

  76. Link Mauve

    Neustradamus, it should be here, but this isn’t the right place for that kind of query: https://git.jabberfr.org/omnipresence.git/

  77. Neustradamus

    Thanks! You have not answered me at another place ;)

  78. Codimp

    I'm looking again on a problem I have: I have 2 computers connected to the same account using Gajim with an OMEMO key for each one. The computer A can send encrypted messages to computer B, but computer B can't because it can't see the other OMEMO key (the key of computer A). Did someone got the same issue? And found a solution?

  79. ong

    has computer B send a message to computer A yet?

  80. ong

    has computer B sent a message to computer A yet?

  81. Codimp

    yep

  82. ong

    try

  83. ong

    spamming send message

  84. ong

    to computer A from computer B if u can

  85. Codimp

    ok just fix it in facts :D I need to disconnect and close Gajim on computer B, then reopen it, and now when I send a message from computer B to A it ask to verify the OMEMO key of computer A

  86. Codimp

    and now it works as expected

  87. ong

    oooooooooooo

  88. ong

    based

  89. Codimp

    yep but wasn't working before I think, I remember already trying that without sucess

  90. Codimp

    very strange sometimes