FI read that grep -v can have some problems when piped in some scenarios
FIdk why
EI'll have to rewrite as a loop
EBut it does in fact work for me
E
AFor anybody using SimpleDeckyTDP on the Legion Go, I pushed some updates for it recently. It now supports changing SMT, CPU Boost, and GPU clocks. GPU clocks have only been tested on my Legion Go, but seems to be working well
https://github.com/aarron-lee/SimpleDeckyTDP
https://github.com/aarron-lee/SimpleDeckyTDP
Knope, but there's a just command to re-gen grub if needed
KI'll work on an installer for this next, ty
Hignore what i said, apparently there is some code for it if it is set to metered in network manager
https://github.com/ublue-os/config/commit/0823567237f8d83a50a75e9a7cd15c7c9d758d22
https://github.com/ublue-os/config/commit/0823567237f8d83a50a75e9a7cd15c7c9d758d22
GitHub
- feat: check metered connection before automatic updates
- feat: add just commands to disable/enable automatic updates
- docs: add metered connection check
- docs: change version
- docs: add a...
WDoes it work on deck since the frequency limiter with powertools doesn't work anymore?
RHow long will
bazzite-hardware-setup take? It has been sitting there for 13 minutes
Kthat's about normal
Aerr, this was primarily intended for non-deck handhelds. completely untested on the deck itself. Heck, it hasn't been heavily tested even on non-deck handhelds, it's a brand new feature I rolled out a few hours ago, I've only done testing on the LGO
WDo you mind testing it also on deck since powertools is now an archived project?
F@EyeCantCU I fixed the issue with -vf (had to remove -o for install & add "-", which I removed before), but it shows me this now
On terminal, it outputs correctly with this:
echo "$FLATPAK_LIST" | grep -vf - "$INSTALL_LIST_FILE"
But here, it complains about "Invalid id" & "Name can't be longer than 255 characters" when I run the service
On terminal, it outputs correctly with this:
echo "$FLATPAK_LIST" | grep -vf - "$INSTALL_LIST_FILE"
But here, it complains about "Invalid id" & "Name can't be longer than 255 characters" when I run the service
EThat's interesting as the exact same thing command is what we're using and what I've tested and what's in the manager. Looks like it wasn't able to find the flatpak. I presume following the error, the rest of the input may have been treated as a single line
RError -22 is going to drive me insane
K@__aru started working on HHD
Khave to wait until it has a selected license
Kbefore I can build it in copr
Kwhen that's resolved though I'll set it up to auto-install and enable on Legion
Ai'll ping the maintainer and let him know 
FI verified it fails when I have more than 1 flatpak in the list
does grep support newlines?
does grep support newlines?
Tit looks like it is certainly trying to find a string with all of those combined together and separated by newlines
Tas in things that contain
but no one thing can contain all items
but no one thing can contain all items
K@mari3434
:testing
MAwesome
JIs there a github issue that's tracking this? I'd like to get involved and try to fix it. Bourne shell scripting is kind of my thing 
FGitHub
…are missing from the list.
This allows us to ditch the state file concept, which only allows us to run flatpak-setup once. After that, you need to manually delete the state file (system & user...
This allows us to ditch the state file concept, which only allows us to run flatpak-setup once. After that, you need to manually delete the state file (system & user...
Klittle app list debloat pass
Kthere's the default folder organization for apps in the app grid, and the default dash placement
K
NIs WiFi currently brokey on the ally:testing branch? 
Kshouldn't be
Khaven't been any changes to it since it was reported as working
Kthe ally is fucky though so you might want to make sure you're up to date as far as the bios is concerned
Tyeah to add on to this, someone else said it's hit or miss
TNAudio works that’s all I want lmao
NI reflashed the bios and WiFi works now
NWtf
NJust be happy and keep moving on 
JI have a rather interesting problem on my bazzite-deck-gnome using Bottles and DVXK. In the two screenshots that follow, the one with the bizarre artifact is with DVXK and the other is without:
JIt works just fine in Lutris with DVXK. I had set both Lutris and Bottles to use wine-ge.
KThat's very strange, hard to tell what it can even be since bottles is a flatpak, should be standard everywhere bottles is run
EOddly Bazzite has no such issue with installation. This sounds like something specific to the script used in bling. I will look over it though I'd suggest just using our scripts here directly
EI think it was worth it
M@KyleGospo if you get the chance (and if you have an HDR display), you should check out Moonlight HDR streaming on the OLED Deck. I was able to get Moonlight HDR's option to work relatively easily on Nobara but couldn't manage the same on
The original experimental HDR AppImage gave me a warning about unsupported hardware for HDR streaming on Bazzite with super messed up gamma. Confirmed for myself that specific AppImage gives me no warning on Nobara and triggers the HDR badge.
bazzite-deck-gnome:testing. The original experimental HDR AppImage gave me a warning about unsupported hardware for HDR streaming on Bazzite with super messed up gamma. Confirmed for myself that specific AppImage gives me no warning on Nobara and triggers the HDR badge.
M
Mthere's also a newer nightly flatpak build from FrogTheFrog that i haven't been able to get working on either Nobara or Bazzite. i have a feeling it may be due to the way they get HDR metadata from the swapchain: https://github.com/moonlight-stream/moonlight-qt/commit/c939537c5c1d6a968c426704e5d70a30a9106834
