After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 723474 - GTK+ applications crash on Wayland servers/shells that do not have XDG_SHELL
GTK+ applications crash on Wayland servers/shells that do not have XDG_SHELL
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-02-02 13:35 UTC by bluescreen_avenger
Modified: 2016-05-03 23:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
bt full of the zenity --info crash running on a non XDG_SHELL server (10.41 KB, text/plain)
2014-02-02 13:36 UTC, bluescreen_avenger 		Details

Description bluescreen_avenger 2014-02-02 13:35:46 UTC 
I am running gtk applications on Orbital
https://github.com/giucam/orbital
but I guess it can be replicated by using an older version of Weston that doesn't support XDG_SHELL as well.

All applications segfault. If I have a WAYLAND_DISPLAY as wayland-orbital with Orbital as the shell (with no current XDG_SHELL support), and I have another WAYLAND_DISPLAY, wayland-weston which is a weston master, and I have a terminal with all the Wayland variable.

If in this terminal, I then run export WAYLAND_DISPLAY=wayland-weston, and run zenity --info it runs. If I press CTRL+C, and then I run export WAYLAND_DISPLAY=wayland-orbital, and try to run zenity --info, it segfaults.


Attached is a bt full of the crash
Comment 1 bluescreen_avenger 2014-02-02 13:36:30 UTC 
Created attachment 267847 [details]
bt full of the zenity --info crash running on a non XDG_SHELL server
Comment 2 Matthias Clasen 2014-02-03 15:17:07 UTC 
We should avoid segfaulting, if at all possible, and instead exit cleanly with an error message. But as far as 'working GTK+ applications', I think the answer will have to be: please implement xdg-shell.
Comment 3 Olivier Fourdan 2016-05-03 15:24:41 UTC 
Dupe of bug 762258 ? 

Now (with gtk+ 3.20), if xdg-shell isn;t available, we don't use the wayland backend and fallback to X11 (and thus Xwayland, on Wayland).

Can we close thus bug?
Comment 4 Matthias Clasen 2016-05-03 23:54:10 UTC 
sounds like it