https://bugzilla.gnome.org/show_bug.cgi?id=766341
--- Comment #11 from Ray Strode [halfline] <[email protected]> ---
we may have to check for EPERM in addition to ENOSYS. see this, oddly
coincidental, irc log from this morning:
[07:15:26] <memeka> i fail to run GTK3 apps under wayland - it crashes with
"creating shared memory file failed: Operation not permitted"
[07:16:37] <memeka> it crashes in create_shm_pool in gdkdisplay-wayland.c
[07:26:40] <halfline> memeka: what's the output of 'uname -a' ?
[07:27:11] <memeka> kernel 3.10.96, armv7l
[07:27:37] <halfline> memeka: and the version of gtk3 ?
[07:27:52] <memeka> i'm running debian, only created a root user
[07:27:55] <memeka> gtk3.20
[07:28:19] <pq> halfline, shouldn't that cause something like ENOSYS rather
than EPERM?
[07:28:46] <halfline> memeka: sounds like you're hitting
https://bugzilla.gnome.org/show_bug.cgi?id=766341
[07:28:49] <halfline> pq: you'd think
[07:28:55] <pq> :-p
[07:29:14] <halfline> pq: but apparently not ...his kernel is too old for
memfd_create
[07:29:18] <halfline> and he's getting EPERM
[07:29:41] <pq> right, that confused me
[07:32:18] <halfline> pq: i wonder if __NR_memfd_create maps to a different
syscall
[07:32:35] <halfline> pq: (say it's accidentally getting the x86 number or
something)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
