Open The-annonymous-guy opened 18 hours ago
also crashing the game when i try to close it, forcing a reboot. Before this, some artifacts happen, and the program suddenly closes.
This sounds like a deeper problem outside of EasyEffects. Even in a situation where EasyEffects crashes the game will keep running because PipeWire will redirect it to another output device. Is there something related to EasyEffects in the output of sudo coredumpctl list
? Do you have killed
messages in the output of sudo journalctl -b
right after the crash?
sudo coredumpctl list
only displayed "no coredumps found", and no killed messages with sudo journalctl -b
.
One thing that is worth mentioning, is that the problem seems to go away if easyeffects is executed with G_MESSAGES_DEBUG=all flatpak run com.github.wwmm.easyeffects
, but Sober still needs to be closed via system monitor, because it still crashes.
sudo coredumpctl list
only displayed "no coredumps found", and no killed messages withsudo journalctl -b
.One thing that is worth mentioning, is that the problem seems to go away if easyeffects is executed with
G_MESSAGES_DEBUG=all flatpak run com.github.wwmm.easyeffects
, but Sober still needs to be closed via system monitor, because it still crashes.
Hum... Usually there is a coredump or in the case where the system decides to kill the process a log message telling that it killed the application. Try to run EasyEffects in debug mode https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#basic-logs so we can see what it is doing when it stops working.
In this time, coredumpctl results in:
Sun 2024-10-20 19:21:50 -03 4838 1000 1000 SIGABRT present /app/bin/easyeffects 12.6M
Sun 2024-10-20 19:47:38 -03 16017 1000 1000 SIGSEGV present /usr/bin/dolphin 4.3M
Sun 2024-10-20 19:21:50 -03 4838 1000 1000 SIGABRT present /app/bin/easyeffects 12.6M
What is the output of sudo coredumpctl info 4838
? Assuming you also have installed the package that provides debug symbols
for easyeffects the output should give some idea about what is going on.
EasyEffects logs seem fine. And the signal SIGABRT
might mean that libc decide to call abort for some reason.
Assuming you also have installed the package that provides debug symbols for easyeffects the output should give some idea about what is going on.
I always forget that in Flatpak packages coredump information has to be extract in a different way. You will have to do what is explained at https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#with-flatpak.
By the way it might be interesting to try with a native Fedora package instead of Flatpak. Sometimes problems happen on one package but not on others.
Using the OpenSUSE package seems to resolve the issue, but unfortunately it's not the latest version.
Based on on the coredump the issue is somewhere inside libc
. It seems to be indeed doing the abort call. Considering that a native older package works maybe there is some kind of incompatibility between the Flatpak package and the libc version currently being used by OpenSuse.
EasyEffects Version
7.1.9
What package are you using?
Flatpak (Flathub)
Distribution
OpenSUSE
Describe the bug
Everytime i try to play roblox (using sober) with easyeffects, the app crashes, also crashing the game when i try to close it, forcing a reboot. Before this, some artifacts happen, and the program suddenly closes. No error messages displayed.
Expected Behavior
No response
Debug Log
Debug Log
``` Paste your log here ```
Additional Information
No response