Confirming here that this bug is still present as of today. Curiously, logging in as a different user on the same system makes it possible to start eog. Unfortunately, that isnt quite an acceptable workaround.
Running eog under strace gives the following output:
Confirming here that this bug is still present as of today. Curiously, logging in as a different user on the same system makes it possible to start eog. Unfortunately, that isnt quite an acceptable workaround.
Running eog under strace gives the following output:
... GESTURE_ MANAGER (manager)' failed
fstat(20, {st_mode=0600, st_size=0, ...}) = 0
fcntl(20, F_GETFL) = 0x2 (flags O_RDWR)
write(2, "\n(eog:11840): GRIP-CRITICAL **: "..., 104
(eog:11840): GRIP-CRITICAL **: register_internal: assertion `GRIP_IS_
) = 104
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
( I can attach the full trace if desired)
It seems that some races were fixed in this release related to this bug: /bugs.launchpad .net/libgrip/ +bug/827958
https:/
But it seems that those fixes werent quite enough.