Every other thread mentioning a problem “always” mentions it together with “this happens on wayland and not on X”.
In the end, i do not understand the Linux community’s aggressive push of wayland to replace X11. I mean why is the hurry? There are too many issues to resolve still. It is obviously not ready. Why is the rush?
Try to force to run the app through xwayland and see if that works?
Something like
GDK_PLATFORM=x11 chromium # for Electron and GTK apps, probably Chromium too
# or
QT_QPA_PLATF0RM=xcb chromium #for Qt apps
I did the latter with QGis. You can edit the application desktop entry to fix that, but Chromium should support wayland natively so this is a bug (–> bugs.kde.org)
# something like this
cp /usr/share/applications/chromium.desktop ~/.local/share/applications/chromium.desktop
sed -i 's/Exec=chromium/Exec=QT_QPA_PLATF0RM=xcb chromium/g' ~/.local/share/applications/chromium.desktop
I started chromium from a konsole window using the command:
QT_QPA_PLATF0RM=xcb chromium #for Qt apps
and received a long error message ending with:
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
(chrome:10957): IBUS-WARNING **: 09:44:03.402: Failed to mkdir /home/garry
/snap/chromium/2713/.config/ibus/bus: Not a directory
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan
/VulkanError.cpp:101)
at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan
/BackendVk.cpp:493)
at Initialize (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:379)
at Create (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
at operator() (…/…/third_party/dawn/src/dawn/native/vulkan
/BackendVk.cpp:556)