Sorry for that double post.
It was already solved by Emmanuel.
Fre;D
De : wayland-devel de la part de
Fred vS
Envoyé : mercredi 4 octobre 2023 20:14
À : wayland-devel@lists.freedesktop.org
Objet : Problem with mmap keyboard.
Hello.
I try to make work the
Hello.
I try to make work the "Keyboard event" step from the Wayland-book but the C
demo crash at loading.
The problem comes from the mapping: with that error:
Line 301: wl_keyboard_keymap: Assertion map_shm != MAP_FAILED' failed.
Here is the function:
static void
wl_keyboard_keymap(void
Hello!
>“From version 7 onwards, the fd must be mapped with MAP_PRIVATE by the
recipient, as MAP_SHARED may fail.”
Yep, it does the trick, well seen, now all the infos of the keyboard are
working.
>I don’t know which wl_shell version you are using,
Huh, I did copy the source from:
Ho, many thanks Emmanuel.
I will deeply study your mail.
By the way, I am busy to translate all the "steps" demos of the Wayland-book
into Pascal:
https://github.com/fredvs/wayland-pascal
Now, Free Pascal compiler can create nice and working "Pure Wayland
applications".
Note too that the C
On Wed, Oct 04, 2023 at 06:19:30PM +, Fred vS wrote:
> Hello.
Hi,
>
>
> I try to make work the "Keyboard event" step from the Wayland-book but the C
> demo crash at loading.
>
> The problem comes from the mapping: with that error:
>
>
> Line 301: wl_keyboard_keymap: Assertion map_shm
Hello.
I try to make work the "Keyboard event" step from the Wayland-book but the C
demo crash at loading.
The problem comes from the mapping: with that error:
Line 301: wl_keyboard_keymap: Assertion map_shm != MAP_FAILED' failed.
Here is the function:
static void
wl_keyboard_keymap(void
On Wed, 4 Oct 2023 11:26:02 +0300
Pekka Paalanen wrote:
> ...
> For the forked clients, there is stop_display()/display_resume().
> Maybe that helps?
Maybe if I understand their usage correctly. Is this right?: A client
would send a sequence of requests followed by a stop_display request.
On Tue, 3 Oct 2023 14:46:14 -0400
jleivent wrote:
> I am trying to write some tests that provoke errors in libwayland, but
> it doesn't seem to me like the existing test suite provides a mechanism
> to create specific event orderings that are allowed but not guaranteed
> by the asynchrony of the
