** Changed in: gvfs
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/325701
Title:
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
To manage
** Changed in: gvfs
Importance: Unknown = Critical
--
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
https://bugs.launchpad.net/bugs/325701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: gvfs
Status: Invalid = New
--
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
https://bugs.launchpad.net/bugs/325701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
there has been a new duplicate on bug #351936 using 1.2.0
** Changed in: gvfs (Ubuntu)
Status: Fix Released = Triaged
--
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
https://bugs.launchpad.net/bugs/325701
You received this bug notification because you are a member
** Changed in: gvfs
Status: Unknown = Invalid
--
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
https://bugs.launchpad.net/bugs/325701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can't remember exactly that day. I think I found the message when I
turned on the computer in the morning, so I had been logged in for at
least a day.
Assuming that apport can get confused as you say, it's quite plausible
that it did: Although I typically update at least once daily, I tend to
Thanks for your reply. I'm going to assume, then, that this is a
duplicate of #318661.
If you get any additional crashers please report them.
Cheers
** Changed in: gvfs (Ubuntu)
Status: Triaged = Fix Released
--
gvfsd-trash crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
Hi Bogdan
If you can remember: how long had you been logged in when the crash
occurred?
Although this is flagged as being a crasher in version 1.1.5, I am
suspicious of the accuracy of that information. Séb packaged 1.1.5 on
the 2nd and this bug is reported on the 5th. Even if you are very
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=570663
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New =
