nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #437549 reported by Hilario J. Montoliu (hjmf)
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

nvidia-config applet crashed while saving changes

~$ lsb_release -rd && apt-cache policy nvidia-settings
Description: Ubuntu karmic (development branch)
Release: 9.10
nvidia-settings:
  Installed: 180.25-0ubuntu1
  Candidate: 180.25-0ubuntu1
  Version table:
 *** 180.25-0ubuntu1 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Sun Sep 27 10:43: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=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x80b68dd: mov 0x1c(%edi),%ebx
 PC (0x080b68dd) ok
 source "0x1c(%edi)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
Title: nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
g_cclosure_marshal_VOID__VOID ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
tags: added: karmic
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.