gvfs-afc-volume-monitor assert failure: gvfs-afc-volume-monitor: plist.c:194: plist_copy_node: assertion `data' 실패.

[Seong-ho Cho]

xfce's desktop icon doesn't shown

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gvfs-backends 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
AssertionMessage: gvfs-afc-volume-monitor: plist.c:194: plist_copy_node: assertion `data' 실패.
CrashCounter: 1
Date: Wed Aug 6 19:13:43 2014
ExecutablePath: /usr/lib/gvfs/gvfs-afc-volume-monitor
InstallationDate: Installed on 2014-04-14 (114 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
ProcCmdline: /usr/lib/gvfs/gvfs-afc-volume-monitor
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=ko_KR
 PATH=(custom, no user)
 LANG=ko_KR.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __assert_fail_base (fmt=0x7f351182dbd1 <error: Cannot access memory at address 0x7f351182dbd1>, assertion=assertion@entry=0x7f3511240721 "data", file=file@entry=0x7f3511240748 "plist.c", line=line@entry=194, function=function@entry=0x7f3511240ad0 "plist_copy_node") at assert.c:92
 __GI___assert_fail (assertion=0x7f3511240721 "data", file=0x7f3511240748 "plist.c", line=194, function=0x7f3511240ad0 "plist_copy_node") at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
Title: gvfs-afc-volume-monitor assert failure: gvfs-afc-volume-monitor: plist.c:194: plist_copy_node: assertion `data' 실패.
UpgradeStatus: Upgraded to utopic on 2014-04-21 (107 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1352154, 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.