Can I ask rq what flatpak version bazzite is on (`flatpak --version`) ?
Can I ask rq what flatpak version bazzite is on (
flatpak --version) ?
EDeck/SteamOS is on 1.14.4 from March, curious if bazzite is more recent
K1.15.6
EThank you 
Knp
EMight have to give bazzite a whirl then
A@KyleGospo after 3 reboots, i didnt get a single time the grub partition selection
Kyou using desktop or deck version of bazzite?
Adesktop-nvidia
Kshould have grub then, you can't not have it
Kan d it's not hidden by default on that image
Kyou don't see a picker for previous and current bazzite release at boot?
Afor bazzite, yes, not also for windows
Aalso, its strangely quick for bazzite
Kujust regenerate-grubworked
Aty
AIs ally testing gonna move to latest soon?
A@KyleGospo did you end up adding the LGO controller emulator yet? If not, there's an alternative version of it that I'd consider potentially better for long term maintenance: https://github.com/antheas/hhd
K@__aru not yet
AThis one basically does the same thing, but has less bugs and is configurable via config file
AAlso handles power button, so you won't need to separately include steam-powerbuttond
AI've been testing it for a few days now, and it's been pretty stable
KThanks, I'll check this out
AThat being said, this one can be installed on Bazzite fairly easily, unlike rogue-enemy (other controller emulator). hhd might not need to be pre-installed on Bazzite
RYeah, it broke again on my LCD on Bazzite, it's not stable.
S
SMy Vivaldi seems to be broken
SIs it something to do with my Nvidia drivers being updated?
SOr a kernel update?
SBefore I switched to Bazzite I used OpenSUSE Tumbleweed for quite awhile but this would always pop up whenever my kernel or other system package was upgraded but I hope this isn't the case with all rpm based distros.
KNot sure there, I don't use Vivaldi and haven't experienced issues like that before
SIf you are wondering yes I installed the Native rpm package from Vivaldi's website using rpm-ostree
K
KTry the flatpak
SI have heard that they are "Testing the waters" with the new flatpak version and that it is "Not Approved" by them yet because of some security thing in Chromium based browsers. Is it stable and secure?
Tit's the sandboxing in chrome they're referring to that flatpak replaces with its own security measures
Tthis is maintained by a vivaldi employee, but yeah the sandboxing that chromium uses is not here
Ti dont think it's a major security risk however
SSo would I be safe to use the browser and it should be stable as well?
Ti cant speak for stability lol but it should be fine security wise i would say
Ti mean you can just install it and see if your issue still persists on the flatpak version
SGood to know, thanks!
Tif it does, or you don't like it simply uninstall it
CIt's at least as secure as every other chromium-based-browser-flatpak since they all rely on the patches developed by one person (refi64, Ryan Gonzalez) who also maintains several of the flatpaks. According to him, theoretically there may be edge cases in the chromium sandbox where it's adapted to make flatpak sandbox calls, but those edge cases should be low risk. None of the other contributors to any of those projects has found any edge cases or security holes. The Vivaldi flatpak should be roughly as stable as all other packages, or a bit more so
SOkay I have it installed but plasma browser integration doesn't seem to be working, is there something in flatseal that I can do?
CGood question. Does that integration work for other chromium based browser flatpaks?
SThat part idk bc the only other browser I've used under flatpak is firefox and it seemed to work if I remember correctly.
SAnd for that I never had to change anything in flatseal.
CGotcha. I'd say check the Chromium flatpak just in case - if it does work there, it may well be a flatseal permission issue
CAnd especially if we track down which one, it'd probably be worth opening an issue on the Vivaldi flatpak repo to get the default changed
