Hi
I've never seen those Gpu errors before.
I don't know why it's happening, but I know that version 4.0.0 (thanks
to the Qt6 port) will work better with Wayland.
If you don't want to wait for your distro to update the package, the
flatpak package v4.0.0 is now available:
https://flathub.org/apps/org.frescobaldi.Frescobaldi
Il giorno mar 1 apr 2025 alle 15:04:11 -04:00:00, Frederick Bartlett
<frederick.bartl...@gmail.com> ha scritto:
When I start Frescobaldi as a regular user, it immediately crashes
with
QSocketNotifier: Can only be used with threads started with QThread
[34939:34971:0401/141649.104015:ERROR:gl_context_egl.cc(259)]
eglCreateContext failed with error EGL_BAD_CONTEXT
[34939:34971:0401/141649.104060:ERROR:gpu_channel_manager.cc(753)]
ContextResult::kFatalFailure: Failed to create shared context for
virtualization.
[34939:34971:0401/141649.104066:ERROR:shared_image_stub.cc(470)]
SharedImageStub: unable to create context
[34939:34971:0401/141649.104087:ERROR:gpu_channel.cc(449)]
GpuChannel: Failed to create SharedImageStub
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
The middle four lines are repeated 15,447 times until:
[34939:34971:0401/141655.443424:ERROR:gpu_channel.cc(449)]
GpuChannel: Failed to create SharedImageStub
The Wayland connection experienced a fatal error: Protocol error
The Wayland connection experienced a fatal error: Protocol error
When I run Frescobaldi as root, it works – except that my Caslon
fonts are replaced with NotoSans, even after I added a symlink from
root to the user .fonts directory.
The midi interface works, and I can run lilypond separately to get a
good PDF. So my workflow is a little more convoluted than I would
like, but it all works.
Any idea what’s happening here?
Thanks!
Fred
