Gajim - 2025-02-12

> its broken for a long time, because flatpak has problem building in a VM I was willing to install the nightly build of gajim (on my Raspberry Pi, where such testing/experimentation has no effect on my daily driver laptop), since there is an unoffical apt source for it 👍 , but alas, there is no ARM64 build at this time 👎️ ↺

Personally, I'm not a fan of VMs, as they indeed tend to introduce strange, unwanted side effects - making it hardly worth it, or even worse, subtle footguns come out. My sense now it do use Raspberry Pis wherever possible, where I might have been tempted in the past to use a VM. Then it's at least on bare metal - although of course there can be subtle bugs arising out of the difference in architecture (AMD64 -> ARM64). ✏

Personally, I'm not a fan of VMs, as they indeed tend to introduce strange, unwanted side effects - making it hardly worth it, or even worse, subtle footguns come out. My sense now, is to try to use Raspberry Pis wherever possible (sparing one's daily driver for the sake of stability), where I might have been tempted in the past to use a VM. Then it's at least on bare metal - although of course there can be subtle bugs arising out of the difference in architecture (AMD64 -> ARM64). ✏

Thanks for the reply lovetox, yes there are hundreds of MUCs indeed. I will try portable master, I did not realise there were continuous builds for windows.

esbeeb, Gajim is a pure Python program, and the package is correctly being built for all architectures.

It’s the python3-omemo-dr package which is built only for amd64.

On my Raspberry Pi I have Raspberry Pi OS (Debian-based),and the options I see available are the old apt package 1.7.3, and then the flatpak for 1.9.5. Can anyone suggest an ARM64 route for non-flatpak, which doesn't need to be built from source?

esbeeb, does it ship python3-omemo-dr?

I see there is a trixie debian package for python3-omemo-dr. But bookworm (which Raspberry Pi OS is currently based on)? No.

Not even in the backports?

debacle does maintain Gajim quite well, and backports what can be usually.

OK, I see a backported package:

https://packages.debian.org/stable-backports/python3-omemo-dr

There you go. :)

OK, I followed this guide to enable Debian backports in Raspberry Pi OS (bookworm):

https://www.complete.org/installing-debian-backports-on-raspberry-pi/

But the gajim I got from there was 1.8.4

1.84.is arguably better than 1.7.3

esbeeb, oh you didn’t want to install gajim from Gajim’s repository? Since it’s available for all architectures that should work. ✏

> esbeeb, oh you didn’t want to install gajim from Gajim’s repository? Since it’s available for all architectures that should work. Are you talking about using the repo as explained here: ↺

https://gajim.org/download/#linux

In the section "Nightly package from git (Debian, Ubuntu)"?

When I did that, I got an error message that there were no builds for my architecture.

Here's the error from "sudo apt update":

N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'https://ftp.gajim.org/debian unstable InRelease' doesn't support architecture 'armhf' N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://ftp.gajim.org/debian unstable InRelease' doesn't support architecture 'arm64'

esbeeb That's an error in the repository, indeed. It behaves like it were only for amd64 and i386.

esbeeb As a workaround, you could download the relevant packages from https://ftp.gajim.org/debian/dists/unstable/main/binary-all/ (e.g. using curl or wget) and install them with `dpkg -i`.

For now, I decided to do the simpler thing which was to use your backport of Gajim 1.8.4. The file upload feature *does* work to my Prosody 0.13 server, which is what I was needing and expecting. This uploading works in AMD64 (1.9.5 flatpak), and ARM64 (1.8.4 from backport)

So I'm happy, and thank you all for your support! I appreciate your efforts.

esbeeb, what was the issue with uploading?

> esbeeb, what was the issue with uploading? Please see: ↺

https://c.im/@sbb/113984964797724874

...and:

https://c.im/@sbb/113990143676763578

esbeeb, thanks, it’s indeed extremely weird that Gajim would fail where Dino would work on the same computer and network.

And there is another user who says they’ve spent three days on the same issue?

Yes, I agree! The problem went away on it's own.

Y’all should report such bugs instead of spending days on them. ^^'

I hope it doesn't come back

> esbeeb, thanks, it’s indeed extremely weird that Gajim would fail where Dino would work on the same computer and network. Yes, Gajim and Dino on the very same computer and network. ↺

That’s why I don’t recommend using distributions shipping obsolete software, bugs get fixed and users continue running two, three, five years old versions just for the sake of it.

It's Gajim 1.9.5 from flatpak, where the paperclip went grey on me for a period of time...

Tooltip became "No File Transfer Available"

And do you see it available in Accounts > Server Info?

I've dug up a very subtle bug for you

Here's hjow to reproduce. The paperclip icon is somewhat sluggish in recovering from being offline, if Gajim was first launched in an offline state. The paperclip will remain greyed out until you 1) go back online *AND* 2) switch to some other contact. Then come back to the contact where you had the greyed-out paperclip. And now it's usable again.

Gajim is polite enough to notice you're offline when you first start, saying "You are offline. Go online to send messages...". Then once you go online, it'll say "Joining..." with a swirling circle, with a little semi-transparent background. But these politenesses once one's gone back online doesn't extend to making the paperclip clickable again, until you click some other contact, and come back again.

Dino *is* polite enough to auto-magically make its own paperclip re-appear again, once you're online. Thus my confusion. ✏

> And do you see it available in Accounts > Server Info? Oops, my prosody server is 0.12.3, not 0.13. But anyway, I've found your bug ↺

esbeeb: this sounds like a bug on Gajim side

I will check if we still have this in master

Thanks. Much appreciated!

> N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'https://ftp.gajim.org/debian unstable InRelease' doesn't support architecture 'armhf' > N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://ftp.gajim.org/debian unstable InRelease' doesn't support architecture 'arm64' > If the arm64 builds are restored in your apt repository for nightly builds, I'm willing to do a test install on my Raspberry Pi to verify. ↺

Hello, does anyone know why XEP-0209 (https://xmpp.org/extensions/xep-0209.html) was removed from gajim ?

benjamin: because it caused more issues than benefits

Hello

I try to find information to use openpgp with Gajim. Can someone maybe give me a hind where I can find it?

on what system are you?

Linux and Android and Windows 😁

there are 2 plugins

pgp and openpgp

which use both the gpg executeable if installed on your syste

the pgp plugin is the one that uses the protocol that has the greater support in other clients but just uses a pgp keyring you need to setup and manage yourself

while the openpgp plugin manages its own keyring, and you cannot bring your own key

Tbh is it normal that the openPGP plugin is broken on flatpak? It's broken for me and a friend

https://hypertext.telepath.im/file_share/0Y1ICiu2VXYVHGrgzW1h3MLQ/0fa91b69-5395-416a-9904-a8187b224e35.png

This is the error btw

I don't mind using the normal PGP plugin I am just currios

> while the openpgp plugin manages its own keyring, and you cannot bring your own key also iirc it does presence signing which allows other users to discover your keys? something like that. I remeber someone mentioning it to me a while ago ↺