When running natively in a Plasma 6 Wayland session, up-to-date Chromium-based browsers and Electron apps should now always use the correct mouse cursor theme and have the cursor drawn in the correct size, even when running in a Flatpak sandbox.

You can enable Chromium’s native Wayland support by setting chrome://flags/#ozone-platform-hint to “Auto” or with a command-line flag. There are multiple ways to apply this preference to Electron apps as well.

To check whether an app runs natively on Wayland or relies on the XWayland compatibility layer, you can look up kwin in any KRunner-enabled search bar (e.g. in the app launcher) and select “Open KWin debug console”.

Hope this helps! 😃

It was, of course, possible to workaround the issue by copying the missing files to their expected locations with a script or manually. For non-systemwide Qt installations, there was also an option of installing the libraries by side with Qt’s own modules. However, these are still platform-dependent workarounds we shouldn’t rely on long-term.

I faced this issue when trying to package Kaidan, a Qt Quick XMPP client, as an AppImage. After a discussion with linuxdeployqt’s contributors and some research, I found that internally the tool uses qmlimportscanner to locate the imported modules, but only passes QT_INSTALL_QML (Qt’s own modules location) to the scanner. It was clearly missing an option to list custom import paths, like -qmlimport. That was easy to fix, and so I did.

linuxdeployqt is a fork of macdeployqt, and so I decided it makes sense to upstream my changes. I made sure I’m not missing anything, then started a Gerrit revision.

While my changes were pending approval, I looked into windeployqt’s sources and submitted a matching revision to that tool.

When all three commits had been merged, I documented my changes.

Conclusion

Starting with Qt 5.13 there’ll be an option in Qt deployment tools ( -qmlimport) to specify custom import paths for Qt Quick libraries. As a nice bonus, this option also allows to choose between multiple versions of a library installed at different locations. For a more in-depth explanation of the change, please refer to this comment.

Contributing to Qt is not that difficult, and making even a small useful change feels so nice 🙂

If you hesitated to try Kirigami in your project because of deployment quirks, give it a go now! Join us on IRC or Matrix, take a look at the docs and have fun creating! 😃

I finally got a small break from the endless studies, so I decided to share my experience during C++ Russia 2018, an amazing C++ developer conference that I was lucky to attend as a volunteer.

The conference is a fun 3-day-long event hosted by the C++ Russia User Group, and an opportunity to listen to deep knowledge and practical wisdom of speakers from all over the world. This year’s keynote speaker was Jon Kalb, a C++ developer with 25-years of experience.

I managed to attend a number of talks, including:

• Interactive C++ Compilation (REPL): The Lean Way by Viktor Kirilov
• C++ No-Launch Code Debugging by Anastasia Kazakova
• Building in Docker with Conan by Evgeny Lukyanets
• Concept Based Testing by Dietmar Kühl
• CMake Pitfalls and Where to Find Them by Dmitry Kozhevnikov
• WebAssembly Transition: Is It Worth It? by Pavel Bulatov

I have also met many interesting people, some developers I previously messaged with, and made new friends 🙂

I would like to thank Sergey Platonov, the event manager, for this awesome experience.