I've just been redirected here by apport on my Ubuntu 17.10. So either
the duplicate detection logic is flawed or this is not fixed as
advertised by the bug's status.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
I should mention that when I say eject, I meant hitting the ⏏ icon in
Nautilus. I'm not yanking USB cables prematurely.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
I found this bug by looking at the DuplicateOf field in the Apport
dialog before I hit the 'Report' button. I can't say how reliable is
apport's backtrace matching, but I remember noticing something about
invalid free() in that report.
I then tried and managed to reproduce a crash on eject, and
There are many crash on eject bugs - the main issue is that the because
the USB device is gone libmtp is left in an unpredictable state, so it's
easy for things to blow up even as we try to exit as quickly as
possible. Did you see the exact same backtrace? It might also match one
of the other
Just saw this bug with gvfs 1.18.2-0ubuntu1. Same as original reporter:
crash on eject.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
gvfsd-mtp assert failure: ***
Assuming that the clean shutdown fix in 1.17.3 addressed this. Unplug
problems are unpredictable and hard to reproduce, so I want to clean the
slate and only look at reports from new releases with that possible fix.
** Changed in: gvfs (Ubuntu)
Status: New = Fix Released
** Changed in:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
gvfsd-mtp assert failure: *** Error in `/usr/lib/gvfs/gvfsd-mtp':
