Tthe official app however yeah doesnt work as well
Thonestly no idea ive always used discord on the browser so....
Mdoes vesktop have screen sharing? I’ve literally never tried.
Tif it has a decently updated electron version im pretty sure yeah it should work fine
T
Tseems to work!
MI always just default to that nowadays, especially since they have an rpm. Although the flatpak is also viable.
Mbut I don’t need to share my screen so I’ve never tested it. screenshots or clips via spectacle have always been fine for my own usage
EOh nice. I had been using
discord-screenaudio
Cthx
TBazzite has been successfully installed without my broken ram stick, im glad thats finally behind me cuz damn that was annoying
Di think i almost got this working, but need to turn off plymouth, anyone know how i can do that? i got the hang of regenerating initramfs, but not sure where the plymouth hook is being set
ADamn, brand new pair of headphones from an entirely different manufacturer and Bazzite STILL doesn't wanna connect via bluetooth to em.
This is getting annoying...
This is getting annoying...
Dare you using a usb bluetooth dongle? or motherboard builtin bluetooth?
Dive had the most success with bluetooth receivers that have intel drivers, anything else has been crap. The most notorious was ASUS bluetooth dongle, works fine on windows, but horrible on linux
HSteamOS did something similar
HIt's not Bazzite, it's just Linux
HPeripherals seldom work on Linux
AAnd yet I've had zero issues with my bluetooth headphones with my stock fedora 39 install on both my desktop and laptop
Dim listening to my Sony bluetooth headphones just fine on linux, though they tend to glitch out on occassion and have to reconnect, once in a bluemoon
ASee all the headphones that weren't connecting to my deck all connect to my other linux running devices without issue so it's like???
Dbut my motherboard has intel powered bluetooth antenna, i attribute that to the stability. Was fedora 39 machine the same as the bazzite machine? or is this an entirely separate box you're trying bazzite on?
Hokay that's weird
HBazzite is effectively Fedora 39 so I'm not sure why that's happening
AExactly lmao
AIt makes no sense
AThe machines are similar too, all ryzen based
Dyes, but same board?
Dbluetooth device onboard might be driven by a different controller
Hoh it's a different computer?
Hoh that's why
Hblame it on Realtek then lol
Hcould be an entirely different driver stack between those two computers for all you know
BFor me, I've only been able to have success after putting the little antennae on the back of the mobo, otherwise, even right at my desk, the reception/connection was terrible
Dso i see that initramfs takes in arguments
"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf" but then there is rpm-ostree kargs which seem to be a combination of initramfs args and whatever is in /etc/default/grub, do kargs get populated by /etc/default/grub?Dnvm i guess this answers my question: https://www.reddit.com/r/Fedora/comments/16d96nd/rpmostree_kargs_vs_updating_grub_config/
Dhazzah! it works
Di can unlock my bazzite VM so as long as its on the same network as a tang server
Dif its offline, it falls back to the OG passphrase, so if im at home steam deck/HTPC/laptop should just unlock, would need to figure out a way to make it use VPN on boot if im away from home, but i can just carry around a portable firewall appliance with me that is always on VPN that can work too
Di also did not have to disable plymouth, misread the docs, thought clevis and plymouth were somehow not compatible
KOn legion go. Does anyone have issues calibrating their left controller gyro? It keeps failing due to noise. The right controller gyro calibrates fine.
KHmm reset the controllers and it calibrated.
Pusing an amd RZ608 (mediatek MT7921K) wifi/bt module. bluetooth has worked in the past (don't remember how long ago) but at the moment my scans never discover any devices. nothing is blocked in rfkill, and bluetooth is enabled.
BAny idea why changing desktop resolution isn’t working for me? When applying the screen goes black for about 5 seconds and then reverts back. This could be a passthrough gpu issue but wasn’t sure if there was something I could override on bazzite
Pi left the window scanning for ~15 mins and it eventually detected my neighbour's living room tv. none of my personal devices, which are much closer, are being detected at all. wtf
P
KNot sure on that one, it should work fine.
KWe don't really customize much of anything about KDE to casue that sort of thing
Kcould try changing the res w/ kscreen to see if that works around it
