Arch Linux User Repository

@dhtseany I've stopped the service, ran the command (my stream deck was then showing my configured buttons), killed it, started the service, same error

Here's the output of systemctl status streamdeck.service

I'm running plain old Arch with Gnome 43/GDM/Mutter. I'm sure I may have modified things here and there but it is not headless, nope

@jvzr I think I dealt with this at one point but I couldn't reproduce it, first kill the running service then try running # python /usr/bin/streamdeck -n (aka as admin), kill the running python thread, then try starting the service again. Does that help? I think it's something with the config file not existing and running it that way makes a dummy file.

If not paste me the output of $ systemctl status streamdeck.service and I'll try to help more. Also, the angry display message is because we're using Wayland but it should still work.

Edit: Upon closer inspection of your initially provided logs I too see how it seems to be a bit more angry than usual, that isn't the normal qta bug I'm used to seeing. The system you're using isn't headless, is it?

@dhtseany I have been trying to make the systemd service work but have been unsuccessful. I get a qt.cpa error relating to the display. Gnome 43 on Wayland. Can I provide you with more info? If so I'd happy to help you debug this.

As always, thank you for the continuous updates!

The update to 2.0.15-1 was fairly uneventful with support for the Stream Deck Pedal being the major feature addition for this version. As always let me know if you need help and remember to check your makedep's if your having problems building.

The update to 2.0.14 has been pushed which notably includes the ability to run the streamdeck binary as a systemd service file however you'll find that the provided .service file does not match what is recommended by upstream. Remember that there's 2 ways to run the streamdeck-ui app on Arch:

1. You can use upstream's provided PIP instructions which installs and runs all within user-space. Running the new service file as instructed by upstream is how you'd want to create the .service file.

2. You choose to install a package like streamdeck-ui or streamdeck-ui-git knowing you'll be running at the system level instead which requires that we run the app slightly different from upstream.

This package is #2 and instead of their --user based command you start/enable/stop the service file as a normal .service file:

$ sudo systemctl start streamdeck.service

Let me know if anyone runs into any problems and I'll do my best to assist!

Edit: Lol sorry about 2.0.14-1, I forgot to save the .service file before I pushed it ^^

Updated to 2.0.13, thanks to the team upstream for the continued work on a great project!

This update sees the removal of pyside2 and the addition of pyside6 to take it's place.

The workaround with xhost is no longer required so I've removed that from the .desktop file and the app will launch normally again without error by using streamdeck.

Let me know if there's any problems during upgrade and I'll do my best to assist.

PS- Remember that you don't need pyside2 anymore, you should be able to remove it safely with $ pacman -Rs pyside2

I updated the .desktop file to provide an easier to use workaround assuming upstream doesn't plan to correct this. That said, you can also use the fix I applied from the terminal by running $ xhost + && streamdeck

If I get feedback on a better way to resolve this such as a patch I can apply during packaging I'm happy to accept the help! Let me know if there's problems from this update for anyone and I'll do my best to help.

I've found a workaround to get the app running again however I don't feel it's a permanent fix...

1. Run: $ xhost +
2. Then run streamdeck: $ streamdeck

I'm aware of the ongoing problem and I'm still waiting on a response about what we should do for a permanent fix from upstream but this should at least get it running again short-term.

We have a bug report filed with upstream, I'll report back with more information as we learn how to work around this problem. Thanks for everyone's patience, it's directly impacting me for work purposes so rest assured I'm focused on finding a resolution, be it temporary or permanent.

@dhtseany: thank YOU for providing this package and being on top of things! We'll wait patiently. In the meantime, if I can help test/validate solutions, don't hesitate to ping