valgrind log obtained by running:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gksu nautilus
Although, it might just be getting info on gksu, not what we really want to look at... Dropping to to root and running just Nautilus doesn't seem to reproduce the crash though...
Probably related:
Bug #420841 Bug #419565 Bug #419092
valgrind log obtained by running:
G_SLICE= always- malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file= valgrind. log gksu nautilus
Although, it might just be getting info on gksu, not what we really want to look at... Dropping to to root and running just Nautilus doesn't seem to reproduce the crash though...
Probably related:
Bug #420841
Bug #419565
Bug #419092