When the system is low on memory, for example the web browser is eating
all of it and the laptop on laptop-mode has vm.swappiness=10, nautilus
will fail to carry out some actions.

Under memory pressure, nautilus won't for me:

Open a document
Archive -> Expand here

both actions fail without message or error, probably because of fork()
or similar fails on low memory. Killing the web browser helps.

Now nautilus uses a lot of memory after a time due to some leak, this is
probably why it can't fork.

The bug is mainly about nautilus' error handling: It should present an
error when it can't open a document by double-click etc etc, since when
it can't open files, it fails in one of its main uses.

Hey Ulrik,

this is an old bug.

Could you please still reproduce this issue with newer nautilus version
like 3.4.2-1+build1 or 3.8.2-3 ?

thanks
regards
althaser