nvidia-settings crashed with SIGSEGV

Bug #467239 reported by MrChris
This bug report is a duplicate of:  Bug #438109: nvidia-settings crashed with SIGSEGV. Edit Remove
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

after upgrading jaunty to karmic, i occasionally get a pop-up on my taskbar saying that my x-server is broken and i should look up this link http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/

i tried to look up my config in system -> prerefences -> display when this crash occured

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 20:06:15 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-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x818210: mov %edx,0x208(%eax)
 PC (0x00818210) ok
 source "%edx" ok
 destination "0x208(%eax)" (0x08c2f1a8) in non-writable VMA region: 0x08c2f000-0x08c30000 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-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
MrChris (cresnik) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #438109, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-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.