scope-runner-dbus.py crashed with SIGSEGV in g_object_ref()

[Khairul Aizat Kamarudzzaman]

trigger when updating unity scope filters

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Sun Jul 28 00:28:57 2013
Dependencies:

ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InstallationDate: Installed on 2013-07-24 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130722)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope
SegvAnalysis:
 Segfault happened at: 0xb6f700e8 <g_object_ref+24>: mov (%esi),%eax
 PC (0xb6f700e8) ok
 source "(%esi)" (0x676f6f67) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 g_object_ref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9
 unity_scope_loader_export_scopes () from /usr/lib/i386-linux-gnu/libunity.so.9
 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9
 unity_scope_loader_load_scope () from /usr/lib/i386-linux-gnu/libunity.so.9
Title: scope-runner-dbus.py crashed with SIGSEGV in g_object_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot 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 #1201526, 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.