[Wayland-bugs] [Bug 90562] failed to create display when use "weston --backend=wayland-backend.so"
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu May 21 22:52:48 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90562
Pekka Paalanen <ppaalanen at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Pekka Paalanen <ppaalanen at gmail.com> ---
Weston's Wayland-backend is meant for running Weston under another Wayland
compositor, yes. Just like the DRM backend is for running Weston on DRM/KMS,
the fbdev backend is for running Weston on /dev/fb, and the X11 backend is for
running Weston under an X server.
(In reply to Mark Yao from comment #2)
> I test run weston --backend=x11-backend.so,success
> then open weston desktop shell:
> int the desktop shell: run weston --backend=wayland-backend.so,
> success display but get this Error: libwayland: unable to lock lockfile
> /run/user/0/wayland-0.lock, maybe another compositor is running
> Is it right?
This is because Weston 1.6.0 IIRC did not yet automatically search for a free
socket name. You can work around that by specifying --socket with an unused
name on the command line. Weston 1.7.0 should find a free socket name
automatically.
> BTW, if I didn't use weston, like glmark2-es2-wayland or gtk3-demo with
> wayland,
> I should run weston first? or there is another way to run an existing
> Wayland compositor.
You can run whatever compositor you want. Weston is just one of them and not in
any way mandatory. GNOME has one, KDE has one, E has one, and there are more.
> My trying is just want to run a destop with wayland backend.
I can't see why? If it works, you already have a Wayland environment running,
and you don't need Weston with the wayland backend.
I think you are confusing some concepts here. The wayland backend is *not*
needed to get a Wayland environment running. A Wayland compositor provides a
Wayland environment for its clients in any case.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150522/1ab547f3/attachment.html>
More information about the wayland-bugs
mailing list