Installed steam to play some games and turned on proton experimental compatibility as usual and the game ran fine as expected. What I just noticed is that easyeffects was no longer launching - it basically showed the loading icon and then nothing happened. In this moment I had no idea that Steam was causing this so I started looking around on the internet to see if anyone else had any issues like this and was disappointed to see no solutions or anyone even facing this issue.
So I ran easyeffects via the terminal and got this error on the last line.
wl_drm#47: error 0: wl_drm.create_prime_buffer is not implemented
Which I found was related to GPU drivers. So as a last ditch effort I uninstalled Steam along with any installations of proton, battleye and vulkan(folder) to see if that works and voila! it worked and easyeffects launched with no issues whatsoever.
I don’t game like ever so this was my first Steam installation. Anyone have any clue why this may be happening? I am not very familiar with troubleshooting linux stuff. Making this post so that if anyone else wonders why their easyeffects no longer launches seemingly randomly.
How were EasyEffects and Steam installed on our system?
Official Arch Repos, AUR, Flatpaks?
This is certainly not only a Steam issue, as I have both installed and they both work.
I will test if Easy Effects can launch while a Steam game is running.
Lastly, I expect to have a similar issue, as EasyEffects does activate some settings that may be either locked by Steam or incompatible with Steam.
Yep, confirmed. Even after closing Steam completely, EasyEffects can’t be launched. I see an update for EasyEffects is available, so I will reboot to see if it can launch after a reboot. In my case, Steam was installed before EasyEffects.
FINAL EDIT (FIX):
Update your device.
After I updated, I also renamed the following folder and rebooted. Now, I can launch and use either Steam or EasyEffects in any order and they both run fine. Just update.
Both were installed normally via pacman -S command. Odd because my system is always updated (its basically routine on every boot now). Anyways, thanks for looking into this and providing a fix
You can close this thread by clicking the “Solution” button under my first post if everything is working now.