SThanks for sharing the guide to yubikey your Bazzite install
TMine has a light in a physical button, works as you described above
TIt wasn't my guide 
Just something I really wanted to make happen
Just something I really wanted to make happenTI'm always super weird about leaving login details on unecrypted devices
Dheh sorry idk how to repost past messages, a bit of a discord noob
TOh I don't mind. But a bazzite ping is almost always 'it broke'
It was a nice change
It was a nice change
SThanks nonetheless 
It's probably my final push to actually start using my key which has just been sitting there for a year now.
I've got the yubikey 5C NFC, with all the bells and whistles.
I totally get the reluctance to lug around unencrypted devices with lots of passwords on
It's probably my final push to actually start using my key which has just been sitting there for a year now.
I've got the yubikey 5C NFC, with all the bells and whistles.
I totally get the reluctance to lug around unencrypted devices with lots of passwords on
TThe graphical unlock could do with some explaination IMO. Currently it just does the spinning 'loading' screen while waiting for your key & interaction.
I wonder how hard it would be to patch that into plymouth
I wonder how hard it would be to patch that into plymouth
Dit also looks like yubikey, or any other fido2 physical key, is the only way to have a truly secure deck, tpm2 would work if steam deck supported secure boot and allow us to lock down the BIOS with a password. There still questions about pcr 11-15 that im not sure would work on bazzite
TYeah I shied away from secureboot without knowing for sure I could change it from BIOS with a secure BIOS password
Aok guys, need some testers for the next hhd version
Abiggest change is that i grab the controller now, so no more passthrough to games
Abut as its a big change, i need someone to test
Aand probably one or more versions down the line i will also support external controllers
SI’ll test it out
Ayou remember the steps?
Ayou also need the new overlay app image
SVaguely enough that I’d need a refresher. Stop hhd then run local copy from whatever bin directory?
Alemme pull up the script
A should work until you reboot
Aafter you verify it works we'll make it a ujust
Aalso check out the new theems
Nsomebody should pin it until it gets its own ujust command
Soo ocean theme
TOoh, not come across HHD before. This looks fun
Sso far so good, just to make sure I'm on the right version HHD 2.3.0 hhd ui 2.2.0 Adjustor 2.1.2?
Tone of the main components that makes using most handheld PCs that aren't the steam deck actually usable
TI had wondered what people were doing for a compatibility layer, this is very much more sophisticated than I imagined.
TI tried getting my frame.work set up as a big picture style session and ended up with a pile of bash scripts all over the place and it wasn't sensible
AProbably lol
AIf you can see the ocean theme it's correct
Sit looks great I like it
Sanything specific to test?
AUse it in games and see if there's any weirdness with passthrough
KHey after the new image update yesterday, I wanted to use Waydroid.
I followed this guide:
https://universal-blue.discourse.group/docs?topic=32
But after
then
I can see that it's downloading the vanilla lineage os image, but following the guide further to
results in a small black screen
do you know how to fix that?
I followed this guide:
https://universal-blue.discourse.group/docs?topic=32
But after
ujust setup-waydroidthen
Initialize WaydroidI can see that it's downloading the vanilla lineage os image, but following the guide further to
/usr/bin/waydroid-launcherresults in a small black screen
do you know how to fix that?
Universal Blue
[Waydroid] NOTE: There is no GPU acceleration when using Nvidia’s proprietary drivers. Waydroid gives users access to an Android container. First-time Setup Open a host terminal and enter this command to setup Waydroid: ujust setup-waydroid Initialize Waydroid Waydroid requires users to initialize it for the first time which can be done by ...
Tpretty sure waydroid is broken after an update to the package
Tthis happens sometimes
Tyou could probably rollback to an older build and it will work setting it up in the meantime
KOh okay, thx.
I also noticed the "output X11-11" line
maby it has to do something with that, because wayland is required
I also noticed the "output X11-11" line
maby it has to do something with that, because wayland is required
Toh are you on X11?
KNo
Tthen you're good
Tit's waydroid's package
KI just noticed the x11 line ^^
JAnyone else having an issue with pytix saying "could not activate remote peer unit"?
GI think it might have actually been the recent kernel update that's causing the waydroid problems, not an update to the package itself? This is just a total guess, but I started having problems after the 20240328 image which, based on the git commit history, is when the kernel was switched from 6.7.9-204 to 6.7.9-207. Of course this could be a total coincidence (correlation is not causation!). But at the same time, all the online discussions I could find about this issue (caused by the binder service dying) have pointed to kernel-related causes
VPosted this in #bazzite-help yesterday but also trying here: I have an AMD eGPU (GPD G1), which gets detected correctly in desktop mode and sends HDMI video out to my TV without issues. (
In game mode, however, HDMI video out just shows a black screen on my TV. I can hear the fans of the eGPU spinning (suggesting that the connection is made correctly), but nothing gets displayed on the external monitor. Would love any guidance if anyone has tips.
gpu-export correctly reports both the dGPU and iGPU, with the dGPU being first in the list. All seems good in desktop mode.)In game mode, however, HDMI video out just shows a black screen on my TV. I can hear the fans of the eGPU spinning (suggesting that the connection is made correctly), but nothing gets displayed on the external monitor. Would love any guidance if anyone has tips.
Tyeah this is a known issue
Tit could be 100% kernel related too
GIn any case, if you still have an older deployment in your GRUB menu from before the kernel update (so earlier than 20240328) that should work, at least from my testing
