way).
But I’m using Frescobaldi natively under Wayland for quite some time now, and
there are no real problems.
You can of course force Frescobaldi to run under XWayland by setting
QT_QPA_PLATFORM=xcb. So as long as you’ve got XWayland running there should be
no problem with getting Frescobaldi
etNotifier: Can only be used with threads started with QThread
> qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
>
> Any possibility Frescobaldi will support Wayland in the short term?
>
> I'd offer to do it but it's way outside my knowledge areas.
>
> Andrew
>
>
>
>
>
t; Any possibility Frescobaldi will support Wayland in the short term?
>
> I'd offer to do it but it's way outside my knowledge areas.
>
> Andrew
I have a quite different issue, also using wayland, but it seems
unrelated, frescobaldi crashes with:
Traceback (most recent call last):
Lots of distros use Wayland now (like it or not). On Fedora 36 I get:
QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Any possibility Frescobaldi will support Wayland in the short term?
I'd offer to do
