Plugin seems extremely inconsistent

[Optionalpoop]

I am unsure as to why, but no matter what linking to Discord seems extremely spotty and I am unable to mute, deafen, or select channels most of the time. I've followed all of the instructions, and I've read the other issue, and running Discord before opening Stream Controller does not help. Restarting my computer is sometimes a bandaid fix, although the problem quickly returns and the buttons are no longer responsive for Discord-related actions. I do not have the flatpak of Discord, I downloaded it through the website, and I also have tried both the flatpak of Stream Controller and building it from the GitHub page. I've reinstalled the plugin a few times, sometimes it helps temporarily and sometimes it does not.

[Optionalpoop]

Sorry if this is a bit convoluted, I've never actually tried to open an issue like this so I have no idea of the proper ways of doing things.

[ImDevinC]

Can you include the logs from when the issue starts happening? The logs can be found at ~/.var/app/com.core447.StreamController/data/logs/logs.log

[Optionalpoop]

logs.log

Screencast.From.2025-12-26.09-51-03.mp4

Here you go, I've also attached a video of how pressing buttons makes it seem to pop up a warning symbol of some sort.

[ImDevinC]

i'm not 100% sure why this is failing, I just see that the backend failed to initialize properly. I did just merge in some changes from #57 which might help. Can you make sure to update to hte latest plugin version from the app store, restart StreamController, and s ee if that helps at all? If not, please grab another log so we can get the latest information.

[Optionalpoop]

logs.log

I've sent a fresh log, as the update does not seem to have helped at all. Interestingly, before I updated the plugin began working momentarily, stopping soon after once I updated it. I first noticed it was working again when I was in a call with a friend, and the buttons started to work again, but once it stopped working I was unable to recreate whatever might have allowed it to work again.

[ImDevinC]

Interesting... thanks. Let's try something else that will get us abit more information if you don't mind

1. Quit StreamController completely (three dots -> Quit)
2. Open a terminal window and run flatpak run com.core447.StreamController 2>&1 | tee ~/StreamController.log. This will launch StreamController in the terminal, and log everything to ~/StreamController.log
3. Reproduce the issue
4. Quit StreamController completely (three dots -> Quit)
5. Upload ~/StreamController.log

[Optionalpoop]

I ran the command, but was not able to interact with the Stream Deck at all during this. I've still attached the log, although I don't believe anything useful will be there. I do have the flatpak of StreamController installed, but due to it having some issues I just went and built it from source code, so I think that the flatpak command might not be super helpful. Is there something else I can use to do a useful log file?

StreamController.log

[ImDevinC]

2025-12-26 11:02:52.897 | INFO     | src.backend.PluginManager.PluginBase:launch_backend:636 - Launching backend: . /home/optionalpoop/.var/app/com.core447.StreamController/data/plugins/com_imdevinc_StreamControllerDiscordPlugin/.venv/bin/activate && python3 /home/optionalpoop/.var/app/com.core447.StreamController/data/plugins/com_imdevinc_StreamControllerDiscordPlugin/backend.py --port=35517
python3: error while loading shared libraries: libpython3.13.so.1.0: cannot open shared object file: No such file or directory
2025-12-26 11:02:53.198 | ERROR    | src.backend.PluginManager.PluginManager:init_plugins:71 - Error initializing plugin <class 'plugins.com_imdevinc_StreamControllerDiscordPlugin.main.PluginTemplate'>: 'NoneType' object has no attribute 'update_client_credentials'. Skipping.

This does actually show the issue. It looks like it has to do with the way things are installed on your system. Usually this happens when there's a mismatch between the python environment used for the main StreamController application, and the automatically created backend for the plugin during install. This is pretty common when not using Flatpak as dependencies get managed outside of the application. To start, I would delete the Discord plugin from StreamController (you can do this in the Store), quit StreamController, and then relaunch it and re-install the plugin to see if that helps. I'm also not sure how you have setup StreamController outside of Flatpak, but I would recommend setting up a virtual environment for StreamController and launching it from the virtual environment to help maintain dependencies.

That being said, Flatpak not working probably points to a larger issue, as the Flatpak installation is self-contained. If that's not working, there may be something larger going on. Can you clarify what doesn't work with Flatpak?

[Optionalpoop]

Interesting! I've uninstalled the plugin, relaunched, and reinstalled, and it seems to be working currently. Like I said before though, it was working occasionally for a little bit before stopping, but this has solved the problem at least for now. I'll come back and add another comment if it stops working again, and if it's okay I can close the issue tomorrow morning when it's been long enough to likely not happen again.

For the Flatpak's issues: at the top in my shell (I use GNOME) the image only appears as three dots as shown in an attached image, which does not happen with the other installation of the app, which shows the actual logo. The big thing though is that it seems to never connect to Discord when I go into the plugin settings and try to add my client ID and secret it can never find my Discord session, assuming that the settings even opens, which it doesn't sometimes.

Thanks for all your help, especially on the holidays!

[ImDevinC]

Glad its working now. Based on the error, and what fixed it, my guess is you recently did an update for Python on your system, so the versions got mismatched.

As for the Flatpak issue, the icon _should_be fixed as of the latest release, if not I'd file a defect on the StreamController GitHub. And for the Discord specific issue, the README in this repository covers the settings that need to be changed to address that. But if it works for now, that should be good (although the next time you do a system update that includes Python, you may run into the same issue)

[Optionalpoop]

Welp, it's been a few days and the problem is back with a vengeance. Once again, Discord interactions do not have any effect. It hasn't started working once since yesterday morning. Reinstalling the plugin has not helped, restarting my computer, running updates, changing versions between the flatpak and source, changing Discord, nothing has helped and I think I may be going a little bit crazy. I also tried deauthorizing the app connected to my Discord, but now it won't ever reauthorize. I never get a popup, and the link within the manager for it just gets me the error not finding port 9000 shown in the attached screenshot.

Running StreamController through the terminal and pressing any Discord buttons gets me the following:

2025-12-30 09:20:21.830 | ERROR | plugins.com_imdevinc_StreamControllerDiscordPlugin.actions.Mute:_on_toggle:64 - 'NoneType' object has no attribute 'set_mute'
2025-12-30 09:20:22.231 | ERROR | plugins.com_imdevinc_StreamControllerDiscordPlugin.actions.Mute:_on_toggle:64 - 'NoneType' object has no attribute 'set_mute'
2025-12-30 09:20:22.783 | ERROR | plugins.com_imdevinc_StreamControllerDiscordPlugin.actions.ChangeVoiceChannel:_on_change_channel:74 - 'NoneType' object has no attribute 'change_voice_channel'
2025-12-30 09:26:12.325 | ERROR | plugins.com_imdevinc_StreamControllerDiscordPlugin.actions.Mute:_on_toggle:64 - 'NoneType' object has no attribute 'set_mute'
2025-12-30 09:26:27.803 | ERROR | plugins.com_imdevinc_StreamControllerDiscordPlugin.actions.ChangeVoiceChannel:_on_change_channel:74 - 'NoneType' object has no attribute 'change_voice_channel'

I've also attached a log file.

logs.log

[ImDevinC]

This looks like the backend is faling to load. Can you grab logs using the same method as outliend above (flatpak run com.core447.StreamController 2>&1 | tee ~/StreamController.log) as this will include some other information that is usually left out of the logs.

[Optionalpoop]

StreamController.log

Here is the log file.