Plasma integration worked with layered Vivaldi, right?
Plasma 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.
CHeh, no rush on our ends, I'm partly just thinking out loud about what all you could eventually try
SAnyways it is getting late and I need to get to bed and thanks so much for your assistance! I'm still new to this immutable distro scene and so far I'm liking it!
SGn
C
R@KyleGospo please push 120 to Deck user.
RLately all shit is breaking loose on my Deck and I'm losing my mind right now.
RRandom shit that keeps breaking on 119
Kshould already be, I rebuilt jupiter-hw-support shortly after that was pushed
RTy
RI'll update then.
RI have no clue what the heck they did with the USB stack on 119.
RBut it also might affect Bluetooth at this point.
Kif you're not already on
:testinggive it a try
LRetroDECK 0.7.5b - Released!
Patch notes are here for those interested:
https://retrodeck.readthedocs.io/en/latest/wiki_rd_versions/version_0.7b/0.7.5b/
Also a new wiki!
Patch notes are here for those interested:
https://retrodeck.readthedocs.io/en/latest/wiki_rd_versions/version_0.7b/0.7.5b/
Also a new wiki!
The Official RetroDECK Wiki
RI think that all subsequent build failed.
RIt's not applying here.
RYep, still 119 on latest testing @KyleGospo
RYeah, same for me
Dwhat is 119 and 120?
RBIOSes
RNope.
RBut the last two days something has began to break lose in my device.
RUSB errors and sleep issues in the bazoo.
Dwhat broke?
