Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.
As you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart. Once you have done this,
repeat the steps necessary to recreate the crash.
You may then get a crash report notification. If so, follow the on-
screen instructions to submit the crash report. If you don't get a
notification and you are using Ubuntu with the Gnome desktop environment
- launch a terminal and submit the crash report using /usr/share/apport
/apport-gtk --crash-file=/var/crash/_my_crash_report.crash. If you are
using Kubuntu or Xubuntu you can file the crash using /usr/share/apport
/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal
- where _my_crash_report.crash is the crash you would like to report.
Also bear in mind that you should only flag a bug as a security
vulnerability if you are reporting a specific security problem. You
aren't reporting a security problem, so you shouldn't have flagged this
bug as a security vulnerability.
I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
** This bug is no longer flagged as a security issue
** Tags removed: libgobject-2.0.so.0.1800.2 loop nautilus segfault
--
system bug: nautilus loops opening hundreds of new sessions on the system
tray...
https://bugs.launchpad.net/bugs/299635
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
