search

raspberrypi / maynard

Desktop environment for Wayland
Other
337 stars 46 forks source link

Maynard needs xdg_shell version 3, latest Weston is at version 4 #25

Closed DragoonAethis closed 10 years ago

DragoonAethis commented 10 years ago

While compiling Wayland, Weston, libinput and Maynard from git on Arch, everything builds and installs fine. However, Maynard fails to start, complaining about: (maynard:26925): Gdk-ERROR **: xdg-shell@15: error 0: incompatible version, server is 4 client wants 3 - probably has to do with this, that is, xdg-shell version bump.

With stable Wayland/Weston installed (from extra/community repos, both at 1.5.0), Maynard doesn't build at all, requires newer Weston, but from before the bump. Also, it looks like they want to go for stable 1.6.0 in a couple of weeks with another xdg-shell version bump in the meantime.

barisione commented 10 years ago

Maynard compiles agains a specific version of Weston with some patches we wrote and that are not completely upstreamed yet. See https://github.com/raspberrypi/maynard/wiki/Develop-on-a-computer

jonnylamb commented 10 years ago

The reason this is failing is actually because your version GTK+ is too old. You are indeed right in thinking that the xdg-shell version was recently bumped and thanks to the way the xdg-shell & GTK+ transition is being handled, you have to either downgrade your weston, or upgrade your GTK+.

The weston patches that were required before to get maynard working have now been pushed to weston and were recently released in the 1.6 rc.

Therefore, this isn't a maynard bug. You need to get your GTK+ and weston in sync with each other (which is a problem everyone has nowadays), taking into account that if you go for a weston too old you need to apply the weston patches I wrote, and if you go for a weston too new you need to use a newer GTK+.

jonnylamb commented 10 years ago

Given it looks as if you're building your own weston, the easiest solution would probably be to downgrade weston to 42ebdda4. If you don't want to change that, you need to build GTK+ from at least cd173a1b.

DragoonAethis commented 10 years ago

Went ahead and compiled GTK+ from Git, this problem is gone... but now it crashes a bit later on, with "Gdk-ERROR **: Error flushing display: Broken pipe". Mayyyybe I'll wait for stable GTK+ 3.14 and Weston 1.6.0.