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
CIt's good to know that Firefox does work. If base Chromium doesn't, it could potentially be a chromium-based issue
CPlasma integration worked with layered Vivaldi, right?
SI can check that one tomorrow and with Firefox I could be misremembering so I will try after school tomorrow.
SYes, installed with rpm-ostree
Calso, I may have just remembered what could cause this, but I am very much not sure
CNvidia GPU?
SMy Dell XPS 15 9510 does have a 3050 Mobile.
CAha, point toward my suspicion
C
CI've had issues with this flag before, but after my main monitor died, I had issues with Vivaldi on my laptop's internal screen, turned it on, and no longer had issues
CI'm using the Vivaldi flatpak on the 11-20-2023 build of Bazzite - the last one with the 535 driver since 545 breaks Gnome experimental VRR
SI'm using Wayland now but when I was on OpenSUSE Tumbleweed with Xorg the problem still occurred.
Coh, huh
Cthen I maybe have no idea
SThe problem never happened back when I used CachyOS so maybe it is a problem with rpm based Distros?
CI don't see how it could be, but maybe..?
CYou said it seems to be kernel-related, yeah?
SGitHub
KDE has extension for Google Chrome / Chromium to provide integration with Plasma (and partly XFCE) desktop (Media playback, file downloads, KDE Connect etc). It's called Plasma Browser Integra...
SYeah on TW every time my kernel updated the problem would happen and it would only go away when Vivaldi updated, no Nvidia Driver updates ever fixed it nor did any further kernel fix it either
CAh, hmmm
CYou might try rebasing back to the December 2nd or November 20th builds of Bazzite to see if the issue still occurs
SWhenever I updated the kernal on CachyOS the problem never happend which is weird.
CThe former should revert a kernel update, and the latter should revert a Nvidia driver update
CI hadn't known/remembered CachyOS, so I initially thought it might use an older kernel, but it seems to use roughly the latest kernel version, but with various modifications under the hood
Cain't got scratch on rebasing to date tags for troubleshooting though lol
SMaybe I should embrace the Flatpak version from now on and see how that goes, if can remember to I can try out the different browsers to see if they have the plasma browser integration problem or not tomorrow after I finish up high school for the day.