nvidia-settings crashed with SIGSEGV in g_closure_invoke()

[more10]

Binary package hint: nvidia-settings

Fresly updated 8.10 x64 beta

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: nvidia
Package: nvidia-settings 177.78-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/nvidia-settings
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nvidia-settings crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
IA__g_closure_invoke (closure=0x25b5d70, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x2158a70, detail=0, instance=0x25b0da0, emission_return=0x0,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[lasers (lasers)]

Occured when I tried to save the X to conf file.

[Cody A.W. Somerville (cody-somerville)]

I can confirm this bug.

[Tero Konnola (weetabix)]

Still problem with Karmic Koala (not final, kernel 2.6.31-9-generic 64 bit).

Way around the "Saving x configuration file" crash is to delete /etc/X11/xorg.conf, sudo nvidia-xconfig, sudo nvidia-settings.

Default xorg.conf after Nvidia drivers (185) is not compatible with nvidia-settings, so the parsing of xorg.conf doesn't work even if you are root.

[briancb (brian-bosomworth)]

My problem with nvidia is the settings are stuck with main screen on separate x screen twin veiw etc greyed out. When loading Nvidia-settings at root I get this:

ERROR: Cannot open display 'Dad:0.0'.

ERROR: Unable to assign attribute CursorShadow specified on line 21 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowAlpha specified on line 22 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowRed specified on line 23 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowGreen specified on line 24 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowBlue specified on line 25 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowXOffset specified on line 26 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute CursorShadowYOffset specified on line 27 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute SyncToVBlank specified on line 28 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute LogAniso specified on line 29 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute FSAA specified on line 30 of configuration
file '/home/brian/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute TextureSharpen specified on line 31 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute AllowFlipping specified on line 32 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute FSAAAppControlled specified on line 33 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute LogAnisoAppControlled specified on line 34 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute OpenGLImageSettings specified on line 35 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute FSAAAppEnhanced specified on line 36 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute RedBrightness specified on line 37 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute GreenBrightness specified on line 38 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute BlueBrightness specified on line 39 of
configuration file '/home/brian/.nvidia-settings-rc' (no Display
connection).

ERROR: Unable to assign attribute RedContrast specified on line 40 of
config...

[Jeroen Hoek (mail-jeroenhoek)]

Same problem as #9: nvidia-settings cannot parse the current xorg.conf (Karmic alpha 6).

[Risto Välimäki (risto-valimaki)]

This affects my Karmic Alpha 6 (64bit) installation too, but this may be duplicate of the following bug:

https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/286424

[wolfen69 (wolfen69)]

Affects me also in 9.10 beta.

[Poltiser (poltiser)]

it is still there

[Paul Libert (plibert)]

Confirmed too - need to reconfigure X-server at each startup.
Karmic After Beta Daily Live

[wraithmonk (geoffitton-deactivatedaccount)]

Also affects me in Karmic 9.10 beta- AMD 64-bit - Kernel 2.6.31-14-generic #47-Ubuntu x86_64 GNU/Linux

[jraborg (jraborg)]

this affected me when installed from scratch Linux stingray 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
but didn't have the problem when upgrade from 9.04 either 32/64 bits version

[wolfen69 (wolfen69)]

This is still happening in 9.10 RC (64bit). When setting up Twinview via nvidia-settings, I get "failed to parse existing x config file '/etc/X11/xorg.conf'

I really hope this is fixed before final release. This is a major bug that will affect all users with nvidia cards and dual monitors.

[bunbuku (bunbuku)]

Me too.
This Problem is Important.

[jraborg (jraborg)]

Still have same isue:

root@shadow:/home/jraborg# /usr/bin/nvidia-settings

ERROR: Invalid display device DFP-1 specified on line 46 of configuration
file
       '/root/.nvidia-settings-rc' (the currently enabled display devices
are
       DFP-0 on shadow:0.0).

ERROR: Invalid display device DFP-1 specified on line 48 of configuration
file
       '/root/.nvidia-settings-rc' (the currently enabled display devices
are
       DFP-0 on shadow:0.0).

ERROR: Invalid display device DFP-1 specified on line 50 of configuration
file
       '/root/.nvidia-settings-rc' (the currently enabled display devices
are
       DFP-0 on shadow:0.0).

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

Segmentation fault

On Sun, Oct 25, 2009 at 8:49 PM, bunbuku <email address hidden> wrote:

> Me too.
> This Problem is Important.
>
> --
> nvidia-settings crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/285192
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-settings” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: nvidia-settings
>
> Fresly updated 8.10 x64 beta
>
> ProblemType: Crash
> Architecture: amd64
> CrashCounter: 1
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/nvidia-settings
> NonfreeKernelModules: nvidia
> Package: nvidia-settings 177.78-0ubuntu2
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/nvidia-settings
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: nvidia-settings
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> Title: nvidia-settings crashed with SIGSEGV in g_closure_invoke()
> Uname: Linux 2.6.27-7-generic x86_64
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

[wolfen69 (wolfen69)]

It will be a major mistake to release ubuntu 9.10 with this bug. There are a lot of users with nvidia cards that will be affected by this.

[wolfen69 (wolfen69)]

Great job letting this MAJOR bug make it into the final release. 9.10 is useless to me without being able to save video settings. Btw, this also happens in Kubuntu 9.10.

Expect many more people to voice displeasure.

[carpie (elcarpie)]

As a workaround, I added:
    Device "Default Device"
in the Screen section of the original xorg.conf. This caused nvidia-settings to be able to parse the file and write it's changes. My system is using Kubuntu 9.10 final.

[Thiago Fraga (tfraga-ufs)]

I also have this bug.
carpie (#23) suggestion worked for me.

[Felipe Blanco-Ollé (fblanco)]

I can confirm this bug - it's still there in the final 9.10 release.

Carpie's workaround does the trick, thanks!

[wolfen69 (wolfen69)]

It's too bad this bug is going to make people do a 360 back towards windows. Just because us geeks know the workaround, does not mean Joe Shmoe will have the patience to research it. Major mistake on ubuntu's part. Great job dev team! Who uses nvidia-settings anyway? Sweep it under the rug.

[madbiologist (me-again)]

Is this problem still occurring on Ubuntu 10.04 "Lucid Lynx"? What about on Ubuntu 10.10 "Maverick Meerkat"? What about on Ubuntu 11.04 "Natty Narwhal"?

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