Hi there!
Recently made the move to Wayland on my Ubuntu 22.04 machine. What didn’t work was Gramps. I’m using the 5.2.4 deb file. Under xorg it works as it should. Is there anything I need to do to launch the app? The only output is ‘Segmentation fault’ if I start Gramps in terminal. A blank window pops up a second and then crashes. Hope you can help!
Sorry I ran Gramps with GDK_BACKEND=x11 then it worked. Gramps should run automatically with xorg (xWayland) if I run Wayland?
1 Like
Ok it works now but from what I understand Gramps should also work with Wayland. Is there something I missed here? Or is it best to use xorg for Gramps?
This has nothing to do with gramps.
This is a problem between Gtk3 and Wayland
Okay, then I’ll continue running Gramps in xorg (under Wayland). Which is the only thing that works in Ubuntu 22.04.
I run Gramps 5.2.3 on Fedora 41. It is running an Intel display
adapter, KDE and Wayland. No problems, it works
1 Like
Stock Ubuntu 22.04, Ubuntu default session (Gnome Wayland), AMD Radeon card. Gramps crashes immediately.
As an interesting coincidence - I recently had a problem very similar to
this with another set of software that I use. Besides genealogy, I am
also very much a caver. Mapping caves is a favorite activity.
The software I use to create cave maps is called Therion. One of the
utilities included in the Therion collection is called loch. Loch is a
viewer for a certain kind of 3D representation of a cave.
When running Wayland, Loch would throw a segmentation fault within 1 or
2 seconds of launch. There was some discussion around the Therion email
support list about this. In the end a solution and a work-around were
provided. The work-around is to add GDK_BACKEND=x11 to the command line
when launching Gramps. Pär reports below that this works.
The solution for loch is some patches to the C++ code and so would be
difficult to apply to Gramps. Essentially it adds a condition test to
the startup procedures which detects Wayland (more exactly - the lack of
EGL) and then forces a connection to X11. A simple patch of about 10
lines of C++. Could something similar be done in Python?
I wonder, though, why Gramps works for me without this work-around and
does not work for Pär. Maybe the Fedora packager worked some magic??
Good explanation! Tonight I’m going to try starting Gramps with GDK_BACKEND=wayland because the crash might come when Gramps tries to choose the backend. It might work if there is only one backend installed eg xorg or wayland.
No it doesn’t work with GDK_BACKEND=wayland either. But that was to be expected as Gramps works if I run Ubuntu with the xorg session. Although what you, Bill told about “Loch” is somehow similar to this. The difference is that Gramps works in Wayland under Fedora as you said but not Ubuntu.
I don’t think it has anything to do with the packager either because I had a working installation from source code before and it was the same.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.