Closing this bug for now, feel free to re open it if you can reproduce
it with latest Gutsy. thanks.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
nautilus crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/131213
You received this bug notification
Does it happen if you use gnome-session-remove nautilus and then it from
a command line or not?
--
nautilus crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/131213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
I'll give it a try but the Valgrind instructions aren't entirely clear
to me. Primarily step 3. Also, this crash happened at login so I may
need some suggestions on getting it in place for future crash-on-login.
--
nautilus crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs
Thanks for your bug report. Could you try to get a valgrind log for the
crash (you can follow the instructions on
https://wiki.ubuntu.com/Valgrind)?
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: New => Incomplete
** Visibility changed to: Publi