(I’m the maintainer) I do use the messenger bridge and it works for me, without disconnection issues.

But what is dead may never die!

Nah, because it’s like no text for 30 secs, then “3 lines per second” (faster than you can read), then more or less synced, then again too slow/too fast. That teletext explanation someone else gave is more plausible. I cannot believe that the original are that bad, so my guess is that the way they’re ripped has issues.

Yes, it’s totally fantastic, and I’m not biased at all when I talk about it. xD

It does support a crazy amount of networks (it uses libpurple which is the lib of pidgin), unfortunately it lacks modern features and even groups don’t work that well. I actually started to work on slidge because I was fed up with spectrum2’s limitations and realised that spectrum2’s maintainer think, like many others, that XMPP is dead…

Oh that “teletext” thing I guess, I get it. I remember using subtitles from this source in France in the 90s, and it was never that off sync. I guess the way they’re ripped may make the offsyncedness worse.

The very definition of fascism yes, nazism being “commenting on articles without reading them”, and communism obviously being “being triggered by feminism”.

Sounds like a dream. Try JIRA tickets and MS Word.

It’s excellent. Too bad there is no lidarr integration yet. I manually run beet import once a download is done, but I’d like to automate that at some point.

I use beets and soulseek but my ambitions are lower than yours.

I think this is unlikely because it’s only this specific device that crashes, and the others are fine?

No, good old SSID+passphrase. But this PC is connected via ethernet (although the mobo does have a wifi chip, that I don’t use).

Nope, I don’t know the first thing about these tools, but now I’m kind of impatient and hope that the next freeze happens soon so I can try. :-)

I would suggest airvpn over mullvad as they allow port forwarding, which will make torrenting work better.

Everything is 2 yo, so this would mean the mobo (well, the onboard ethernet thing) was malfunctioning from the start. Maybe!

I might try disabling and using the onboard wifi chip temporarily instead, just to see if I notice a new freeze. The issue is, I’ve never understood what triggers it, and it’s quite rare (less than once a week), so it’s really annoying to debug…

I like my debian vanilla but thanks for the suggestion. The other network card would be interesting to try out. I don’t really suspect the network card, since I have no idea whether the network block is a consequence or a cause here.

Nope. May I ask what would be the connection with my issues?

Updating. I’m willing to try your solution but I am a little bit worried about not being able to reinstall anything after I sudo apt remove network-manager. Why would a package reinstallation help? Wouldn’t resetting the config files be more efficient btw?

EDIT: Ce n’est pas update sur update, y a juste eu bullseye (d’abord testing, puis stable), puis récemment je suis passé à bookworm. Mais le soucis est là depuis le début. Il est pas trop chiant parce que c’est rare, mais quand même ça m’enquiquine.

Oh this would explain why it kills the connectivity of all ethernet-connected devices. The ethernet interface is the one on the mobo. Drivers are included by the linux kernel AFAIK. The problem persisted across 2 debian versions so I am not sure re-installing drivers would do anything here. But thanks for the plausible explanation about the network issue!

This has been happening for 2 years, with the previous debian version too, so I doubt this would do anything?