nvidia-settings crashed with SIGSEGV in __GI___libc_malloc()

Bug #1427247 reported by Cavsfan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Received this error while getting updates.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nvidia-settings 346.35-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Mar 2 10:05:06 2015
ExecutablePath: /usr/bin/nvidia-settings
InstallationDate: Installed on 2015-01-24 (36 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150124)
ProcCmdline: nvidia-settings -q GPUCoreTemp
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f92806b2f70 <__GI___libc_malloc+64>: lock cmpxchg %esi,(%rbx)
 PC (0x7f92806b2f70) ok
 source "%esi" ok
 destination "(%rbx)" (0x7e90a7007e90a618) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 __GI___libc_malloc (bytes=176) at malloc.c:2887
 ?? () from /usr/lib/nvidia-340/libGL.so.1
 ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.76
 ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.76
 ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.76
Title: nvidia-settings crashed with SIGSEGV in __GI___libc_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Cavsfan (cavsfan) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___libc_malloc (bytes=176) at malloc.c:2887
 ?? () from /tmp/apport_sandbox_TIqat4/usr/lib/nvidia-340/libGL.so.1
 ?? () from /tmp/apport_sandbox_TIqat4/usr/lib/nvidia-340/libnvidia-glcore.so.340.76
 ?? () from /tmp/apport_sandbox_TIqat4/usr/lib/nvidia-340/libnvidia-glcore.so.340.76
 ?? () from /tmp/apport_sandbox_TIqat4/usr/lib/nvidia-340/libnvidia-glcore.so.340.76

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for nvidia-340
no debug symbol package found for nvidia-settings
no debug symbol package found for nvidia-settings

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.