Error on Discord

I am coming from Windows 10, and one of the tools I use in my daily life is Discord.I get this error after taking a break and returning from the lock screen.I have Discord installed from the software store; in fact, whenever possible, I try to install everything from there to avoid compatibility issues or errors.I want to know if it's just me or if it's a general error of Zorin OS/Ubuntu.Thanks in advance.

When You have downloaded it from the Software Store: Is it the Flatpak Version? If yes, I would suggest to try the .deb Version directly from Discord:

Looks like you're not the only one:

I tried it with the Flatpak version and with the package downloaded from the official website; it happens on both X11 and Wayland.

https://support.discord.com/hc/en-us/articles/32556110769943-Discord-Error-Message-Guide

For Windows on the discord website is recommended to delete %appdata% >discord and %LocalAppData% >discord and then to reinstall discord. Maybe someone can tell you the corresponding directories in Zorin?

Looks like a known issue that sometimes happens with the repo version. You might want to try the Flatpak build or grab the official .deb — in most cases they're much more stable. After installing, give your system a reboot just to be safe.
Also, if the issue persists, it can help to launch Discord from the terminal once and check if it throws any specific errors — that usually points you in the right direction.

not work my friend..

This also happens to me. I am on a laptop.

Usually happens after screen has been off for a while.

Yes, have tried first flatpack, then .deb.

Will now try edit sleep.conf in /etc/systemd

AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore

I'll tell how it goes.

Edit: Didn't help. Still an issue when leaving computer for a prolonged period

As this is a Discord specific issue (It is trying to write or stream to a closed pipe and crashing when it attempts to log it), the only course is pressuring the Discord developers with bug reports.

1 Like

I've submitted a bug report.

This bug happens on all Linux distros?

From what I can tell, it happens on several, but I have not scoped out a common connection - like if only on Debian based Distros.

It seems, as bugs often do, to rely on a variety of actions and factors to combine in the right way, for it to manifest. I am not an electron app developer, though and offer a Novice Observation.

I've now had it happen twice after two attempts at reinstalling Zorin OS.

Installed Mint and been running a day without issue. Installed the same apps, Virtualbox, ect.

I have the same problem, after screen lock the discord broken.