Gentleman, If your GNOME session *runs on Wayland* but your application * expects X11,
* you might need to **force X11**: GDK_BACKEND=x11 ./your_app * Or, if you're using Wayland: GDK_BACKEND=wayland ./your_app please take this into account when debugging gdk_display_open() was called before gtk_init() The incorrect setting could provoke this behaviour (trying to access the GTK display before GTK has been initialized.) Possible Values for GDK_BACKEND Value Description x11: Uses X11 as the windowing system. wayland: Uses Wayland as the windowing system. broadway: Runs GTK applications in a web browser using a built-in web server. quartz: Used on macOS (Cocoa-based windowing). win32: Used on Windows. headless: Runs without a display server (useful for testing and automation). There might be other environment variables too that provoke this behaviour. i.e. QT has QT_QPA_PLATFORM Common Values for QT_QPA_PLATFORM Backend: Value Description xcb: Default for X11-based Linux systems. wayland: Used for Wayland-based compositors. windows: Default for Windows systems. cocoa: Default for macOS. offscreen: Used for headless rendering without a visible GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095214 Title: xdg-desktop-portal-gnome crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2095214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
