scope-runner-dbus.py crashed with SIGSEGV in g_object_ref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libunity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
just upgraded to 13.10
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.0.9+13.
ProcVersionSign
Uname: Linux 3.8.0-27-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Sun Jul 28 09:52:07 2013
Dependencies:
ExecutablePath: /usr/share/
InstallationDate: Installed on 2013-07-05 (23 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
SegvAnalysis:
Segfault happened at: 0xb6fd20e8 <g_object_ref+24>: mov (%esi),%eax
PC (0xb6fd20e8) 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/
?? () from /usr/lib/
unity_
?? () from /usr/lib/
unity_
Title: scope-runner-
UpgradeStatus: Upgraded to saucy on 2013-07-28 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.