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 748108 - gtk apps don't start under weston
gtk apps don't start under weston
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-04-18 14:56 UTC by Matthias Clasen
Modified: 2015-10-02 10:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2015-04-18 14:56:52 UTC
weston 1.7.0, GTK+ master. I get

(lt-gtk3-widget-factory:27377): Gdk-ERROR **: wl_display@1: error 1: invalid arguments for xdg_shell@15.get_xdg_surface

on the client side, and

 libwayland: not a valid new object id (5), message get_xdg_surface(no)

on the weston side
Comment 1 Matthias Clasen 2015-04-18 14:58:35 UTC
things work fine under mutter
Comment 2 Carlos Garnacho 2015-04-18 16:43:46 UTC
AFAICT this is due to the xdg-shell v5 changes:
https://bugzilla.gnome.org/show_bug.cgi?id=744455

If I (hackishly) revert that patch, gtk3-demo gets to appear on weston, so I guess it comes down to waiting for weston to catch up, if a decision was done there yet.
Comment 3 Jonas Ådahl 2015-04-20 06:02:20 UTC
(In reply to Carlos Garnacho from comment #2)
> AFAICT this is due to the xdg-shell v5 changes:
> https://bugzilla.gnome.org/show_bug.cgi?id=744455
> 
> If I (hackishly) revert that patch, gtk3-demo gets to appear on weston, so I
> guess it comes down to waiting for weston to catch up, if a decision was
> done there yet.

The v5 changes are on weston master, so updating to that would also make GTK+ clients work again as well.
Comment 4 Matthias Clasen 2015-04-20 13:13:28 UTC
ah, thanks. I forget: would it be possible to make gtk+ work with both v4 and v5 compositors ? Or is that not feasible ?
Comment 5 Jonas Ådahl 2015-04-20 13:18:59 UTC
It'd probably be easier to support both xdg_shell and wl_shell in that case.
Comment 6 Daniel Stone 2015-04-20 13:19:24 UTC
(In reply to Matthias Clasen from comment #4)
> ah, thanks. I forget: would it be possible to make gtk+ work with both v4
> and v5 compositors ? Or is that not feasible ?

no - the way xdg_shell is designed, it is impossible to provide any kind of fallback handling. even the version negotiation mechanism is no longer workable between v4/v5 - which is why you get the cryptic mismatched-type error, rather than a more friendly error message.

this is a large part of the reason i really wanted to get the version changes nailed down ...
Comment 7 Matthias Clasen 2015-10-02 10:44:38 UTC
not a problem anymore