I realize I can disable the touchscreen per game entirely but that seems heavy handed when I just wa
I realize I can disable the touchscreen per game entirely but that seems heavy handed when I just want to disable the swipe to menu actions
KPatch from chimeraos doesn't expose a setting to turn it off atm
Kwhen that happens I'll update you
VYeah, gonna make the first release later just need to fix some issues related to cursor themes and the .desktop file 
TDoes that swipe menu function only exist on non-Deck hw?
Kworks on deck too
THuh TIL
VWhat I've done is super-duper basic, but I think it's a good intro into understanding the concepts behind flatpak'ing stuff.
NWhat did you pack up?
EThe ginormous screen makes it a thing for me on the LeGo. On my Steam Deck I never trigger it.
VI updated someone's Feishin flatpak
VIt's not gotten a commit in 4 months and is 3 minor versions behind so I'm assuming they're done with it lol
©Can you post the output of
It should mention the origin of it..
systemctl --user status app-org.kde. ... xwayland-video-bridge@autostart.service or something like that?It should mention the origin of it..
NOh sweet
©had a little typo, fixed, look again carefull at that command
©the
status is important part©Don't worry if it mentions your username and homedir, no one will be ale to use that info 
RI tried disabling it but it's "generated" so I can't seem to do that.
Hgenerated means its made from autostart either from system or homedir
Hand it tells you where
©It should have had a
source line also...H/etc/xdg/autostart/org.kde.xwaylandvideobridge.desktopRsaw that, but I didn't want to delete it...perhaps I could just move it?
©No that's the generated service...
Roh
Hno thats the file it is generated from, same as
~/.config/autostartahhh it ends in
desktop i see...im used to a source line mentioning from which file it is generated...Rhmm so could I simply
mv the file with a .backup extension to disable it from autostarting? I know I can just start it if I do happen to need it but I cannot figure out a way to hide the little icon from showing up in the Overview expose in KDE.©You should be able to disable it using the GUI settings of your WindowManager
Hdont know if systemd looks for .desktop specifically but you could make a folder
/etc/xdg/autostart.disabledonly if its in
~/.config/autostartyeah it doesn't show up there, I already checked
Rbrb gonna reboot and see if it still autostarts after trying @HikariKnight's suggestion. TY guys.
©Maybe it is located in
/etc/systemd/user/etc/xdg/autostartyooo it works
Rit's gone ty
©great, another problem solved and happy person 
Rbut now of course I may have to deal with screen sharing not working since it isn't autostarted and I'll have to manually start it, but eh that's not a big deal
RI tried figuring out how to hit the little xwayland-video-bridge window from things like Overview and alt-tab switching but to no avail.
©everything has it's "Pro" and "Cons"
©A Question for the Guru's here:
Is it possible to make something that changes config files for stuff installed using
Is it possible to make something that changes config files for stuff installed using
rpm-ostree installI made a tweak for the
toruBlueTime for 
, tomorrow another day to fiddle... 
, tomorrow another day to fiddle... 
EDid you fix issue? I installed Bazzite on fresh SSD drive on legion go. When I download games my GPU consumes 10-15W and frequency is from 800 to 2000. But I don’t play game! I can’t understand why my GPU utilizes so much power in steam interface. Frame rate is also very slow no matter what settings I set.
EIt’s important to mention that I installed everything step by step from Aru’s layest guide on YouTube
DDoes anyone know how to reset sdgyrodsu's config? Seems like the service's preset is set to disabled, and I can't seem to figure out how to make it start with Bazzite. If I manually start it with systemctl --user restart sdgyrodsu.service, it works.
Ksystemctl --user enable --now sdgyrodsu.serviceThat made it start, but it still says preset: disabled. Is that normal?
DIt also seems to broadcast itself on 0.0.0.0 instead of localhost/127.0.0.1
Aso steamUI has an issue where it uses up GPU while on certain pages in SteamUI. do you have high GPU utilization when you're not on the home page? e.g. library page
