nvidia-settings crashed with SIGSEGV in XcursorLibraryLoadImages()

[Nick Messick]

Binary package hint: nvidia-settings

This program crashed on launch.

ProblemType: Crash
Architecture: i386
Date: Thu Nov 5 12:54:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: wl nvidia
Package: nvidia-settings 180.25-0ubuntu1
ProcCmdline: /usr/bin/nvidia-settings
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 ?? () from /usr/lib/libXcursor.so.1
 ?? () from /usr/lib/libXcursor.so.1
 XcursorLibraryLoadImages () from /usr/lib/libXcursor.so.1
 XcursorShapeLoadImages () from /usr/lib/libXcursor.so.1
 XcursorTryShapeCursor () from /usr/lib/libXcursor.so.1
Title: nvidia-settings crashed with SIGSEGV in XcursorLibraryLoadImages()
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0xb6deb0bc: call 0xb6de6e57
 PC (0xb6deb0bc) ok
 source "0xb6de6e57" (0xb6de6e57) ok
 destination "(%esp)" (0xbf9acee0) in non-writable VMA region: 0xbf9ac000-0xbf9ad000 r--p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None

[Apport retracing service (apport)]

StacktraceTop:_XcursorThemeInherits (
XcursorScanTheme (theme=<value optimized out>,
XcursorLibraryLoadImages (file=0xb6dec892 "xterm",
XcursorShapeLoadImages (shape=152, theme=0x827d840 "Human",
XcursorTryShapeCursor (dpy=0x82608c8, source_font=25165864,

[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.