nvidia-settings crashed with SIGSEGV in free()

Bug #428262 reported by komputes
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned
nvidia-graphics-drivers-180 (Ubuntu)
Invalid
Medium
Unassigned
nvidia-settings (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nvidia-settings

I have two monitors one VGA and one DVI. I am trying to make an extended desktop and am experiencing many issues.

Just installed Ubuntu 9.10 on a computer using the following VGA controller:

01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb

There are many issues I have experienced:

- when trying to "Save to X Configuration File" nvidia-settings crashed with error: Failed to parse existing X config file '/etc/X11/xorg.conf'!
-Fullscreening (maximized) applications take up the whole desktop. Fullscreening in totem, displays the movie on both screens and crashes totem. How can I avoid this?
-Windows that pop up end up in the middle of the desktop meaning the dialog is shared on both screen (no concept of primary monitor)
-Artefacts are seen when moving windows around when compiz is run
-Since the resolutions do no match on the Y-axis (vertical) gnome panel runs into invisivle space, not displaying half of the icons on the right of the second screen (right).

$ xrandr
Screen 0: minimum 320 x 240, current 2720 x 1024, maximum 2846 x 1024
default connected 2720x1024+0+0 0mm x 0mm
   1280x1024 50.0 51.0 96.0
   1280x960 52.0
   1152x864 53.0 54.0 55.0 56.0
   1024x768 57.0 58.0 59.0 60.0
   960x600 61.0
   960x540 62.0
   840x525 63.0 64.0 65.0
   832x624 66.0
   800x600 67.0 68.0 69.0 70.0 71.0
   800x512 72.0
   720x450 73.0
   680x384 74.0 75.0
   640x512 76.0 77.0
   640x480 78.0 79.0 80.0 81.0
   576x432 82.0 83.0 84.0 85.0
   512x384 86.0 87.0 88.0
   416x312 89.0
   400x300 90.0 91.0 92.0
   320x240 93.0 94.0 95.0
   2720x1024 96.0 50.0*
   1440x900 50.0 51.0
   2846x1024 51.0

I am using nvidia binary version 173

dpkg:
ii nvidia-173-kernel-source 173.14.20-0ubuntu1 NVIDIA binary kernel module source
ii nvidia-173-modaliases 173.14.20-0ubuntu1 Modaliases for the NVIDIA binary X.Org driver
ii nvidia-185-modaliases 185.18.36-0ubuntu2 Modaliases for the NVIDIA binary X.Org driver
ii nvidia-96-modaliases 96.43.13-0ubuntu2 Modaliases for the NVIDIA binary X.Org driver
ii nvidia-common 0.2.15 Find obsolete NVIDIA drivers
ii nvidia-glx-173 173.14.20-0ubuntu1 NVIDIA binary Xorg driver

ProblemType: Crash
Architecture: i386
Date: Sat Sep 12 00:56:09 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_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0x80b68dd <gdk_pixbuf_from_pixdata@plt+420201>: 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:
 ?? ()
 ?? ()
 free () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Title: nvidia-settings crashed with SIGSEGV in free()
Uname: Linux 2.6.31-10-generic i686
UserGroups:

Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :

See terminal.log first for errors concerning ~/.nvidia-settings-rc

I erased .nvidia-settings-rc to avoid the error and got the following when trying to create two X sessions (one for each screen) and trying to save to xorg.conf

mike@TheXeons:~$ sudo rm .nvidia-settings-rc
mike@TheXeons:~$ sudo nvidia-settings

VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
Undefined Device "(null)" referenced by Screen "Default Screen".

Segmentation fault (core dumped)

Revision history for this message
komputes (komputes) wrote :

What I did to somewhat fix the situation:

sudo rm ~/.nvidia-settings-rc
sudo rm /etc/X11/xorg.conf
sudo nvidia-settings
# In the nvidia settings, Configure the two monitors to be 2 Seperate X Screen and enable Xinerama
# Saved to /etc/X11/xorg.conf (had to define file path)
# Edited xorg.conf to the attached, redefining define monitor 0 and 1 and switched the positioning from RightOf to LeftOf (personal preferences)

What issues exist in this configuration:
-Compiz cannot be enable. I get the following error when trying to set the appearance to "Extra":

The Composite extension is not available

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

StacktraceTop:?? ()
?? ()
?? ()
?? ()
IA__g_cclosure_marshal_VOID__VOID (closure=0x0,

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: crash
Revision history for this message
Travis Watkins (amaranth) wrote :

All of the compiz parts of this report are already reported (bug 277801 for example).

Changed in compiz (Ubuntu):
status: New → Invalid
Bryce Harrington (bryce)
affects: xorg-server (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in compiz (Ubuntu):
importance: Undecided → Medium
status: Invalid → Incomplete
Changed in nvidia-graphics-drivers-180 (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Changed in nvidia-settings (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Invalid
Bryce Harrington (bryce)
Changed in nvidia-settings (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Bryce Harrington (bryce)
Changed in nvidia-settings (Ubuntu):
status: Incomplete → Invalid
Changed in compiz (Ubuntu):
status: Incomplete → Invalid
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.