Open Calhym opened 3 months ago
If Companion is running on the same machine as Discord, Discord is from the official Discord website, and you're not doing any sort of sandboxing of apps, then there's not much support I can offer.
I don't use Discord on my Linux machines so can't test myself, but others who have ran in to issues previously on linux have all been due to sandboxing, so I'd recommend you investigate that on your end.
I didn't consider sandboxing might be happening. I will try to look into that over the next few days.
If I find anything I'll be sure to post here. Or if I find the "fix".
I'm trying to switch to using Linux, and companion seems to be a good way to control the Stream Deck. I was able to use "shell path local" to somewhat work around using terminal commands under my main account, and I assume a similar issue might be in place for the discord app. However I'm knew to this and not sure if this is the case.
(NOTE: the shell work around was to use "echo | su - -c "". Not secure but was for testing.)
To Reproduce
1.Open discord on your machine
Expected behaviour Considering I'm still learning this all, my "expected behavior" is to be able to control discord.
Additional context This is being done on a repetitively clean install of Linux. Specifically PopOS. I have tried both the Discord version in the PopOS repository and the DEB file from the Official Discord website. (I believe both of these are the "official" version.)