Summary: | New Intel Iris don't works with Wayland | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kwayland | Reporter: | NR <me> |
Component: | general | Assignee: | Martin Flöser <mgraesslin> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | carbonchauvinist, nate |
Priority: | NOR | ||
Version: | 5.59.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Syslog while running plasma wayland
stderr from startplasma-wayland startplasma-wayland stderr with Iris driver startplasma-wayland stderr with i965 driver |
Description
NR
2019-05-16 07:10:13 UTC
I updated the "version" field to 5.59.0. Can I help? I don't know if I can provide some logs or test something. > Plasma Wayland doesn't start Plasma
To check if this is a driver issue, please test 'Weston' reference compositor.
Hi, I changed the status to "NOT A BUG" because I installed Weston with the same result. Tomorrow I'll find at Iris issues and write down my info. Best regards and sorry for waste your time. Thanks for the update; changing status. I have the same problem with Iris driver (mesa git f764725b3e) and Plasma 5.17.1. Weston starts just fine, but Plasma does not. All I can see is a functional(?) mouse pointer on a black screen. It seems that Qt tries to load the xcb platform plugin when Iris is in use. Under weston + iris, running qdbusviewer shows a window with blurred texts (I have 2x scaling so that almost means Xwayland is in use), but with "-platform wayland" texts are sharp and clear. Created attachment 123438 [details]
Syslog while running plasma wayland
Created attachment 123439 [details]
stderr from startplasma-wayland
Created attachment 123630 [details]
startplasma-wayland stderr with Iris driver
This is a new log, running:
QT_LOGGING_RULES="kwin*=true;qt.qpa*=true" startplasma-wayland
in a tty session, with MESA_LOADER_DRIVER_OVERRIDE=iris.
Created attachment 123631 [details]
startplasma-wayland stderr with i965 driver
The same command, except without MESA_LOADER_DRIVER_OVERRIDE (i.e. with the default i965 driver)
Have same behavior described by hexchain with following setup: Version ======= KWin version: 5.17.2 Qt Version: 5.13.2 Qt compile version: 5.13.2 XCB compile version: 1.13.1 Operation Mode: Xwayland Build Options ============= KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_EGL_STREAMS: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12005000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 $ uname -a Linux 5510 5.3.8-arch1-1 #1 SMP PREEMPT @1572357769 x86_64 GNU/Linux Am able to start plasma X11 session or a SWAY plasma session just fine while using the iris driver also. I'm now able to start a plasma session successfully with the iris driver! $ qdbus org.kde.KWin /KWin supportInformation ... Version ======= KWin version: 5.17.4 Qt Version: 5.14.0 Qt compile version: 5.14.0 XCB compile version: 1.13.1 ... Compositing =========== Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 530 (Skylake GT2) OpenGL version string: 4.6 (Core Profile) Mesa 19.3.1 OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Intel GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 19.3.1 Linux kernel version: 5.4.6 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no $ printenv |grep iris MESA_LOADER_DRIVER_OVERRIDE=iris |