running wayland outside X

[Üstün Ergenoglu]

Hi,

2010/12/28 Zan Dobersek <zandobersek at gmail.com>:
> Set WAYLAND_DEBUG env variable, it helps a lot. You will probably see which
> object is non-existent.
thanks.

before the client aborts, I see these on wayland's output:
-> display at 1.range(1280)
-> display at 1.global(new id 1, "display", 1)
-> display at 1.global(new id 2, "drm", 1)
-> display at 1.global(new id 3, "compositor", 1)
-> display at 1.global(new id 4, "visual", 1)
-> display at 1.global(new id 5, "visual", 1)
-> display at 1.global(new id 6, "visual", 1)
-> display at 1.global(new id 7, "shm", 1)
-> display at 1.global(new id 8, "shell", 1)
-> display at 1.global(new id 9, "screenshooter", 1)
-> display at 1.global(new id 10, "output", 1)
-> display at 1.global(new id 11, "output", 1)
-> display at 1.global(new id 12, "input_device", 1)
-> drm at 2.device("/dev/dri/card0")
-> output at 10.geometry(0, 0, 1600, 1200)
-> output at 11.geometry(0, 0, 1280, 1024)
drm at 2.authenticate(113)
-> display at 1.invalid_object(0)
disconnect from client 0x8849158


anyone with a clue?

-üstün