[Hardy] nvidia-settings crashed with SIGSEGV in g_closure_invoke()

Bug #194528 reported by Daniel06
58
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-settings

Using Ubuntu 8.04 Hardy (up-to-date) on my Lenovo T61 laptop (with Nvidia Quadro NVS140M), nvida-settings chrashed while I was configuring an external Display.

I have chosen " X-Server Display Configuration " and marked the external display (Eizo S2231W connected via DVI) as "seperate X screen" by clicking on the "configure" button.

Then I clicked at "apply" and "Save to X Configuration File", there comes the crash. Preferences are automatically set to default after the crash.

It did not matter, if I start nvidia-settings via terminal (sudo nvidia-settings) or via systemmenu, the crash is reproducable.

installed version of Nvidia-settings : 1.0+20071221-0
version of Nvidia driver: 169.09

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 22 23:04:38 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: nvidia
Package: nvidia-settings 1.0+20071221-0ubuntu5
PackageArchitecture: amd64
ProcCmdline: /usr/bin/nvidia-settings
ProcCwd: /home/daniel
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.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 angelique 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Revision history for this message
Daniel06 (dleh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
IA__g_closure_invoke (closure=0xda5a30, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x771ec0, detail=0, instance=0xda4820, emission_return=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Daniel06 (dleh) wrote :

Seems to be fixed with actual updates (March 2nd)

Revision history for this message
Wade Menard (wade-ezri) wrote :

I am seeing this issue as well, performing the same steps (trying to enable a device as a separate X screen). With latest packages under x86.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-settings - 1.0+20080304-0ubuntu1

---------------
nvidia-settings (1.0+20080304-0ubuntu1) hardy; urgency=low

  * New upstream version. (LP: #198484)
    - Fixes errors writing out xorg.conf
      (LP: #194528,195241,195302,197568,198215)

 -- Mario Limonciello <email address hidden> Tue, 04 Mar 2008 13:50:58 -0600

Changed in nvidia-settings:
status: New → Fix Released
Revision history for this message
spideylinux (spidey-oldskool) wrote :

I don't believe that this has been fixed. Just posted a bug with crash info in bug 204831.

Revision history for this message
Leandro Pereira de Lima e Silva (leandro-limaesilva) wrote :

The bug isn't corrected yet. I had the same problem here with 1.0+20080304-0ubuntu1.

Changed in nvidia-settings:
status: Fix Released → Confirmed
Revision history for this message
cornbread (corn13read) wrote :

still not fixed apparently. running latest intrepid alpha.

Revision history for this message
spideylinux (spidey-oldskool) wrote : Re: [Bug 194528] Re: [Hardy] nvidia-settings crashed with SIGSEGV in g_closure_invoke()

Found a work around that is good in Hardy. Grabbed the EnvyNG package
and installed the latest drivers (173.14.12). Then I ran as root
these two commands: 'nvidia-xconfig', and 'nvidia-settings'. In the
settings I setup twinview and then saved to the X Config File,
Restarted X and all was good. Give it a shot.

:wq!
jason

On Wed, Sep 17, 2008 at 2:42 PM, cornbread <email address hidden> wrote:
> still not fixed apparently. running latest intrepid alpha.
>
> --
> [Hardy] nvidia-settings crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/194528
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "nvidia-settings" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: nvidia-settings
>
> Using Ubuntu 8.04 Hardy (up-to-date) on my Lenovo T61 laptop (with Nvidia Quadro NVS140M), nvida-settings chrashed while I was configuring an external Display.
>
> I have chosen " X-Server Display Configuration " and marked the external display (Eizo S2231W connected via DVI) as "seperate X screen" by clicking on the "configure" button.
>
> Then I clicked at "apply" and "Save to X Configuration File", there comes the crash. Preferences are automatically set to default after the crash.
>
> It did not matter, if I start nvidia-settings via terminal (sudo nvidia-settings) or via systemmenu, the crash is reproducable.
>
> installed version of Nvidia-settings : 1.0+20071221-0
> version of Nvidia driver: 169.09
>
> ProblemType: Crash
> Architecture: amd64
> Date: Fri Feb 22 23:04:38 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/nvidia-settings
> NonfreeKernelModules: nvidia
> Package: nvidia-settings 1.0+20071221-0ubuntu5
> PackageArchitecture: amd64
> ProcCmdline: /usr/bin/nvidia-settings
> ProcCwd: /home/daniel
> ProcEnviron:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=de_DE.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 angelique 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video
>

Revision history for this message
Christoph Langner (chrissss) wrote :

I can confirm this for Intrepid Beta...

Revision history for this message
Eddie Hung (eddieh) wrote :

Thanks Jason - I just did a nvidia-xconfig followed by nvidia-settings, and it worked, using the latest 177 drivers on intrepid.
It turns out that when the nvidia drivers are installed, nvidia-xconfig is not run, which is used to create a xorg.conf that nvidia-settings can recognise. Hence, later when it comes to try and modify the existing xorg.conf file (which in my case was the default intrepid one), it doesn't know how to interpret it, and segfaults.

In summary, try a nvidia-xconfig before nvidia-settings!

Revision history for this message
Simone Crescenzo (simone.crescenzo-deactivatedaccount) wrote :

Confirmed in Intrepid Beta too...

Revision history for this message
Jorge Pereira (jpereiran) wrote :

I receive the same problem using the host amd64 and driver "nvidia-173-kernel-source"

Revision history for this message
Jorge Pereira (jpereiran) wrote :

I think that this problem when executing the "nvidia-settings", happen when the SCIM is running! nvidia-settings running when SCIM has been started, receive below message in stderr

"The messenger is now down
An IOException occurred at scim_bridge_client_imcontext_set_cursor_location ()"

Revision history for this message
Dann S. Washko (dann) wrote :

I can confirm that this problem is happening in Intrepid Beta but it seems to be related to the xorg.conf file more than anything. The work around to run nvidia-xconfig before running nvidia-settings did not work for me. Interestingly enough, my old xorg.conf (which no longer worked when I upgraded to intrepid) allowed me to save the nvidia-settings. I had to use my new xorg.conf and get into X, copy my old xorg.conf over and then run nvidia-settings.

I'm running nvidia-173-kernel-source.

Revision history for this message
Mikhael Enosh (mkhlnsh) wrote :

I did not filed a bug about this, since i think is kinda related to this one.
I'm using Intrepid Beta and for me nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID(), but after runing nvidia-xconfig nvidia-settings worked.
So i think is only about nvidia-xconfing not beeing run when installing nvidia drivers.

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.