https://bugs.kde.org/show_bug.cgi?id=500403

John <ilikef...@waterisgone.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOT A BUG                   |---
     Ever confirmed|0                           |1

--- Comment #10 from John <ilikef...@waterisgone.com> ---
In the meantime, Mesa 25 came with the updates yesterday:
glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
    Device: Mesa Intel(R) UHD Graphics 620 (KBL GT2) (0x5917)
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.0-1
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.0-1
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.0-1

kinfocenter (running from terminal in the Wayland session), still doesn't show
the pills and has the same output:
qt.qml.typeregistration: Invalid QML element name "Hint"; value type names
should begin with a lowercase letter
Failed to load vulkan: Cannot load library vulkan: vulkan: cannot open shared
object file: No such file or directory
initInstance: No Vulkan library available
Failed to create platform Vulkan instance
Failed to create vulkan instance
GPU count mismatch (from vulkan) 0 2
Looking at QList("/usr/bin", "/usr/lib/qt6/libexec",
"/usr/lib/qt6/libexec/kf6", "/usr/lib/x86_64-linux-gnu/libexec",
"/usr/lib/x86_64-linux-gnu/libexec")
"/usr/lib/x86_64-linux-gnu/libexec/kinfocenter-opengl-helper"
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0

Is it possible that this new major upgrade of Mesa, with its Vulkan and OpenGL
drivers also is packaged wrong, with something missing?
I think it's probably a low chance that both Mesa 24.3 and 25 is packaged wrong
in Debian and whatever Mesa is in KDE Neon is also wrong.
Maybe some of these errors in the output mean something.
Shouldn't the underlying OpenGL or Vulkan functions used to get info about the
GPUs work the same on X and Wayland?
To me it doesn't make much sense why it doesn't work only on Wayland, which is
what I use by default for years and I have no intention to get back from it as
all my computers intentionally use only AMD and Intel GPUs.
Feel free to close the report if this cannot be resolved now for whatever
reason!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to