[Desktop-packages] [Bug 1278798] Re: nautilus crashed with SIGSEGV in gdk_property_change()

2014-03-17 Thread Sebastien Bacher
*** This bug is a duplicate of bug 979406 *** https://bugs.launchpad.net/bugs/979406 ** This bug has been marked a duplicate of private bug 979406 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launc

[Desktop-packages] [Bug 1278798] Re: nautilus crashed with SIGSEGV in gdk_property_change()

2014-03-15 Thread John Russell
** This bug is no longer a duplicate of private bug 979406 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1278798 Title: nautilus crashed with SIGSEGV in gdk_property_change() Statu

[Desktop-packages] [Bug 1278798] Re: nautilus crashed with SIGSEGV in gdk_property_change()

2014-03-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/12

[Desktop-packages] [Bug 1278798] Re: nautilus crashed with SIGSEGV in gdk_property_change()

2014-02-11 Thread LeadMan
*** This bug is a duplicate of bug 979406 *** https://bugs.launchpad.net/bugs/979406 Bug #979406 can't be found. Maybe it is private only? If so, how am I supposed to mark it as affecting me? Or others? -- You received this bug notification because you are a member of Desktop Packages, which

[Desktop-packages] [Bug 1278798] Re: nautilus crashed with SIGSEGV in gdk_property_change()

2014-02-11 Thread Apport retracing service
*** This bug is a duplicate of bug 979406 *** https://bugs.launchpad.net/bugs/979406 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #979406, so is being marked as such. Ple