[Bug 131213] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2007-09-26 Thread Pedro Villavicencio
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

[Bug 131213] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2007-08-17 Thread Sebastien Bacher
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 Desktop Bugs, which is a bug assignee.

[Bug 131213] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2007-08-16 Thread Sebastien Bacher
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: Public

[Bug 131213] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2007-08-16 Thread Christer Edwards
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()