nautilus crashed with SIGABRT in raise()

[nofallyaqoo]

Hello...

i add PPA for lightspark which is flash player for web browser, and then i did sudo apt-get update and then i did sudo apt-get install lightspark browser-plugin-lightspark.

and after all this i rebooted my system (i usually dont restart computer for just installing software/application but this time restart it because i noticed my computer become very very slow)
after i restart my computer and logged in bug reporter Immediately opened up and send me here.
IN SHORT WORDS... THIS BUG SOME HOW RELATED TO LIGHTSPARK, or maybe not !!

PLEASE CHECK LINK DOWN:
http://www.noobslab.com/2012/06/install-lightspark-0601-flash-in.html

OS: ubuntu 13.04
SYSTEM STATUS/STATE: FULLY UPDATED & UPGRADED
BIT: 32bit
WEB BROWSER: firefox 19.0
KERNELS: 3.8.0-9-generic

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Mar 2 23:21:59 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+0+24'"
InstallationDate: Installed on 2013-02-18 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130216)
MarkForUpload: True
ProcCmdline: nautilus -n
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #905686, 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.