Discord and Anytype displaying errors if I close my screen

Hey Guys,

I just moved to Zorin OS to avoid going to windows 11, so this is my first linux experience. My machine is a Lenovo IdeaPad 3 14ALC6.

Whenever I'm using discord or anytype, if I close my screen during my session, I start getting these error messages below. One is with wayland and the other with xorg. Is there a fix for these?


Let me know if need more information. Please help me out if you can.

I'm not really sure what may be causing this, maybe the package format used to install them. For Discord, for example, you can install it either from the Software store as a so-called "Flatpak" or download it from their website directly and install it as "Debian package".

Don't worry about what these are right now, they are just different ways to do the same things, although with some nuances. It may not be related at all, but I think it's worth trying installing Discord, as a test, from their website.

Here is another thread with some instructions, and extra context:

I suspect that this is specific to Electron built applications.
When you close the lid, this induces either suspend or sleep, which halts the process - the Electron app loses connection to the socket.
While this is more likely to occur on Wayland, it can happen on X11, too.

I just did a search and found an open bug ticket:

I was looking for a fix.

Welp.

As a workaround, you can mask the process that get halted:

sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

Hey guys,
I forgot to check here for replies,my bad.
I'll try this fix for now.

I worked around discord by making a web app with zorin's utility, but I can't do that with anytype. Hopefully this gets fixed soon! Sadly it happened once while I was showing how linux is "much more solid now" to a friend :clown_face:. It was really unfortunate.

Hi zenzen, thanks for the reply!

I installed discord from the deb file, I still don't know a lot about the package managers themselves, but it occurred to me that it could've been a bad install. Sadly it wasn't. Hopefully it gets fixed soon because I intend to use anytype more frequently.

1 Like