[Bug 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

2010-04-25 Thread Martin Mai
*** This bug is a duplicate of bug 518891 *** https://bugs.launchpad.net/bugs/518891 ** This bug is no longer a duplicate of bug 515495 nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() ** This bug has been marked a duplicate of bug 518891 nautilus crashed with SIGSEGV in

[Bug 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

2010-02-06 Thread Sense Hofstede
*** This bug is a duplicate of bug 515495 *** https://bugs.launchpad.net/bugs/515495 Thank you for taking the time to report this bug. However, it is a duplicate of bug #515495. Even though Sebastien requested you to report a new bug instead of reopening the old bug, you don't have to create

[Bug 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

2010-02-06 Thread lelamal
*** This bug is a duplicate of bug 515495 *** https://bugs.launchpad.net/bugs/515495 Thank you for taking the time to report this bug. You're welcome. However, it is a duplicate of bug #515495. And how would I know? If it was up to me to decide, I would have followed Apport, and

[Bug 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

2010-02-06 Thread Sense Hofstede
*** This bug is a duplicate of bug 515495 *** https://bugs.launchpad.net/bugs/515495 lelamal: The point is that bug #422393 was an old bug that was already marked as Fix Released when you encountered the issue. You were asked to open a new bug so Apport would upload all the log files and

[Bug 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

2010-02-02 Thread lelamal
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/38674260/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/38674261/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/38674262/Disassembly.txt ** Attachment