Use it in games and see if there's any weirdness with passthrough
Use 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
KI mean it's not that important at the moment, I think I can wait
Jis there a known fix/eta for fix?
Ai had to manually swap to a tty and enable konsole for to get around the ptyxis issue
3anyone got smthing to modify DPI and polling rate of a roccat kone aimo? 
Ais there any way that bazzite could ship with both ptyxis and konsole enabled in the future? as in, have konsole also show up when a user searches
terminal
Aits probably still in one of the layers lmao
Akonsole is there, but it doesn't show up in searches for
terminal 
KI never remove it, I just hide the desktop icon
KYou can restore it using ujust
Abut if you can't open ptyxis to run ujust 
KOh fun that one snuck in here too huh?
KI will have a build out very shortly to fix this
KYou can TTY
Kto get just
Ayep, i did that for now
Abut i think there might also now be a different issue for users that have the borked ptyxis
Awhen i ran the system update app, it was just hanging
Awhich i had assumed was related to ptyxis
KYes, that app runs the ujust in ptyxis
Kthough you can also just update from TTY or game mode
Ai was just thinking that if a user has a borked ptyxis, they'll need to manually run
ujust updatesince running the system update app hangs right now
KAutomatic updates still work, as do updates in game mode
KSo most people shouldn't have an issue unless they specifically need a terminal
Anice, good to know 
Ais this something we should be concerned about? apparently affects xz 5.6.0, 5.6.1
https://www.theregister.com/2024/03/29/malicious_backdoor_xz/
https://www.theregister.com/2024/03/29/malicious_backdoor_xz/
Red Hat in all caps says STOP USAGE OF ANY FEDORA RAWHIDE INSTANCES
Kdoes not affect us, only rawhide/F41 (and extremely recent F40 builds)
Kshout out to upstream for catching this
TRed Hat in all caps says STOP USAGE OF ANY FEDORA RAWHIDE INSTANCESthis affects so much more too. happy we're not affected by this. debian sid, arch, gentoo, nixOS unstable, and even the homebrew package are affected too
Co damn thats p spooky, a good catch indeed wow
Ryea xz is kinda wild to have a backdoor
Fthe thing is, even previous xz versions could be affected by merged commits from that user
K5.4.6 stable hasn't been found to have any vulns so far
