Justin Yes , well I tried to run it without terminal again and it crashed, bugged me ingame but not for too long.
I am now again running with terminal only getting those for now, but i'll keep updating if it quits.
Btw, in one of your posts i saw you mention the new call of duty modern warfare, do you have or already tryed to get the new Warzone battle royal mode to run on linux?Can't get any info on it yet.

    Justin

    Failed to get crash dump id.
    Report Id:
    Segmentation fault

    laky I've got MW but I don't think it's Linux friendly. Mind you I haven't looked in a while. I keep Windows for this purpose.

    As for the crash segfaults are not my specialty and need the dbginfo packages to help you debug it. Hopefully someone with that kinda knowledge comes along to assist soon.

      I've been having this problem too. It mostly happens when I'm in a call. I'll run discord from the terminal for a while and see if I can collect any info.

      Justin I will resarch more about that matter with time i should get my answers regarding MW and linux.
      I never done debuging stuff but that might help here since there is nothing currently helping , i was playing for like 1 h untill it crashed again randomly even with HW acc enabled no changes.
      Thanks very much for your efforts helping me 😃

      On reddit someone suggested to use ripcord instead. It has an appimage, so also on Solus it should run fine. I haven't tried myself, but just in case it's a nice alternative for anyone having these discord issues.

        As I said, it happens quite a lot. So here's my output:

        Crash dump id: 69e266cd-4618-4a21-847f-c3bc3244ecb9
        Segmentation fault

        It's the same as @laky 's output, but I got an ID. Does anyone know where I can find the crash dump?

        I've read somewhere on forums about this problem, and one of the comments was to try installing flatpaks version of discord, is that possible here on Solus?

        Snoober I did something similar for wine-staging repository might actually try install flatpaks repo and try it out..Btw , how do you mean again? You already had flatpaks discord installed or was it something els you needed it for?
        Edit: Okay I got this
        Application ID Version Branch Remotes Description
        com.discordapp.Discord 0.0.10 stable flathub Chat client

        Now how did you install it?
        Edit2: Nvm , I managed to install it now i am going to test it out . Is it not possible to run it from terminal anymore after you install the flatpak version? running discord in terminal does nothing now.

          laky I can't remember I think I used flatpak before (maybe when I was using another distro).

          To run in command line do flatpak run [app name] so:

          flatpak run com.discordapp.Discord

            Snoober It just kicked me again with flatpak discord.. Its something to do with discord team.

              laky I'd suggest like Josh said to report it to them.

              • laky replied to this.

                Justin I am now waithing for them to answer , with info i gathered so far.
                Tnx to Josh for pointing that out. 🙂

                I got an answer from Discord team via email i send them. This is what they replied:

                I'm very sorry to hear that you're having trouble using the Discord app while playing games within your Linux machine.

                Could you please try to completely uninstall the client and reinstall it through the use of sudo make uninstall in your distro's terminal?

                If you continue to experience this same issue with our updater upon reinstall, let's see if the issue persists in our Public Test Build. You can grab our PTB client here!
                If you're using Deb: https://discordapp.com/api/download/ptb?platform=linux&format=deb

                If you're using Tar.gz: https://discordapp.com/api/download/ptb?platform=linux&format=tar.gz

                Here's also Github with some common fixes to some of the issues in the Linux version https://github.com/simoniz0r/Discord-Linux-Client-Issues.

                Give these steps a shot and let me know how it goes.

                I wonder is it safe to use this tar.gz and compile it in Solus, in other words how would this work?
                Edit: Safe thing aside, i have run it and going to test it from there.

                18 days later

                I can confirm Discord crashes incessantly and dozens of other people have come out of the woodwork to report it, which is a Discord problem. I am posting here to say @laky that I stopped the crashing on my system by turning ON 'Minimize to tray' (ENABLE). lol Hope that narrows down workarounding on Solus.

                  JohannPopper Hey funny thing is that probably won't stop it from crashing, but the most recant info about a workaround that i got involves couple more things to be disabled atleast it did for me. If you get anymore crashes try this:
                  Voice & Video - For INPUT SENSITIVITY and disable "Automatically detemine input sensitivity." (set it yourself)

                                        "OpenH264 Video Codec provided by Cisco System, Inc." (disable)
                  
                                         "H.246 Hardware Acceleration" (disable) 
                  
                                          "Enable Quality of Service High Packet Priority" (disable)

                  Notifications - "Enable Desktop Notifications" (disable)

                                       "Enable Unread Message Badge"(disable)

                  Game Activity - (have this disabled at all times)

                  Streamer Mode - "Enable Streamer Mode" (disable)

                                           "Automatically Enable/Disable" (disable)
                  
                                           "Disable Notifications" (disable)

                  Hope it helps! 🙂 (Notifications having disabled is 99% of the problem which fixes it,well maybe...)
                  Edit: This is just my settings not sure is all of this needed, 'Minimize to tray' is enabled for me too but that alone didn't fixed it.