disturbed display of vivaldi menu and KDE menu
-
My Vivaldi 5.1.2567.66 (Stable channel) stable (64-Bit) on Fedora 35 disturbes the display of KDE start menu (not usable, starts getting displayed but quickly drops away) and as well the menu of the Vivaldi menu (same effect). Plus the display overall gets light irritation irregularly every some seconds.
This effect does not take place with other browsers
Reproducable
Is this a bug?
-
@aburwitz Fedora uses Wayland by default right? Could it be related to that and possibly your nvidia card? There are some posts related to Wayland already.
-
I saw such isdue this last year only with broken Compositing in KDE environments.
-
Fedora leaves a choice at install and right, it's wayland in my system
-
@aburwitz said in disturbed display of vivaldi menu and KDE menu:
Fedora leaves a choice at install and right, it's wayland in my system
But there's no Nvidia card
-
Have to fallback to Firefox, as this behaviour is not usable in my work...
will look back to Vivaldi after next updates and check, as I like it. But that doesn't help when I cannot use it
-
@npro said in disturbed display of vivaldi menu and KDE menu:
Fedora uses Wayland by default right?
Fedora Workstation [ie, gnome] uses W by default, but not KFedora, which the OP apparently has. With KF, just like any KDE, on the SDDM screen the user can choose the X11 or Wayland Plasma session.
I tested the OP's claim in my F36 Branched VM. It all worked as expected for me, both in X11 & Wayland Plasma sessions, wrt both the KDE App Menu, & the V menu.
X
W
-
@guigirl But it's still first in the list, no? Btw wasn't OP supposed to be running V with the
--ozone-platform
et al. switches? -
@npro said in disturbed display of vivaldi menu and KDE menu:
still first in the list, no?
You might be right, i can't recall atm.
@npro said in disturbed display of vivaldi menu and KDE menu:
running V with the --ozone-platform et al. switches?
Well, my intention last night was to do one X11 + two W tests, but as it turned out i was only able to the Xwayland app one when in W, coz when i attempted the second one to run V as full-W via Ozone, it threw errors & aborted. It was very late & i was very tired so i didn't feel like troubleshooting it [tbh, i strongly suspect it's a 36 Branched problem, remember those error messages?]. Prolly i need to retest in one of my other, stable, Fedora 35 VMs... but wrt this thread, & the OP having already given up & walked away, i feel my motivation waning...
-
Fwiw [& noting that OP still has not reappeared here], i had another go at this, but instead of my F36 Branched VM, i used my F35 Stable VM. In its existing logged-in X11 session, i did a full system update [last done weeks ago], then installed V Stable, rebooted, logged into Plasma Wayland, launched V with
vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
in Konsole, & observed afaict entirely normal/proper/correct behaviour.Ergo, once again i have been unable to reproduce the OP's claimed symptom.
Update: Nope, not all good after all. It's the damndest thing. That initial launch of V-W went fine, as described. However, no subsequent V-W launch has worked correctly. The V icon appears in the Plasma Task Manager in the Plasma Panel as expected, all the usual individual processes appear in System Monitor... just one tidly little detail is amiss ... no actual V window appears at all.
Shazbot.
-
Back in the F36 Branched VM, i did the latest batch of updates & rebooted, then decided to log into its GNOME [rather than KDE] Wayland desktop first. Fired up V from terminal with
vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
. Once the proper V window appeared, it seemed to behave fine. In itsvivaldi://gpu
:XDG_SESSION_TYPE wayland Ozone platform wayland
Logged out of GNOME, logged into Plasma Wayland, launched V again from terminal, & it seems fine. In its
vivaldi://gpu
:XDG_SESSION_TYPE wayland Ozone platform wayland
NB: Not in my GNOME login, only in my KDE login today, my initial attempt to launch V once again resulted in the V processes appearing, & the V icon appearing in the Plasma Panel Task Manager, but no actual V window. Confused, i eventually realised my mistake; i'm so used to Arch that i forgot that whereas in Arch V Stable launch command is simply
vivaldi
, whereas in Fedora it must bevivaldi-stable
. I got it right when i was in GNOME, but slipped up initially once in Plasma. It transpires that when launched only asvivaldi
in KF-W, the window is not created, but once correctly launched, all is good.I now strongly suspect that i made this same silly error in yesterday's F35 test, so am about to try that again...
F35 tba... --> upon initial relaunch today of my F35 Stable VM, i verified that in fact i had NOT made a launch command error; i had indeed usedvivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
... & again today the V window did not appear.Then, i found that 22 packages were available for update, including several fedora wayland library packages. I applied the updates, logged out/in, repeated the launch command... & voila, V is good! In its
vivaldi://gpu
:XDG_SESSION_TYPE wayland Ozone platform wayland
So, it had been a Fedora problem, not a V problem. With that resolved, F35's V-W behaviour is normal, no menu or other hassles experienced.