Anyone seen this issue before: ``` /etc/ublue-update.d/system ❯ ./00-system-update.sh error:
Anyone seen this issue before:
Tit's preferred to use as a flatpak
KFix for that just went up, it's from the new auto signer feature
Krpm-ostree updateIn the meantime
GYeah, there was a typo/missing prefix in the refspec in
image-info.json, just PRed the fix so should all be good and land shortlyGHoping not too many people got the broken
image-info.json in their imageGIn the meantime I should probably do something to prevent the system update script failing because of typos in the refspec when trying to rebase
GMaybe a call to
test or something, anyhow I gotta get some sleep now
Dok the manual ostree update fixed it. all good now
TJust trying to get this issue and not finding it myself. Are you setting the env the same way as steamos?
discover_overlay will detect the ENV variable GAMESCOPE_WAYLAND_DISPLAY and set itself into gamescope compat mode.
Wdamn alright you really love your samsung SSDs
VOh wow
VThe adwaita steam theme affects notifications
Wis there something like the adwaita steam theme but for KDE
VNot that I've seen
VI just use the Adwaita theme cuz it looks nice
Veven if it doesn't fit
Will probably do the same lol
WI have corectrl, syncthing and easyeffects in my autostart but the only thing that starts is easyeffects. anyone know whats up with that?
Walso first boot setup never ran I just realized its just sitting there
KHave to enable the auto launched we made it you havent
KThere's a file in /etc/default that has a variable you can toggle to 1 to do it
KThen it'll launch and die with gamescope so long as you also have flatpak discord installed
TI'll get my hub set up on my deck when I'm free and try it directly, see what's happening, Ta for the pointer there, hadn't worked out what was happening with /etc/default from here
KIssue is since I'm launching discover automatically at boot (if feat enabled in default + discord installed) it eats the single overlay that's used by mangohud
KI figured this was my fault and disabled it so I could reintroduce with a daemon that starts and stops it with discord
KBut if we can do that in discover instead and leave it running that's awesome
TIn normal usage it should play nice and only show an overlay if there's anything to display.
From what I see the major change between your system and steamos gamescope is the use of the environment variable above, as I can't see it in your script
From what I see the major change between your system and steamos gamescope is the use of the environment variable above, as I can't see it in your script
TKids are almost in bed so I'll have a chance to look in a bit
KThe difference is we're automatically launching it here, that environment variable is something I added when I noticed the bug to disable that behavior by default
KIt just starts with game mode starts
KNothing is displayed, but it still consumes the layer that mangohud would
KIf that last part could be fixed it would be great, because starting Discord in game mode and joining a voice channel starts showing the overlay, for the intended functionality is working excellently
TI feel like we're talking about two different variables here
KThe one in /etc/default, no?
KGitHub
…discover-overlay if the discord flatpak is present
KGitHub
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...
TI currently can't see, but I assume not. 'GAMESCOPE_WAYLAND_DISPLAY' needs to be set for correct functioning
KAh, we are talking about a different one then
KDiscover overlay works perfectly, the issue is only the fact that launching it the way I'm launching it breaks mango HUD
KI believe in your tutorials you have it set up as its own non-steam game
KAnd launch at the same time you launch Discord
KInstead of at the very beginning of the session like we are
NSo you guys want to hear a weird issue I'm having?
KSup?
N- Running Bazzite NVIDIA - Bazzite Arch container for Steam.
- Tell Steam to install Final Fantasy XV (that's 15, not the MMO).
- Steam starts the download, gets about 7% of the way through, then the network activity drops, the disk activity slowly drops off, and then stop.
- Steam will say "stopping download" but the pause button is still there, and doesn't change anything.
- This then affects Steam so that I can't fully shut it down. It acts like, perhaps not the correct term, a zombie process.
- I can close the window, but can't stop the process(es).
Tthis happened to me but not on bazzite
Tnor in the bazzite-arch container
Nwith this same game?
Tno
