Discord had to be open before StreamController

[Thrymbor]

I have to start the StreamController after Discord is loaded (nobara42).
When I have Stream controller in auto-start. i have to manually restart Streamcontroller, because Discord wasn’t loaded before the stream controller.

[ImDevinC]

Can you please provide a log file from ~/.var/app/com.core447.StreamController/data/logs/logs.log? Please do the following to generate a fresh log file:

1. Restart your computer
2. Wait for both StreamController and Discord to launch
3. To try to use one of the Discord actions in StreamController
4. Wait a few seconds and then try again
5. Quit StreamController
6. Provide the mentioned log file above

[CheeseB0y]

I have this same issue. I have StreamController set to run at startup but not discord. After I launch discord the mute and deafen buttons don't work until I exit and reopen StreamController. I have attached my log file below following your instructions. Please let me know if I could provide any more information regarding this issue I would be happy to assist.

logs.log

[ImDevinC]

@CheeseB0y something is happening in your startup of StreamController that is preventing the plugin from loading correctly. Unfortunately, that doesn't seem to be logged anywhere because of how plugins are loaded. To troubleshoot this, we'll need to do some triaging if you don't mind.

1. Open StreamController
2. Under Settings -> System, disable Autostart
3. Quit StreamController
4. Download the two attached files, and put them in ~/.config/autostart/ (tar -xvzf archive.tar.gz -C ~/.config/autostart)
5. Make sure to mark the script as executable (chmod +x ~/.config/autostart/streamcontroller.sh)
6. Restart your computer
7. Verify the issue still happens
8. Quit StreamController
9. Attach the log file located at ~/tmp/streamcontroller.log

This script just makes sure to capture logs at the python root level instead of just inside the application. This should help us understand why the plugin is failing to initially load.

archive.tar.gz

[CheeseB0y]

For whatever reason I had trouble getting the StreamController-debug.desktop file to autostart despite being in the ~/.config/autostart folder. I've found that the Exec line in the StreamController-debug.desktop file must be an absolute path so I modified it to Exec=~/.config/autostart/streamcontroller.sh and the desktop file would launch if I opened it manually, but still not automatically after restarting. I can keep digging on why the autostart isn't working, but starting it manually I still see the same behavior with the mute and deafen shortcuts. Closing and reopening fixes this issue as long as discord is open when the program is launched. I have attached the new log file generated below.

streamcontroller.log

[ImDevinC]

Weird, this failed differently than before. But that should be ok. I created a debug version of the plugin that adds a lot more print data. Can you please try the following:

1. In StreamController, uninstall the Discord plugin
2. Go to Settings -> Store
3. Disable auto-update assets
4. Click the + next to "Custom Plugins"
5. Enter https://github.com/imdevinc/StreamControllerDiscordPlugin for the Repository URL and debug-socket for the branch
6. Enable the Custom Plugins option
7. Close the Settings window
8. Open the Store (it may take a few seconds to refresh the store)
9. Find the Discord - Debug plugin and install it (not the regular Discord plugin) (all the settings and such should still get picked up just fine)
10. Close StreamController
11. Reproduce the issue the same way you did for the previous log (please try clicking the button three separate times as well, instead of the two I mentioned before)
12. Provide the new streamcontroller.log file

[CheeseB0y]

I have attached the log file as requested below. I see that we are attempting to connect to the socket at /run/user/1000/discord-ipc-0 which I can confirm does exist at the time of testing.

streamcontroller.log

[ImDevinC]

Hmm... Just to to confirm, you're testing the following in the logs:

1. Discord and StreamController not running
2. Start StreamController
3. Start Discord
4. Try to push button in StreamController

If so, after getting to step 4, can you run the following two commands and post the results:

• ls -lah /run/user/1000/discord-ipc-0
• ps aux | grep -i Discord | grep -i socat

[CheeseB0y]

Yes that is correct. I'm not getting any response from the second command even after I restart StreamController and the discord buttons to work.

╭─cheeseb0y@zohar ~
╰─ඞ ls -lah /run/user/1000/discord-ipc-0
srwxr-xr-x 1 cheeseb0y cheeseb0y 0 Sep  6 15:22 /run/user/1000/discord-ipc-0

╭─cheeseb0y@zohar ~
╰─ඞ ps aux | grep -i Discord | grep -i socat

I do get a response from ps aux | grep -i Discord and ps aux | grep -i socat if done separately but I don't know if that output is of any use here.

[ImDevinC]

That second command returning no results showcases the issue, but I'm not sure why. If there's no results, it means Discord isn't creating it's RPC socket for some reason. Can you run those same two commands when everything is working correctly and post the results?

[CheeseB0y]

I get the same response even when it's working correctly.

╭─cheeseb0y@zohar ~
╰─ඞ ls -lah /run/user/1000/discord-ipc-0
srwxr-xr-x 1 cheeseb0y cheeseb0y 0 Sep  6 17:39 /run/user/1000/discord-ipc-0

╭─cheeseb0y@zohar ~
╰─ඞ ps aux | grep -i Discord | grep -i socat

[ImDevinC]

Wow, even more confusing. Let's try the following two commands:

ls -lah /run/user/1000/discord-rpc-* and ps aux | grep -i discord-rpc

[CheeseB0y]

I tested this before and after restarting StreamController and got the same result.

╭─cheeseb0y@zohar ~
╰─ඞ ls -lah /run/user/1000/discord-rpc-*
ls: cannot access '/run/user/1000/discord-rpc-*': No such file or directory

╭─cheeseb0y@zohar ~
╰─ඞ ps aux | grep -i discord-rpc
cheeseb+    3706  0.0  0.0   6744  4176 pts/1    S+   19:30   0:00 grep --color=auto -i discord-rpc

[ImDevinC]

Ahh my bad, I typo'd. Apologies for the back and forth, just really confused by what we're seeing. Let's try this while things are in a working state:

ls -lah /run/user/1000 | grep discord-ipc
ps aux | grep -i discord-ipc
lsof /run/user/1000/discord-ipc-0

[CheeseB0y]

No worries I'm happy to help get to the bottom of this.

╭─cheeseb0y@zohar ~
╰─ඞ ls -lah /run/user/1000 | grep discord-ipc
srwxr-xr-x  1 cheeseb0y cheeseb0y   0 Sep  6 19:29 discord-ipc-0

╭─cheeseb0y@zohar ~
╰─ඞ ps aux | grep -i discord-ipc
cheeseb+   85321  0.0  0.0   6744  4172 pts/2    S+   20:52   0:00 grep --color=auto -i discord-ipc

╭─cheeseb0y@zohar ~
╰─ඞ lsof /run/user/1000/discord-ipc-0
COMMAND  PID      USER FD   TYPE             DEVICE SIZE/OFF  NODE NAME
Discord 2071 cheeseb0y 55u  unix 0x0000000053cd90ae      0t0 26715 /run/user/1000/discord-ipc-0 type=STREAM (LISTEN)
Discord 2071 cheeseb0y 63u  unix 0x00000000e16ae243      0t0 32843 /run/user/1000/discord-ipc-0 type=STREAM (CONNECTED)

[ImDevinC]

Ok, the lsof shows what I was expecting to see with the ps aux command, so that's good. So let's get back to the broken state (StreamController launches, the Discord launches, but buttons still don't work) and then run lsof /run/user/1000/discord-ipc-0 again