as I plug in the i-phone, the mistake appears.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gvfs-backends 1.20.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
Uname: Linux 3.16.0-16-generic i686
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
AssertionMessage: gvfs-afc-volume-monitor: plist.c:194: plist_copy_node: Zusicherung »data« nicht erfüllt.
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Sep 20 17:03:59 2014
ExecutablePath: /usr/lib/gvfs/gvfs-afc-volume-monitor
InstallationDate: Installed on 2013-06-09 (468 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
ProcCmdline: /usr/lib/gvfs/gvfs-afc-volume-monitor
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
LANGUAGE=de_DE
PATH=(custom, no user)
LANG=de_DE.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
__assert_fail_base (fmt=0xb58b1fea <error: Cannot access memory at address 0xb58b1fea>, assertion=assertion@entry=0xb7779aa1 "data", file=file@entry=0xb7779ac9 "plist.c", line=line@entry=194, function=function@entry=0xb7779dcb "plist_copy_node") at assert.c:92
__GI___assert_fail (assertion=0xb7779aa1 "data", file=0xb7779ac9 "plist.c", line=194, function=0xb7779dcb "plist_copy_node") at assert.c:101
?? () from /usr/lib/i386-linux-gnu/libplist.so.2
plist_copy () from /usr/lib/i386-linux-gnu/libplist.so.2
?? () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
Title: gvfs-afc-volume-monitor assert failure: gvfs-afc-volume-monitor: plist.c:194: plist_copy_node: Zusicherung »data« nicht erfüllt.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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 #1361011, 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.