Hmm. I don't even know how nautilus is being run on login, much less how to start it up under valgrind. AFAICT, I don't see any reason that nautilus should even be trying to start up. It's not in my session script, I'm not using it to manage my desktop, etc...
Anyway, I'd be happy to try running nautilus under valgrind on login, if you can explain how I can do so. -- nautilus crashed on login with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/150072 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
