nvidia-settings crashed with SIGSEGV in call_init()

Bug #1723388 reported by Gabriele Tramonte
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
New
Medium
Unassigned

Bug Description

Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
nvidia-settings:
  Installato: 384.69-0ubuntu1
  Candidato: 384.69-0ubuntu1
  Tabella versione:
 *** 384.69-0ubuntu1 500
        500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nvidia-settings 384.69-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 13 12:19:17 2017
Disassembly: => 0x11e0: Cannot access memory at address 0x11e0
ExecutablePath: /usr/bin/nvidia-settings
InstallationDate: Installed on 2017-07-20 (84 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
ProcCmdline: /usr/bin/nvidia-settings -q gpucoretemp -t
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x11e0: Cannot access memory at address 0x11e0
 PC (0x000011e0) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 ?? ()
 call_init (l=<optimized out>, argc=argc@entry=4, argv=argv@entry=0x7ffcda862a28, env=env@entry=0x7ffcda862a50) at dl-init.c:72
 call_init (env=0x7ffcda862a50, argv=0x7ffcda862a28, argc=4, l=<optimized out>) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x563e4b1b03f0, argc=4, argv=0x7ffcda862a28, env=0x7ffcda862a50) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffcda862570) at dl-open.c:575
Title: nvidia-settings crashed with SIGSEGV in call_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Gabriele Tramonte (pspgt) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 call_init (l=<optimized out>, argc=argc@entry=4, argv=argv@entry=0x7ffcda862a28, env=env@entry=0x7ffcda862a50) at dl-init.c:72
 call_init (env=0x7ffcda862a50, argv=0x7ffcda862a28, argc=4, l=<optimized out>) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x563e4b1b03f0, argc=4, argv=0x7ffcda862a28, env=0x7ffcda862a50) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffcda862570) at dl-open.c:575

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nvidia-settings (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.