kwallet-tools-5.25.0git.20160724T133134~8cf7300-2.2.x86_64 Best get in contact with us to check what works and if you are interested: please help in adding support for it. Unfortunately all popup menus were placed in previous position of main menu, not current. Maybe it’s caused by having color correction enabled, maybe because of using OpenGL core profile (though one of your debug outputs doesn’t show it). It will work.  https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/ Follow their code on GitHub. Looks like the pageFlip fails, but why? It is unclear how this will evolve. > QSocketNotifier: Invalid socket 29 with type Read, disabling… OpenGL shading language version string: 4.30 OK. I do have the kwayland-integration package installed. That’s a problem I have never heard of – for me lock screen is always working. I was able to interact with kwrite without any problems – I wrote some word in this editor. xprop: unable to open display ” _XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed Virtual Machine: no Mesa version: 11.2.2 synchronous: QVariant(qlonglong, 1) cat /etc/pam.d/system-login More information about what was introduced in KDE SC 4.9 can be found at the following link: Sometimes the screen position of an application is vital to your comfort, so use the flexibility of KWin to make sure it's always where you want it. If I switch to VT2 and run `kwrite –platform wayland`, it seems to show success (“Using Wayland-EGL”), but when I switch back to the first VT, it… well, it doesn’t actually refresh the screen, I still see the contents of VT2, just without the cursor blinking. The most often problem I have heard is that KWin freezes at this point and gdb shows KWin is in the main event loop. qtwayland5-5.6.1-2.mga6 OpenGL version: 3.0 > Configuring Lock Action GLSL version: 1.40 Here the experience differs and I myself don’t know exactly what is supported on which hardware and in which setting combination. I’m not able to detect a pattern for your system. import QtQuick.VirtualKeyboard 2.1 Also from testing it looks like KWin has problems with starting a working Xwayland in a nested setup with the OpenGL compositor. X-Server started on display :1 libwayland-egl-devel-12.0.1-141.1.x86_64 QObject::connect: invalid null parameter Tested nested kwin_wayland on Mageia 6 (Plasma 5.7.1, Frameworks 5.24): the kwin window opens without errors, but when I tried launching kwrite/konsole in it, the window remained black: however, the mouse cursor changed as I moved it, as if the application was there, only invisible, and I’m pretty sure I could interact with it (didn’t manage to save a text file blindly though), Kwin_wayland output: Actually, I just found that D-Bus was failing to start elogind. Simply means "current directory" https://s7.postimg.org/3pneqkgyj/20160807_162240.jpg, kept an eye on kde and wayland for some time now. Elaborate checks have been build in to ensure users with low-end hardware are not presented with an unusable setup. GPU class: Unknown $ kwin_wayland –xwayland Here I experienced some wired problem with handle of keyboard. Wouldn’t it be possible to try and simulate that by simply not having a video card driver other than llvmpipe built into Mesa? I could start KRunner and with it other applications, but then at some point the whole system froze, having me need to do a hard-poweroff. I have also Qt-5.7.0 and KF are built with this Qt. The problem is more that we often don’t know what was the cause. The options open to you may depend on your distribution or theme, and it's clear that there is more to come. Since 5.4 KWin is able to manage Wayland clients and this allows to start a Plasma session on Wayland. Here you can enable effects to more efficiently manage your windows. This means that the platform/backend plugin is not installed. kwin_core: Creating egl surface failed Service started, version: 7.0.0 I wasn’t able to reproduce this behavior. –> as a reference, I get a constant 60 FPS in all conditions with a super slow Intel HD 3000 or a more recent Intel HD 530… _XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed the pageFlip is in the drm layer so after OpenGL/llvmpipe. The most common reason for this is that your environment does not contain the XDG_RUNTIME_DIR environment variable. file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-log-out kwin_core: Egl Initialize succeeded $ kwin_wayland –xwayland Setting the name of 0x13b3970 to “org.kde.ActivityManager.RunApplication” Texture NPOT support: yes Pastebin is a website where you can store text online for a set period of time. session optional pam_elogind.so OpenGL version string: 3.1.0 NVIDIA 364.19 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/user-identity I mean in password field cursor was blinking, but I wasn’t able to type any letter, only digits and other characters like colon, dot, slash, etc. Drag icons there to where you want to see them. QSocketNotifier: Invalid socket 12 and type ‘Read’, disabling… file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-switch-user.  with kwin 5.6.5, kf5 5.24.0, kde applications (dolphin, kwrite, …) 16.04.3, qt5 5.6.1, mesa 12.0.1, kernel 4.6.4, ah running in a wayland session requires adding another argument: –socket=wayland-1, Otherwise KWin tries to use wayland-0 and fails. Thank you so much for writing this. Before installing Plasma, make sure you have a working Xorg installation on your system.Install the plasma-meta meta-package or the plasma group. Why not a new Compositor? You may find that you have other icons available to you. Driver version: 367.35 export QT_QPA_PLATFORM=wayland Linux kernel version: 4.7 import QtQuick.Enterprise.VirtualKeyboard 2.0 Or is it really a kernel driver issue? pam_kwallet-0.0.1git.1454233429.d749c2d-31.1.x86_64 kwin_core: Init of kglobalaccel failed Works fine for me on Fedora 24. bash: bashtop: command not found. fails to show a window with black background. Then it shows some artifacts and then it freezes. KWin has seen many performance improvements to enable these effects even on low-end hardware. kwin_core: The used windowing system requires compositing – Option 2 works fine (there is no window to resize, after all, – Running startplasmacompositor from a VT did show the splash, but then I just got a black screen with a cursor. KCrash: Attempting to start /usr/bin/plasmashell from kdeinit whatever command I type I keep getting "bash: ls: command not found". Thanks to the work on OpenGL ES 2.0 our default compositing backend is now OpenGL 2.x based instead of OpenGL 1.x as it was till 4.6. OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile Texture NPOT support: yes OpenGL shading language version string: 4.30 From the other system (on tmux or not, although I find it useful to just put it in another tab) we can run sudo gdb --pid `pidof kwin_wayland` and it will attach. Improvements in the existing effects make window management smoother than ever. So start your normal X session and run a nested KWin: This means that KWin failed to create the Wayland server socket. By the way its a "SunOS" I don't have choice in the matter, as its … You can for example use the Present Windows as the effect for window switching. Driver: Intel Using Wayland-EGL 2. In which case, wouldn’t that mean it should be filed as a bug against the kernel or such? Requires strict binding: no GLSL shaders: yes kwin_wayland –xwayland –libinput –drm –exit-with-session=kate force the (full or not) composition pipeline; However… When applying 1) or 2), kwin animations are very inconsistent. On Acer Aspire One I find that 8 point is a good base settings. Day 1. OpenGL version: 3.3 Click with your right mouse button on a window decoration or use System Settings to access the new and easier configuration of KWin. Driver: Intel Curing graphics problems depends on knowing the correct drivers for your graphics card. $ kwin_wayland –xwayland I cannot move the cursor, although if I claw at the screen enough it sometimes turns into an “I” shaped cursor. file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:41: TypeError: Cannot read property ‘length’ of undefined Column/List of items to CSV, . Purchase books, mugs, apparel, and more to support KDE. Texture NPOT support: yes Just use the Alt-Tab keysequence and keep the Alt key pressed. I was able to run nested session (with kwrite inside) – like you described. file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/main.qml:29: TypeError: Cannot read property ‘Layout’ of null Acknowledgement sent to Martin Insulander : New Bug report received and forwarded. The only options with systemd/logind in dbus configure are glamor: EGL version 1.4 (DRI2): file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-switch-user. OpenGL renderer string: GeForce GT 430/PCIe/SSE2 u/Yummychickenblue. – Trying to start Plasmay (Wayland) from SDDM got me a Plasma, which however crashed pretty quickly. export QT_QPA_PLATFORM=wayland kwin_core: EGL version: 1 . In output I have received (I put only errors): The most likely you are right. wal_autocheckpoint: QVariant(qlonglong, 100) I would like to handle this better, but I don’t have a system without logind to test. wayland-devel-1.11.0-1.3.x86_64 Please activate all KWin related debug categories, run it again and report a bug against KWin – ideally for the platform you used. i can get weston working but not kde-wayland…, had to use arches aur weston-eglstream to get it working. Texture NPOT support: yes When pressing Ctrl+C I get a segmentation violation crash in kwin_wayland: “kwin_wayland: segfault at 20 ip 00007f5ba9aa8952 sp 00007fff9f538378 error 4 in libwayland-server.so.0.1.0[7f5ba9a9d000+10000]”. It’s an i686 Poulsbo tablet, so while it’s using Mesa DRM drivers, they don’t have hardware acceleration and thus it’s all llvmpipe or friends. or the current kwin code does not support whatever stuff done in a wired way by nvidia? kwin_core: We are going to quit KWin now as it is broken. GLSL shaders: yes Thanks! lib64wayland-cursor0-1.11.0-1.mga6 > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. And the caching command just didn’t run for upgrade, probably because of some weird conflict of latest g++ library and the one required by some packages (in fact, after upgrade even Xorg didn’t run, but I figured it out and fixed). apt-get remove kwin -y Step 2: The command reads the package lists and proceeds with the uninstallation. OpenGL version string: 3.3 (Core Profile) Mesa 12.0.1 Here you can enable effects to more efficiently manage your windows. OpenGL vendor string: NVIDIA Corporation Requires strict binding: no allright, it’s the lack of GL_OES_EGL_image. You can take control and disable these checks or change settings like the global animation speed to fine-tune your experience. Applying the debugging settings from https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/#comment-71360 OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) works fine and reports wayland windowing system. OpenGL vendor string: Intel Open Source Technology Center It’s a runtime dependency of KWin. After executing the command, restart the terminal for the new $PATH value to take effect. Session path: “/org/freedesktop/login1/session/_32” The second option is set by build system. Before you ask your administrator for help, please consider the following points- QObject::connect: invalid null parameter I took care other things and forgot for a moment about Wayland session. Configuring Lock Action wayland-tools-1.11.0-1.mga6 query_only: QVariant(qlonglong, 0) When I back to Wayland sessions I got locked screen (sddm like). Requires strict binding: no /bin/bash: yarn: command not found - using circleci/ruby:2.5.0-node-browsers. I’ve gathered that there might be something going on with MS VSCode C++ Plugin or something to do with Python or something to do with AV Software. OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Click with your right mouse button on a window decoration or use System Settings to access the new and easier configuration of KWin. > QObject::connect: invalid null parameter Like calling to start xwayland: we know it failed, but not that it’s not installed. As the comment section may not be appropriate/efficient for a ‘debugging’ session, I’ve changed my email address to one I actually check on a regular basis. Then at some point my system froze again. If you want to try Wayland please always first try the nested setup. KWin works fine in the nested setup: awesome. Position the window where you want it to open, then right-click on the title-bar, choosing Advanced -> Special Window Settings. What could also help is enforcing qpainter compositing as KWin still ignores llvmpipe. (this one was also tested with git versions of Qt, frameworks and plasma), One cannot start konsole with the exit with session argument. org.freedesktop.login1 is available Intel drivers (xf86-video-intel) was: 2.99.917.8-1 (in Mageia 6 it was: 2.99.917-26). libkwalletbackend5-5-5.25.0git.20160724T133134~8cf7300-2.2.x86_64, unfortunately, gnupg still doesn’t have a wayland pinentry client (as far as I understand, the Qt-version uses the Xcb plugin in order to place the window properly and take the focus). QObject::connect: invalid null parameter dbus: [system] Successfully activated service ‘org.freedesktop.login1’, I looked for all login1 mentions in kwin sources and according to qdbusviewer Just read through the code and I think it fails in eglInitialize. Log in to a tty and setup similar to nested setup – I recommend the exit-with-session command line option to have a nice defined setup to exit again: export $(dbus-launch) kwin_core: Failed to initialize compositing, compositing disabled Does it bypass login1? No backend specified through command line argument, trying auto resolution xorg-server-xwayland: 1.18.3-3 Don’t have another wayland compositor running on the same user name. OpenGL version string: 4.3 (Core Profile) Mesa 12.0.1 This will open a settings window, with appropriate entries already made. kwin_core: bind OpenGL API failed libkwinglutils: Update of color profiles failed kwin_core: Failed to initialize compositing, compositing disabled GPU class: Unknown Cleaning up…, kwrite output: The four most common reasons why you may see the “command not found” message in the Mac command line are as follows: the command syntax was entered incorrectly the command you are attempting to run is not installed the command was deleted, or, worse… Change the "xfwm4" part (and only that part) so it's more like this: . kwin_wayland –xwayland –exit-with-session=kate The Plasma crash seems to be fixed but there are still a lot of bugs left, I will report them. Requires strict binding: no With this blog post I want to show some of the most common problems and how to diagnose correctly what’s going wrong. import QtQuick.VirtualKeyboard 2.1 PSA: The kwin command got split into kwin_x11 and kwin_wayland. On SkyLake platform I use driver from git in version: 2.99.917+676+g26f8ab5-1. The "." Did the Wayland compositor die? libwayland-server0-1.11.0-1.3.x86_64, I use kwallet with a gpg backend and pinentry-qt window will not want to apper in the wayland desktop… seems to be somewhere in the curses version since I get the time out message from kwallet. For the full experience, you need to use OpenGL mode. Just tell me what to do. kwin_core: We are going to quit KWin now as it is broken. lib64qt5waylandclient5-5.6.1-2.mga6, Full output is following: http://pastebin.com/9R6h4G9Q. $ kwin_wayland –xwayland GLSL shaders: yes (kwin_wayland:1860): Gtk-WARNING **: cannot open display: OpenGL version: 4.3 Feel free to use it if you want. To make windows run inside this nested kwin_wayland one needs to Creating directory: “/home/piotrm/.local/share/kactivitymanagerd/resources/” lock called dbus: [system] Activating service name=’org.freedesktop.login1′ (using servicehelper) To select kwin as window manager, select it from the Preferences > LXQt settings > Session Settings panel menu item. GLSL shaders: yes _XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed I was looking for info like this for some time as Ive never managed to start KDE with wayland even though I have been trying for some time. 1. Linux kernel version: 4.6.3 There are still some issues with certain hardware, more info about that can be found on techbase. It will notify you if it does so, and you can re-enable compositing by pressing Shift+Alt+F12. Virtual Machine: no display :1 libwayland-cursor0-1.11.0-1.3.x86_64 kwalletd5-5.25.0git.20160724T133134~8cf7300-2.2.x86_64 So “kwin_core: bind OpenGL API failed” has been replaced with “kwin_core: choose config failed”, but it’s otherwise identical. ^ kwin_core: The used windowing system requires compositing I am on a setup with kde pretty up to date, few days behind the git, kernel 4.7.0, qt 5.7.1, [16:46:42 drFaustroll@circassia:~]: rpm -qa | grep -i wayland Using Wayland-EGL Mesa version: 12.0.1 4. file:///usr/share/kwin/virtualkeyboard/main-enterprise.qml:21:1: module “QtQuick.Enterprise.VirtualKeyboard” is not installed To simply move things around you work with the specimen titlebar. Linux kernel version: 4.6.4 Driver: NVIDIA Also possibly relevant is that I’m using plasma 5.6 as not all 5.7 packages have been uploaded to sid, but I could upgrade the following packages to 5.7 if that would help: bluedevil breeze breeze-cursor-theme kde-cli-tools kde-cli-tools-data kde-config-gtk-style kde-config-screenlocker kde-config-sddm kde-style-breeze kde-style-breeze-qt4 kde-style-oxygen-qt5 kgamma5 khotkeys khotkeys-data kinfocenter kscreen ksysguard ksysguard-data ksysguardd kwayland-integration kwin-common kwin-data kwin-style-breeze kwin-wayland kwin-wayland-backend-x11 kwin-x11 kwrited libkdecorations2-5v5 libkdecorations2private5v5 libkf5libkdepim-data libkf5libkdepim-plugins libkf5libkdepim5 libkf5sysguard-bin libkf5sysguard-data libkscreenlocker5 libksgrd7 libksignalplotter7 libkwin4-effect-builtins1 libkwineffects8 libkwinglutils8 libkwinxrenderutils8 liboxygenstyle5-5 liboxygenstyleconfig5-5 libprocesscore7 libprocessui7 milou oxygen-sounds plasma-integration plasma-pa qml-module-qtquick-controls-styles-breeze systemsettings user-manager. There is a tutorial on defining your own rules for the behaviour of specific windows on the KWin Rules pages. Take a look at System Settings -> Application Style -> Window Decorations -> Buttons tab. kwin_wayland --xwayland, This should create a black window. _XSERVTransMakeAllCOTSServerListeners: server already running https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/#comment-71360, http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-Wayland-Design-XDC, https://firstname.lastname@example.org/msg00030.html, https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/. Hmm not sure whether we really need it or whether there could be a replacement. Oh you didn’t export the variable. Just something gone wrong. ksylvest March 16, 2018, 5:33pm #7 This page was last edited on 23 May 2020, at 12:53. Error message: unable to lock lockfile /run/user/[uid]/wayland-0.lock, maybe another compositor is running PSA: The kwin command got split into kwin_x11 and kwin_wayland. X-Server started on display :1 $ export $(dbus-launch) OpenGL renderer string: GeForce GT 430/PCIe/SSE2 OpenGL version string: 4.3 (Core Profile) Mesa 12.0.1 Restarting it Konsole inside that session worked, but it crashed again pretty quickly with this message (with the object number being different each time): wl_display@1: error 0: invalid object 174 Show your love for KDE! OpenGL version: 3.3 OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile I think it wouldn’t help much as we don’t have the hardware to properly investigate. _XSERVTransMakeAllCOTSServerListeners: server already running The effect itself does not seem to do anything on my computer, but I think you can enable/disable it through dbus in this way: Enable. Requires strict binding: no Using that tool you can either set a specific font size, or better still, tell it to use your KDE desktop settings. No backend specified through command line argument, trying auto resolution This is the tricky situation. No backend specified through command line argument, trying auto resolution GPU class: SandyBridge The Gallery holds many screenshots of past and present desktops and effects. All you need to do now is select the Size & Position tab and check Position and Size. OpenGL shading language version string: 3.30 Texture NPOT support: yes We'll assume you're ok with this, but you can opt-out if you wish. 4 It works pretty much the same as on KDE Neon (artefacting all over). KCrash: Application ‘plasmashell’ crashing… Yes one can go crazy and try running KWin on devices like the Nexus 5, Virtual Machines or NVIDIA based systems. Full output from kwin_kwayland was following: $ kwin_wayland –xwayland All was OK. After that I moved window and I did the same. file:///usr/share/kwin/virtualkeyboard/main.qml:21:1: module “QtQuick.VirtualKeyboard” is not installed Please get in contact with your distribution on how to get the logind DBus interface installed (this does neither require using systemd nor logind). Here is the tutorial to learn how to uninstall kwin with apt-get command. _XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed kwin_wayland –xwayland –libinput –framebuffer –exit-with-session=kate GPU class: GF100 Nevermind, sorry for the noise. Using Wayland-EGL, After launching kwrite, I can terminate it correctly by pressing Ctrl+Q in the window, Testing Mageia 6, I experienced the same problem. import QtQuick.Enterprise.VirtualKeyboard 2.0 `export $(dbus-launch)` GitHub is where people build software. I’m opening the terminal from an arduino workspace /imported project. Close. Setting the name of 0x1345780 to “org.kde.ActivityManager.Resources.Scoring” I'm not sure when it happened, but I just found out while trying to restart kwin, and I figured it might help someone else. kwin_core: The used windowing system requires compositing Workaround #1: After that clicking in any pop-up menu from main menu makes that it is shown at the position/height of title bar (not main menu as I expected).