*** This bug is a duplicate of bug 518891 ***
https://bugs.launchpad.net/bugs/518891
Trace looks exactly like the one in bug #518891.
** This bug has been marked a duplicate of bug 518891
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
--
nautilus crashed with SIGSEGV in
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Medium
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
OK, thanks!
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
The duplicates have already been stripped of private information, so
there's no need to do that
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Thanks Vish. I was asked by a user who wished to follow the bug to
switch it to public. Do you think it safer if I switch the duplicates to
private as well?
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notificatio
@lelamal , for future reference , if a crash report has been uploaded
you can wait until the re-tracers have gone thorough your report.
Usually CoreDump.gz _might_ contain personal information. [though i
havent checked the one uploaded here , let's just be safe :)]
--
nautilus crashed with SIGSE
Marking as private since the CoreDump.gz is still attached to the
report
** Visibility changed to: Private
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yeah, I know that. I do it everytime the upload fails - mostly when the
report exceeds 200 MB. But what does it have to do with what have been
discussed? If your reply refers to comment #3, then please allow me to
be clearer:
1. Crash
2. Apport: "Oops, let's upload a report to the developers?". Me
Crash reports are stored in /var/crash, if you don't report the bug on
Launchpad immediately you can still do so later by executing those files.
However, that will bring up the same dialogue you cancelled earlier and that
dialogue will create a new bug report.
--
nautilus crashed with SIGSEGV i
... continued from Bug #516219:
> lelamal: The point is that bug #422393 was an old bug that was already marked
> as Fix Released when you encountered the issue.
I have encountered fixed bugs that get confirmed and reopened, if users report
that the bug is reoccurring, without them being asked t
Please, also refer to the new Bug #516219
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/515495
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.ub
12 matches
Mail list logo
