Bug 407581 - New Intel Iris don't works with Wayland
Summary: New Intel Iris don't works with Wayland
Status: REOPENED
Alias: None
Product: frameworks-kwayland
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.59.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-16 07:10 UTC by NR
Modified: 2020-01-01 23:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Syslog while running plasma wayland (100.06 KB, text/plain)
2019-10-23 11:55 UTC, hexchain
Details
stderr from startplasma-wayland (9.87 KB, text/plain)
2019-10-23 11:56 UTC, hexchain
Details
startplasma-wayland stderr with Iris driver (81.20 KB, text/plain)
2019-10-31 22:07 UTC, hexchain
Details
startplasma-wayland stderr with i965 driver (98.18 KB, text/plain)
2019-10-31 22:08 UTC, hexchain
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NR 2019-05-16 07:10:13 UTC
SUMMARY

Hi,

I don't know If this bugtracking is the correct place, or maybe at Intel developers.

Please, if you need some log file, ask me.

I try to use the new Intel Iris graphic driver.
I use latests drivers since the first day with Neon installed (sudo add-apt-repository ppa:oibaf/graphics-drivers)

If I try to log in with Plasma Wayland doesn't start Plasma.
Alt + F3 to get a terminal, "top" and I can see all process normally running. WiFi and all Plasma components starts, but the logging screen stay satic.

I use "sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 xwayland-hwe-18.04".
Also, I tried the 5.0 kernel from Canonical with the same result (Iris driver have memory leak with 4.18 kernel).

STEPS TO REPRODUCE
1.
"sudo vim.tiny /etc/profile.d/galliumiris.sh && sudo chmod 644 /etc/profile.d/galliumiris.sh"
+ lines
#!/bin/sh
MESA_LOADER_DRIVER_OVERRIDE=iris
export MESA_LOADER_DRIVER_OVERRIDE

2.
Try to logging with Plasma Wayland. The screen logging is static.

3.
"Alt + F3" and "sudo rebot"
Choose "Pasma" (X11) and everything runs perfectly.


OBSERVED RESULT
Loggin screen static.

EXPECTED RESULT
See th Plasma desktop.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12
Comment 1 NR 2019-06-12 12:13:26 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.
Comment 2 Christoph Feck 2019-07-03 15:26:20 UTC
> Plasma Wayland doesn't start Plasma

To check if this is a driver issue, please test 'Weston' reference compositor.
Comment 3 NR 2019-07-03 20:15:01 UTC
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.
Comment 4 Christoph Feck 2019-07-03 20:19:31 UTC
Thanks for the update; changing status.
Comment 5 hexchain 2019-10-23 11:54:21 UTC
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.
Comment 6 hexchain 2019-10-23 11:55:46 UTC
Created attachment 123438 [details]
Syslog while running plasma wayland
Comment 7 hexchain 2019-10-23 11:56:21 UTC
Created attachment 123439 [details]
stderr from startplasma-wayland
Comment 8 hexchain 2019-10-31 22:07:32 UTC
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.
Comment 9 hexchain 2019-10-31 22:08:50 UTC
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)
Comment 10 carbonchauvinist 2019-11-10 19:54:47 UTC
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.
Comment 11 carbonchauvinist 2020-01-01 16:51:39 UTC
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