there has been no such issue reported in years, assuming it doesn't
exist in the current version of the code and closing
** Changed in: nautilus (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: nautilus
Status: New = Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/917744
Title:
nautilus crashed with SIGSEGV in
Sent upstream: https://bugzilla.gnome.org/show_bug.cgi?id=670070
** Bug watch added: GNOME Bug Tracker #670070
https://bugzilla.gnome.org/show_bug.cgi?id=670070
** Changed in: nautilus (Ubuntu)
Status: New = Confirmed
** Also affects: nautilus via
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/917744
Title:
nautilus crashed with SIGSEGV in
** Changed in: nautilus
Status: Unknown = New
** Changed in: nautilus
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/917744
Title:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/917744
Title:
nautilus crashed with SIGSEGV in g_thread_pool_set_max_idle_time()
To manage
