This doesn’t happen in other distros so far, though I haven’t tested discord on other distros’ KDE versions, as I normally don’t use KDE. An example of one of the GIFs that’s crashing me every, single, time, I hover over it is this one: Crusade Thinking GIF - Crusade Thinking Meme - Discover & Share GIFs
Sometimes after crashing, discord will crash when it tries to start up, and will do so about 8-10 times before it finally starts up properly. I don’t know what’s going on, and don’t know how to fix it.
After turning off hardware acceleration, it still crashes. This was an old issue on fedora with hardware acceleration, so I decided to try that, but it didn’t work.
Reinstalled openSUSE to check to see if it crashes in XFCE. it does, much worse than in KDE. It completely hangs when it tries to restart itself, showing a blank screen. After terminating it through task manager, it will refuse to start now, showing the spinning discord logo forever.
After restarting, it no longer hangs, and can be restarted after each crash, but it still crashes. This definitely seems like it’s an openSUSE package issue, and not specifically tied to a DE/etc.
Did you install Discord from OpenSUSE’s repository or from Packman? I have the one from Packman and it’s not crashing for me. I even tried the gif you posted. The flatpak version is also worth a try if you haven’t already tried it.
Yep, I just uninstalled the one from Packman and installed the one from the main repository and it immediately crashed the moment I pasted the link of the GIF in your post.
Sorry, I prefer native packages. So flatpak is out of the question. (I even have flatpak backend removed.) It would be nice to see it fixed in the main non-oss repos like fedora/arch/etc.
Packman is a frequent source of issues with updates. You will experience issues and must be confident to resolve these.
If possible, only add the essentials repository.
Is also a serious warning that I don’t want to ignore, especially on a supposed “Rolling Release” distro.
Using discord myself, I just use the version distributed by Discord as a tar.gz and unpack it and use it that way, updating when it says there’s an update on startup.
Haven’t had any issues with doing it that way (I’m running it on Tumbleweed as well).
Just as a note, I won’t accept this as a solution. So don’t mark it such just before the 30 days are up. The solution is to have the maintainers of the non-oss package update discord to the repos as per the bugzilla bug.
@coldreactive So there is a new release available, can you confirm and if so as requested close the bug report. And you can just bump the post if wanting to keep it from auto closing.
We generally leave the solution marking to the person who created the topic. Staff can identify a solution, but it’s extremely rare that we do (in fact, I don’t know that we have since we enabled that functionality).
If the 30 days runs out and you want to add to this, you can always link to this topic in a new one - in fact, if you click the share button on the topic itself, one of the options is to create a new topic. This topic will then also have a notification that it’s been linked to a new topic.
Since OP haven’t responded yet, I went ahead and tested the one in the main repo (version 0.0.66-1.1) and the one from games:tools repo (version 0.0.66-148.1). Unfortunately both still crash when hovering over or opening GIFs.