Gajim - 2025-02-10

hi

i am having issues with gajim nightly

Error: Package 'gajim-nightly' has no installation candidate

i did

``` sudo apt remove gajim wget -qO- https://gajim.org/gajim.key | sudo tee /etc/apt/trusted.gpg.d/gajim.asc sudo sh -c "echo deb https://ftp.gajim.org/debian unstable main > /etc/apt/sources.list.d/gajim.list" sudo apt update sudo apt install gajim-nightly ```

where can i download .deb package?

It's broken currently

how can i get debian package?

is there any instructions on how to build a deb package on my own system?

*Memory* A long time ago, there was an indication in the group chats as to which message had been read. Is such a hint planned again? It would be a great help to me.

donnerwetter: it might be implemented at some point. There is a merge request in that direction

> it might be implemented at some point. There is a merge request in that direction cal0pteryx, Thank you for your feedback. I'll have to be patient a little longer 😉.

does gajim support editing of muc icon?

why is it impossible to see chat history?

Scroll up to load more chat history…

but there's none

you can only load more chat history if you have it in your database

https://conference.gajim.org:5281/muc_log/gajim/

here if you need history from before you joined here

rak, yes in the chat settings under tab "Manage"

justforgajim, debian package should be soon available again

when bro?

probably in the night

aight

I am having a hard time debugging a windows-specific gajim 1.9.5 breakage, possibly caused by my MUC component (gateways). I'm writing the current state of my investigations in case anyone has an idea because I'm out of them. - It was working fine for months and gajim was not updated recently. Since a few days back, on startup, gajim either (a) freezes or (b) eats all CPU without freezing but fails to receive or send anything on any account. - After wiping the data folder, I narrowed it down to this account where there are hundreds of autojoin MUCs in the bookmarks (a whatsapp bridge for a very old whatsapp account - a loooot of groups) - Examining the logs, I see that gajim sends a lot of disco#info queries to the MUCs which are unanswered, possibly a bug in my MUC component implementation. But why would this kill gajim like this? When not frozen, I can see the MUCs are "joining", but why would that prevent 1:1 message to go through?

It gets weirder: - Logging in to the same account from Gajim 1.9.5 on debian stable causes no trouble (so my component does answer to the disco queries, but not when they come from windows? that does not make sense ofc, but this is what it looks like) - Logging in to the same account from Cheogram (=Conversations) causes no trouble either.

There is definitely a bug in gajim somewhere, but I haven't managed to gather enough accurate information for a useful bug report. There _might_ be a bug in slidge's MUC implementation too but I am not convinced it is the case anymore (I was convinced at first) — in any case, this should never make gajim unusable, right? And why is the issue not present with the same gajim version launched from linux? This boggles my mind. I did capture a massive debug log from windows, anonymizing it is nearly impossible. devs, let me know if you are interested in seeing the log: I don't mind sharing the log privately.