nvidia-settings can't save settings to xorg.conf

Bug #439192 reported by Johan Ryberg
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Karmic by Johan Ryberg

Bug Description

Binary package hint: nvidia-settings

I tried to activate a secondary screen and then I pressed "Save xorg.conf"-ish-button I got this error in the terminal from where I started the application:

jory01@jory01-labb:~$ gksudo nvidia-settings

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

^C

The nvidia-settings stopped responding and I had to press Ctrl+C

apport also wanted to add this text in the summary: nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

ProblemType: Crash
Architecture: i386
Date: Wed Sep 30 09:15:30 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_US.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
Johan Ryberg (jryberg) 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
Revision history for this message
Johan Ryberg (jryberg) wrote : Re: nvidia-settings crashed then activating secondary screen

I noticed it does not matter what I do, I can't save any kind of changes without this kind of error message

Johan Ryberg (jryberg)
Changed in nvidia-settings (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Johan Ryberg (jryberg) wrote :

I would like to change the subject to "nvidia-settings can't save to xorg.conf" or something like that.. I'm not alone and it's very very soon time for release

summary: - nvidia-settings crashed then activating secondary screen
+ nvidia-settings can't save settings to xorg.conf
Revision history for this message
Johan Ryberg (jryberg) wrote :

I'm having 2 different computers with a clean installation of Ubuntu 9.10 and Nvidia graphics with exactly the same problem.

Is it the same for others with the same issue?

Revision history for this message
Vik (vik-catalyst) wrote :

@rancor: Yup, exactly the same here. Karmic install stole my second screen. But that's nothing - you should've seen the mess it made when I tried upgrading from Jaunty! Ye Gods. Nobody QA'd that on a Ge 7300 machine for sure.

Revision history for this message
starslights (starslights) wrote :

Hello,

I run kubuntu karmic on x86 64 and i have excatelly the same error when i try to add a secound monitor and save to xorg.conf

Linux moon 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

driver: 185.18.36

Revision history for this message
Pau Garcia Quiles (pgquiles) wrote :

Make sure packages pkg-config and python-gtk2 are installed

Revision history for this message
bugbot (bugbot) wrote :

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.

Changed in nvidia-settings (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) 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-settings (Ubuntu):
status: Incomplete → Expired
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.