Summary: | gtk3-demo crashes run with wayland backend, wl_display invalid argument | ||
---|---|---|---|
Product: | Wayland | Reporter: | Mark Yao <mark.yao> |
Component: | wayland | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | jadahl, mark.yao |
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | run gtk3-demo with WAYLAND_DEBUG=1 |
Description
Mark Yao
2015-05-22 07:33:08 UTC
You are reporting a crash in gtk3-demo, but this it the freedesktop.org bug tracker. Crashes in gtk3-demo should be reported it to bugs.gnome.org. Anyhow, the crash you are seeing is a version mismatch between the unstable xdg_shell of version 4 in weston 1.7, and the unstable xdg_shell of version 5 in gtk+ 3.17. If you upgrade to the latest RC (released a few days ago) of wayland/weston they will have the same version, or downgrade gtk to some earlier version that shipped with xdg_shell unstable version 4. (In reply to Jonas Ådahl from comment #1) > You are reporting a crash in gtk3-demo, but this it the freedesktop.org bug > tracker. Crashes in gtk3-demo should be reported it to bugs.gnome.org. > > Anyhow, the crash you are seeing is a version mismatch between the unstable > xdg_shell of version 4 in weston 1.7, and the unstable xdg_shell of version > 5 in gtk+ 3.17. If you upgrade to the latest RC (released a few days ago) of > wayland/weston they will have the same version, or downgrade gtk to some > earlier version that shipped with xdg_shell unstable version 4. Sorry for bad place to report the bug. I'm new to the wayland, is there a tag or branch to point which version is stable? I compile the gtk/weston/wayland on arm board, very slow for compiling, Hope get less compile to success show a wayland display. (In reply to Mark Yao from comment #2) > (In reply to Jonas Ådahl from comment #1) > > You are reporting a crash in gtk3-demo, but this it the freedesktop.org bug > > tracker. Crashes in gtk3-demo should be reported it to bugs.gnome.org. > > > > Anyhow, the crash you are seeing is a version mismatch between the unstable > > xdg_shell of version 4 in weston 1.7, and the unstable xdg_shell of version > > 5 in gtk+ 3.17. If you upgrade to the latest RC (released a few days ago) of > > wayland/weston they will have the same version, or downgrade gtk to some > > earlier version that shipped with xdg_shell unstable version 4. > > Sorry for bad place to report the bug. Thats alright. Thanks for the report, even though it being in the wrong place :) > > I'm new to the wayland, is there a tag or branch to point which version is > stable? I compile the gtk/weston/wayland on arm board, very slow for > compiling, Hope get less compile to success show a wayland display. Just in a some days there will be a new stable release of wayland and weston. This will be compatible with both gtk+ 3.17 and the current master branch and gtk+ 3.16.*. If you don't want to wait, just grab the latest release candidate. You can find theme here: http://wayland.freedesktop.org/releases/ where the most recent ones are 1.7.92. I've downgrade the gtk+ to 3.16.3, but same error again. I found that there is a error at libwayland: "libwayland: not a valid new object id (5), message get_xdg_surface(no)." (In reply to Mark Yao from comment #4) > I've downgrade the gtk+ to 3.16.3, but same error again. That is not old enough. Looking at the git log, you need at least 3.15.6 or older. The easiest thing you can do is probably upgrading wayland/weston to the latest RC. (In reply to Jonas Ådahl from comment #5) > (In reply to Mark Yao from comment #4) > > I've downgrade the gtk+ to 3.16.3, but same error again. > > That is not old enough. Looking at the git log, you need at least 3.15.6 or > older. The easiest thing you can do is probably upgrading wayland/weston to > the latest RC. Thanks very much, gtk+-demo works. current version is that: gtk+(3.16.3) wayland(1.7.92) weston(1.7.92) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.