mtpfs assert failure: *** Error in `mtpfs': free(): invalid next size (fast): 0x00007fcffc0014b0 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mtpfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Error occurring when tried 'cd' to MTP devices (like Samsung Galaxy) mounted directory. This error happened repeatedly on different computers, different versions of mtpfs. Noticed on Ubuntu 64 bit version from Quantal to Saucy.
lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
apt-cache policy mtpfs
mtpfs:
Installed: 1.1-4.1
Candidate: 1.1-4.1
Version table:
*** 1.1-4.1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: mtpfs 1.1-4.1
ProcVersionSign
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AssertionMessage: *** Error in `mtpfs': free(): invalid next size (fast): 0x00007fcffc0014b0 ***
Date: Sun Nov 3 20:39:52 2013
ExecutablePath: /usr/bin/mtpfs
ExecutableTimes
InstallationDate: Installed on 2013-08-01 (93 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: mtpfs -o allow_other /media/
ProcCwd: /
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
SHELL=/bin/bash
Signal: 6
SourcePackage: mtpfs
StacktraceTop:
__libc_message (do_abort=
malloc_printerr (ptr=0x7fcffc00
_int_free (av=<optimised out>, p=0x7fcffc0014a0, have_lock=0) at malloc.c:3779
?? ()
?? ()
Title: mtpfs assert failure: *** Error in `mtpfs': free(): invalid next size (fast): 0x00007fcffc0014b0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: kismet
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 #1161620, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.