Hi, 2010/12/28 Zan Dobersek <[email protected]>: > 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: -> [email protected](1280) -> [email protected](new id 1, "display", 1) -> [email protected](new id 2, "drm", 1) -> [email protected](new id 3, "compositor", 1) -> [email protected](new id 4, "visual", 1) -> [email protected](new id 5, "visual", 1) -> [email protected](new id 6, "visual", 1) -> [email protected](new id 7, "shm", 1) -> [email protected](new id 8, "shell", 1) -> [email protected](new id 9, "screenshooter", 1) -> [email protected](new id 10, "output", 1) -> [email protected](new id 11, "output", 1) -> [email protected](new id 12, "input_device", 1) -> [email protected]("/dev/dri/card0") -> [email protected](0, 0, 1600, 1200) -> [email protected](0, 0, 1280, 1024) [email protected](113) -> [email protected]_object(0) disconnect from client 0x8849158 anyone with a clue? -üstün _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
