I stopped a copy of data to my Android SD card and the report a bug appeared,

[Irving Bunton Jr]

I connected a Samsang Galaxy S5. I successfully moved 1.2 Gb of pictures on the phone to the Ubuntu running on an SD card. I started copying the same files to the SD card. As this would take 3 hours, I stopped it after 1% was done. The Pac Man aborted. Expected it to stop without aborting.

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

 apt-cache policy pacman
pacman:
  Installed: (none)
  Candidate: 10-17ubuntu2
  Version table:
     10-17ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
j0hnbr0wn@IB-VAIO-VPCF132FX-2:~$

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: pcmanfm 1.2.0-1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1
Architecture: amd64
Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf'
CurrentDesktop: LXDE
Date: Tue Nov 11 08:36:01 2014
ExecutablePath: /usr/bin/pcmanfm
InstallationDate: Installed on 2014-10-01 (40 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: pcmanfm --desktop --profile lubuntu
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: pcmanfm
UpgradeStatus: Upgraded to trusty on 2014-10-01 (40 days ago)
UserGroups: adm cdrom dip lpadmin netdev 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 #1303092, 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.