libxfce4ui will potentially do Wayland-specific things if GDK_WINDOWING_WAYLAND is defined by Gdk, which happens if Gtk is built with the wayland USE flag. Despite this, it's missing a wayland USE flag of it's own (and the associated dependency on the wayland flag for Gtk). This means that the following sequence of events will produce a broken libxfce4ui (which will for example prevent launching Xfce):
1. Add wayland to your USE flags
2. Run "emerge --deep --verbose --newuse @world"
3. Install Xfce or any program that uses libxfce4ui
4. Remove wayland from your USE flags
5. Run "emerge --deep --verbose --newuse @world"
After that, libxfce4ui-2.so will still refer to the "gdk_wayland_display_get_type" symbol, which will no longer exists due to Gtk not having the wayland USE flag set anymore.
I don't see any configure option that would be relevant to this. This is an upstream bug then, isn't it?
There is no configure option, but it does check for the define that Gdk defines (GDK_WINDOWING_WAYLAND), which seems good enough to me in this case.
(In reply to Kacper Słomiński from comment #2)
> There is no configure option, but it does check for the define that Gdk
> defines (GDK_WINDOWING_WAYLAND), which seems good enough to me in this case.
I don't see how to use that to prevent the breakage if libxfce4ui[-wayland] is built against gtk+[wayland].
(In reply to Michał Górny from comment #3)
> I don't see how to use that to prevent the breakage if libxfce4ui[-wayland]
> is built against gtk+[wayland].
Hmm, good point. I was thinking of having libfxce4ui depend on gtk+ having the same state of the wayland USE flag. Also probably worth noting, the Wayland detection is only there to disable some functionality that's broken under Wayland:
if (GDK_IS_WAYLAND_DISPLAY (gdk_display_get_default ()))
if (startup_notify == TRUE)
/* 'sn_display_new' crashes when used via wayland, so no startup notification support here */
g_warning ("startup notification not supported for wayland sessions");
startup_notify = FALSE;
Sounds like they're working around some bug in startup-notification then. Any idea if this bug is still valid? I suppose it kinda sucks to add a dep on conditional symbols over something like this.
Not sure what do to about this. Looking at the source code for libsn, sn_display_new crashes because it unconditionally uses the given X11 display (and immediately goes to work querying atoms without checking if it's valid), so it's not easy to fix there probably, considering the whole lib looks pretty X11-specific.
Just for some further reading: there's all sorts of problems similar to this, unfortunately, see bug 624960 (although the XFCE issue here is actually something concrete instead of gcr etc)