python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()

[Craig Stein]

Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up.

apt-cache policy python
python:
  Installed: 2.7.14-2ubuntu1
  Candidate: 2.7.14-2ubuntu1
  Version table:
 *** 2.7.14-2ubuntu1 500
        500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: python2.7-minimal 2.7.14-2ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 06:15:41 2017
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2017-10-17 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
ProcCmdline: python accountable2you.pyc --username
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f84d920daa9 <ffi_closure_unix64_inner+105>: movzwl 0xa(%rdi),%r15d
 PC (0x7f84d920daa9) ok
 source "0xa(%rdi)" (0x640000007d) not located in a known VMA region (needed readable region)!
 destination "%r15d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ffi_closure_unix64_inner (closure=0x7f84db002128, rvalue=0x7f84cc4f58c0, reg_args=0x7f84cc4f5810, argp=0x7f84cc4f58e0 "\360XO\314\204\177") at ../src/x86/ffi64.c:585
 ffi_closure_unix64 () at ../src/x86/unix64.S:229
 IceFlush (iceConn=0x55c128968320) at ../../src/misc.c:78
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=0x7f84cc4f5a10) at ../src/x86/ffi64.c:525

[Craig Stein (whitebunnyflock)]

I should also mention that this happened after i added the following kernel command line:
GRUB_CMDLINE_LINUX="modprobe.blacklist=radeon radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1"

[Craig Stein (whitebunnyflock)]

i wiped my system and loaded production ubuntu 17.10 and the same error still exists there.

[Matthias Klose (doko)]

it's more likely that this happens in some extension module. Please could you tell what command you were running?

[Craig Stein (whitebunnyflock)]

it possible that this happened after installing the Sensors extension in Gnome, the extension does not work.

[Matthias Klose (doko)]

is this a packaged extension?

[Craig Stein (whitebunnyflock)]

It is on the GNOME software/extension center so I assume that is a yes

On Nov 27, 2017 11:50 PM, "Matthias Klose" <email address hidden> wrote:

> is this a packaged extension?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724233
>
> Title:
> python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
>
> Status in python2.7 package in Ubuntu:
> Incomplete
>
> Bug description:
> Booted into stock Ubuntu 17.10 release candidate from October 15, 2017
> and this error message simply came up.
>
> apt-cache policy python
> python:
> Installed: 2.7.14-2ubuntu1
> Candidate: 2.7.14-2ubuntu1
> Version table:
> *** 2.7.14-2ubuntu1 500
> 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: python2.7-minimal 2.7.14-2ubuntu2
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Oct 17 06:15:41 2017
> ExecutablePath: /usr/bin/python2.7
> InstallationDate: Installed on 2017-10-17 (0 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
> ProcCmdline: python accountable2you.pyc --username
> ProcEnviron:
> LANGUAGE=en_CA:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> 3.6.3-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> 2.7.14-2ubuntu1
> SegvAnalysis:
> Segfault happened at: 0x7f84d920daa9 <ffi_closure_unix64_inner+105>:
> movzwl 0xa(%rdi),%r15d
> PC (0x7f84d920daa9) ok
> source "0xa(%rdi)" (0x640000007d) not located in a known VMA region
> (needed readable region)!
> destination "%r15d" ok
> Stack memory exhausted (SP below stack segment)
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: python2.7
> StacktraceTop:
> ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
> ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
> IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6
> ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
> ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
> Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/
> 1724233/+subscriptions
>

[Craig Stein (whitebunnyflock)]

looking through the original documentation above could this be due to the accountable2you program? I guess what i could do is turn off all my extensions and attempt to find which one is bringing up the error?

[Launchpad Janitor (janitor)]

[Expired for python2.7 (Ubuntu) because there has been no activity for 60 days.]