The mutter update would definitely fix the problem described (app fails to launch another app), but I don't see how it could possibly be related to the ensureGigacage() backtrace. Anyway, that bug is closed now too... we can always revisit if it becomes a problem again.
(In reply to Michael Catanzaro from comment #15)
> ^ This remains the next step here. We need to know why the mmap() call is
> failing.
Jeremy discovered Deja Dup is setting a virtual memory limit in its desktop file:
Exec=sh -c "ulimit -v 1000000; exec @pkglibexecdir@ /deja-dup- monitor"
which is incompatible with Gigacage. It needs to not do that. This is NOTABUG. Good find, Jeremy!
(In reply to Tomas Popela from comment #21) /bugzilla. redhat. com/show_ bug.cgi? id=1554873# c6. Updating mutter
> Nevermind, see Jiri's response in
> https:/
> fixed the issue..
The mutter update would definitely fix the problem described (app fails to launch another app), but I don't see how it could possibly be related to the ensureGigacage() backtrace. Anyway, that bug is closed now too... we can always revisit if it becomes a problem again.