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 a bug assign
** Changed in: nautilus
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/475943
Title:
nautilus crashed with SIGSEGV in g_closure_invoke()
--
desktop-bugs mailing list
** Changed in: nautilus
Importance: Unknown => Critical
--
nautilus crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/475943
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
** Changed in: nautilus
Status: Unknown => New
--
nautilus crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/475943
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-b
I found that you can reproduce this by using file-roller to unpack
something. This will create a new folder into which the files will go
during uncompressing. Attempting to open the folder at a time when it is
still visible in nautilus but has been deleted by file-roller will
trigger the crash. It
