nvidia-settings crashed with SIGSEGV

[Pako]

Binary package hint: nvidia-settings

crash when nvidia-settings window closed

ProblemType: Crash
Architecture: i386
Date: Mon Sep 28 14:25:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: nvidia
Package: nvidia-settings 180.25-0ubuntu1
ProcCmdline: /usr/bin/nvidia-settings
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x9d2210: mov %edx,0x208(%eax)
 PC (0x009d2210) ok
 source "%edx" ok
 destination "0x208(%eax)" (0x088c9220) in non-writable VMA region: 0x088c9000-0x088ca000 r--p None
SegvReason: writing VMA None
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/tls/i686/cmov/libdl.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/tls/i686/cmov/libdl.so.2
Title: nvidia-settings crashed with SIGSEGV
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_dl_close_worker (map=0x88c8ae0) at dl-close.c:150
_dl_close (_map=0x88c8ae0) at dl-close.c:742
dlclose_doit (handle=0x88c8ae0) at dlclose.c:37
_dl_catch_error (objname=<value optimized out>,
_dlerror_run (operate=<value optimized out>,

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.