You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to use fontforge on Manjaro linux, with a KDE plasma session on Wayland.
Fontforge cannot be started.
Copyright (c) 2000-2023. See AUTHORS for Contributors.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
Version: 20230101
Based on sources from 2023-04-07 06:26 UTC-ML-D-GDK3.
(fontforge:37290): Gdk-WARNING **: 18:12:56.283: cannot open display:
The output above also reports the fontforge version.
Using an X11 Plasma session, fontforge starts normally. Unclear why it is not using XWayland on Wayland.
When reporting a bug/issue:
Screenshot
The FontForge version and the operating system you're using
The behavior you expect to see, and the actual behavior
[ X Steps to reproduce the behavior
(optional) Possible solution/fix/workaround
The text was updated successfully, but these errors were encountered:
Diagnosed: you need to unset GDK_BACKEND or set it to x11 for fontforge to work.
If fontforge cannot deal with GDK_BACKEND=wayland probably it should ignore it rather than breaking.
How do gimp or inkscape start at the same command prompt? I'm not sure whether applications or the window manager are in charge of GDK_BACKEND setting.
Gimp and inkscape start just fine with GDK_BACKEND set to wayland on my system. Xeyes suggests that gimp starts as an X11 application, while inkscape is wayland.
Trying to use fontforge on Manjaro linux, with a KDE plasma session on Wayland.
Fontforge cannot be started.
The output above also reports the fontforge version.
Using an X11 Plasma session, fontforge starts normally. Unclear why it is not using XWayland on Wayland.
When reporting a bug/issue:
The text was updated successfully, but these errors were encountered: