scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libunity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred when I was uninstalling an Extension pack 4.2.16 from VirtualBox 4.2.18 running on saucy, using the GUI.
I had just purged Saucy 4.2.16 Ubuntu package and upgraded to 4.2.18 from virtualbox.org apt repositories for raring.
The 4.2.18 packages from official virtualbox repositories were built for raring (but meet saucy dependencies) and I had unity-scope-
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.1.0+13.
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 6 22:31:22 2013
Dependencies:
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7fd41c7048be: cmp %rbp,(%rax)
PC (0x7fd41c7048be) ok
source "%rbp" ok
destination "(%rax)" (0x900000001) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: scope-runner-
UpgradeStatus: Upgraded to saucy on 2013-09-03 (3 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse kismet libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vde2-net video
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 #1194465, 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.