https://bugs.kde.org/show_bug.cgi?id=497548
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=497548
--- Comment #8 from Bug Janitor Service ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it wi
https://bugs.kde.org/show_bug.cgi?id=497548
John Kizer changed:
What|Removed |Added
CC||john.ki...@proton.me
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=497548
Nate Graham changed:
What|Removed |Added
Keywords||wayland-only
--- Comment #6 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=497548
David changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REP
https://bugs.kde.org/show_bug.cgi?id=497548
--- Comment #4 from Bug Janitor Service ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it wi
https://bugs.kde.org/show_bug.cgi?id=497548
--- Comment #3 from Nate Graham ---
Yeah, you'll have to launch the app with a special flag. Every app does it
differently. For Chrome/Chromium, you add "--ozone-platform=wayland" to force
it into Wayland mode, and without that, it's in XWayland mode. S
https://bugs.kde.org/show_bug.cgi?id=497548
--- Comment #2 from David ---
(In reply to Nate Graham from comment #1)
> Does it happen in Chrome or Chromium too?
>
> Can you test when all of these browsers are in native Wayland mode as well
> as in XWayland mode?
Does "native Wayland" and "XWayla
https://bugs.kde.org/show_bug.cgi?id=497548
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
