nvidia-settings crashed with SIGSEGV

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

Bug Description

Binary package hint: nvidia-settings

To store a new xorg.conf setup I run sudo nvidia-settings, and change from my laptop monitor to an external monitor. When I press "Save to xorg" it dumps:
VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
Undefined Device "(null)" referenced by Screen "Default Screen".

Segmentation fault (core dumped)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 19 10:05:20 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: nvidia
Package: nvidia-settings 180.25-0ubuntu1
ProcCmdline: nvidia-settings
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_DK.UTF-8
 LANGUAGE=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x46b9b8: mov 0x38(%rdi),%rbx
 PC (0x0046b9b8) ok
 source "0x38(%rdi)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nvidia-settings
Stacktrace:
 #0 0x000000000046b9b8 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff8b4074f8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 3171):
 #0 0x000000000046b9b8 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff8b4074f8
Title: nvidia-settings crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

Revision history for this message
hugo_laffez (lars-lydersen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Timo Aaltonen (tjaalton)
visibility: 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.