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

2014-02-08 Thread Andrew M Tapp
I don't know about the other guys, but the bug happened to me while copying files from one location to another. I've since reattempted the copy while waiting for the bug data to upload and it went smoothly. So I don't know if I can reproduce the bug for a valgrind log. Is there a way to set up a ru

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

2007-08-23 Thread Sebastien Bacher
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. ** Changed in: nautilus (Ubuntu)

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

2007-08-06 Thread Sebastien Bacher
Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)? -- nautilus crashed with SIGSEGV in g_slice_alloc()" https://bugs.launchpad.net/bugs/128142 You received this bug notification because you are a member of Ubuntu Bugs, which is

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

2007-08-06 Thread Pedro Villavicencio
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Impo