<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi Chris, Adam and others,</p>
<p>I am not the technical person to answer details, but I am on the QGIS PSC and can assure you that building QGIS on Qt6 is high up on our priority list (for at least a year or even longer). You can already build QGIS fine on Qt6 (for at least 2-3 versions now) but the core devs came across some blockers that had to be solved first, before we can bring this to the end users without major regressions:</p>
<ol>
<li>isues around qt3d and webengine compatibility (one could either use 3D or the webengine, not both together)</li>
<li>issues around the fact that Qt webengine cannot output HTML/web output to vectors when rendering to PDF</li>
<li>PyQt6 bindings had to be done</li>
</ol>
<p>While the first issue is already solved, the 2nd issue is currently being solved by introducing another library (<a href="https://github.com/JakubMelka/PDF4QT">https://github.com/JakubMelka/PDF4QT</a>) and the third item is roughly 2/3 done and still actively being worked on.</p>
<p>Then there is the issue that all QGIS plugins have to be migrated to PyQt6 ...</p>
<p>We will probably offer QGIS Qt6 builds as technology previews soon in parallel to the normal Qt5 builds.</p>
<p>Now - about wayland: all of this has really nothing to do with Wayland but has to be done anyway, because Qt5 isn't developed any further and QGIS.ORG already invested in Qt6 improvements from which we cannot yet take advantage of until we ship with Qt6.</p>
<p>Moving QGIS to Qt6 doesn't automatically mean that all QGIS wayland issues are solved - but probably quite a few of these issues.</p>
<p>Hope this clarifies the situation? If you want more detailed, more technical responses, I recommend discussions on the QGIS developers mailing list. It would only bore regular QGIS users ...</p>
<p>Greetings,</p>
<p>Andreas<br />QGIS.ORG treasurer and PSC member</p>
<p><br /></p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div dir="ltr">
<div class="v1gmail_quote">
<div> </div>
<div>I don't know if you have recently run QGIS on a Wayland desktop, but there is a stern message strongly suggesting reverting to X.</div>
<div> </div>
<div>So as we seem to be marching away from X and ever forward to Wayland, I would like to start planning ahead a bit, and I would especially like to find some real information, as opposed to "I think this (but I really don't know)", or even worse, the people who can see a bright future for (let's say) Wayland-only desktops and aren't worried about the bumps on the road getting there.</div>
<div> </div>
<div>Fortunately it seems Ubuntu 24.04 will continue to support X <a href="https://discourse.ubuntu.com/t/ubuntu-desktop-24-04-lts-roadmap-highlights/41032" target="_blank" rel="noopener noreferrer">https://discourse.ubuntu.com/t/ubuntu-desktop-24-04-lts-roadmap-highlights/41032</a> so in my case at least I know I can drop back to X if / as necessary for the immediate future.</div>
<blockquote class="v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><br />> There is some stuff on GitHub but it seems to be at least a year or two<br />> old, talking about Qt6.0 and I gather we are at Qt6.6 by now. Plus endless<br />> short conversations in places like Reddit that throw off more heat than<br />> light.<br /><br />Updating to a new Qt version is likely going to be a lot of work, sot<br />imagine nobody is that keen on starting until there's really no choice.</blockquote>
<div> </div>
<div>As it happens, a search for qt6 in the QGIS repo on GitHub shows work being done on qt6, apparently for QGIS 4. So maybe someone has started already? I wonder how that's going?</div>
<blockquote class="v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><br />> Does anyone have any suggestions as to where to keep informed on this<br />> topic? Because it seems like Wayland is coming whether we want it or not...<br /><br />Wayland has been around for many years at this point, and is already the<br />default on some Linux distributions, which have no problem running<br />QGIS. There is so much legacy code that they are always going to have<br />compatibility modules to keep non-Wayland programs usable. I wouldn't<br />worry about any programs suddenly breaking due to Wayland.</blockquote>
<div> </div>
<div>While I appreciate your attempts to reassure me, this isn't helping.</div>
<div> </div>
<div>I'm aware from firsthand experience that Wayland has been around for many years at this point. I have even used it on and off. In fact it's my daily driver on my laptop.</div>
<div> </div>
<div>My concern is learning how QGIS development might converge - or not - with a Wayland-only future, since it seems several important Linux distros are leaning away from supporting X to some degree or another.</div>
<div> </div>
<div>As to whether QGIS might break under Wayland, there are 31 issues in the QGIS repo as of this evening related to Wayland in some form or the other. Plus the warning I mentioned above.</div>
</div>
<br /><span class="v1gmail_signature_prefix">-- </span><br />
<div class="v1gmail_signature" dir="ltr">
<div dir="ltr">Chris Hermansen · clhermansen "at" gmail "dot" com<br /><br />C'est ma façon de parler.</div>
</div>
</div>
</div>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br />QGIS-User mailing list<br /><a href="mailto:QGIS-User@lists.osgeo.org">QGIS-User@lists.osgeo.org</a><br />List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br />Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></div>
</blockquote>
<p><br /></p>
</body></html>