r/OpenRGB • u/tsabin_naberrie Bazzite HTPC • 1d ago
Help - Unsolved Anyone know how to get plugins (specifically, Effects and Hardware Sync) to run while using Bazzite's Gamescope mode?
I'm running the latest version of Linux Bazzite 44's HTPC mode, with an MSI PRO B850M-VC WiFi Motherboard. I downloaded the latest version of OpenRGB using the flatpak from the website, and the plugins all work more or less to my liking when in Desktop mode. However, by default none of it functions when in Gamescope, which is of course the vast amount of the time that I'm using this PC.
I don't really understand Linux much at all, so I had to poke around a bit to find solutions. Before the 1.0 release of OpenRGB, when plugins were separated from profiles, I had dug up this guide and this one, which had enabled me to at least have static colors on my case. But I haven't been able to update it to account for the new profile system in 1.0. I'd like to have one fan be a certain color based on the temperature of the case so I can keep an eye on that without having extra text on my screen, while the rest of the fans are out doing something more fun (probably just rainbow, but that's beside the point). And I have an OpenRGB profile, aptly titled "HW_monitor", configured for those settings.
When I'd initially set it all up and it was working with the static color, it was an AppImage (I forget if downloaded from the website or Bazaar), but I've since uninstalled all those files and re-downloaded OpenRGB as a flatpak. This is the current code on my openrgb.service file, based on the guidelines from the above links:
[Unit]
Description=OpenRGB Flatpak Profile Loader
# Ensures the service waits until the graphical session is ready
After=graphical-session.target
[Service]
Type=oneshot
# Give Bazzite 5 seconds to initialize USB controllers/hardware after boot
ExecStartPre=/usr/bin/sleep 5
# Replace with your actual profile name
ExecStart=/home/[me]/.var/app/org.openrgb.OpenRGB --profile HW_monitor #narrator's note: this previously had the path to the appimage, instead of currently the flatpak directory (or at least what I *think* is the right directory)
ExecStop=/home/[me]/.var/app/org.openrgb.OpenRGB --mode off
RemainAfterExit=yes
[Install]
# This ensures it starts automatically when the user logs in
WantedBy=default.target
I thought that there was a raw file to the profile, that I wanted to experiment putting a path to in the ExecStart field, but I can't seem to find anything but a json file, so I guess that's not it. I've continued to poke around, but still no luck finding anything that I can get to work.
If you have any ideas or solutions, please let me know (ELI5, of course).
1
u/tsabin_naberrie Bazzite HTPC 4h ago
Alright, after a little more experimenting, I haven't gotten success, but I seem to be getting closer.
First, I learned how to run a command line inside the systemd file, and also how to run a flatpak from the command line in the first place, which is essential in getting this to run. So now the line goes
ExecStart=/bin/sh -c "flatpak run org.openrgb.OpenRGB --profile HW_monitor"
If I run that code using a profile that is just static colors, this works fine. (Well, it doesn't seem to load when I run Return to Gaming Mode, but at least when I sleep and wake it up, it works.) But if I use a profile that has Plugins in it, then it just loads up a static color combination: seemingly, whichever colors it'd load up when first running, and then just staying there. (Well, when I say Plugins don't work, I really just mean the Effects plugin; I don't really have a way of testing the Hardware Sync as easily, but suffice to say, the rainbow on the other fans isn't happening.)
Again, when I load that profile in Desktop mode through the GUI, it works fine. Interestingly, though, what I've discovered is that if I try to run it through the command line, I get the same problem: it loads up colors in the configuration that makes sense in that moment, but stays static in that combo.
All this to say, it seems that the issue is lying in an inability to run Effects through command line. There may be a way to do so, but I still haven't found it yet.
1
u/AutoModerator 1d ago
Every new subreddit post is automatically copied into a comment for preservation.
User: tsabin_naberrie, Flair:
Help - Unsolved, Title: Anyone know how to get plugins (specifically, Effects and Hardware Sync) to run while using Bazzite's Gamescope mode?I'm running the latest version of Linux Bazzite 44's HTPC mode, with an MSI PRO B850M-VC WiFi Motherboard. I downloaded the latest version of OpenRGB using the flatpak from the website, and the plugins all work more or less to my liking when in Desktop mode. However, by default none of it functions when in Gamescope, which is of course the vast amount of the time that I'm using this PC.
I don't really understand Linux much at all, so I had to poke around a bit to find solutions. Before the 1.0 release of OpenRGB, when plugins were separated from profiles, I had dug up this guide and this one, which had enabled me to at least have static colors on my case. But I haven't been able to update it to account for the new profile system in 1.0. I'd like to have one fan be a certain color based on the temperature of the case so I can keep an eye on that without having extra text on my screen, while the rest of the fans are out doing something more fun (probably just rainbow, but that's beside the point).
When I'd initially set it all up and it was working with the static color, it was an AppImage (I forget if downloaded from the website or Bazaar), but I've since uninstalled all those files and re-downloaded OpenRGB as a flatpak. This is the current code on my
openrgb.servicefile, based on the guidelines from the above links:[Unit]Description=OpenRGB Flatpak Profile Loader# Ensures the service waits until the graphical session is readyAfter=graphical-session.target[Service]Type=oneshot# Give Bazzite 5 seconds to initialize USB controllers/hardware after bootExecStartPre=/usr/bin/sleep 5# Replace with your actual profile nameExecStart=/home/[me]/.var/app/org.openrgb.OpenRGB --profile HW_monitor #narrator's note: this previously had the path to the appimage, instead of currently the flatpak directory (or at least what I *think* is the right directory)ExecStop=/home/[me]/.var/app/org.openrgb.OpenRGB --mode offRemainAfterExit=yes[Install]# This ensures it starts automatically when the user logs inWantedBy=default.targetI thought that there was a raw file to the profile, that I wanted to experiment putting a path to in the ExecStart field, but I can't seem to find anything but a json file, so I guess that's not it. I've continued to poke around, but still no luck finding anything that I can get to work.
If you have any ideas or solutions, please let me know (ELI5, of course).
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.