We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in:
I don't know what action triggered it. Since Nautilus will launch on
every window open, file action etc - if the stack trace from apport
isn't useful... Maybe a patch is needed to have Valgrind used on every
use of Nautilus?
--
nautilus crashed with SIGSEGV in free()
using valgrind slow things by a magnitude and would mean opening a menu
would take some 15 seconds it's not an option
--
nautilus crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/430393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Could you please confirm my understanding?
Apport with stack trace for a Nautilus crash is incomplete, so if it can
not be readily reproduced as required to use Valgrind, the bug is
incomplete rather than New - but there is nothing else the user can
gather?
If true, is marking it incomplete
the bug is let incomplete in case some user could provide useful
informations if that's not the case it will be closed because there is
not a lot of work which can be done using the one on the bug now
--
nautilus crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/430393
You received
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/430393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
