ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #34989
Re: [Bug 286424] Re: nvidia-settings crashes when user clicks Save To X Configuration File
Review post 80
"oranges wrote on 2009-10-22: #80
Greetings, just wanted to let you guys know, I solved this problem by doing:
a) sudo nvidia-xconfig <- it should detect the missing "default
display/screen" entry and create a new file for you to write in.
then do...
b) sudo nvidia-settings and do the usual thing to save your settings.
That's all I did - it worked.
Oranges"
-----Original Message-----
From: bounces@xxxxxxxxxxxxx [mailto:bounces@xxxxxxxxxxxxx] On Behalf Of Fabian A. Scherschel
Sent: Tuesday, November 17, 2009 3:45 AM
To: jraborg@xxxxxxxxx
Subject: [Bug 286424] Re: nvidia-settings crashes when user clicks Save To X Configuration File
I've been following this bug for quite a while and it is pretty clear
that this is *NOT* a permissions problem. I've always run nvidia-
settings with gksudo / sudo and the problem was always there. So please
don't mark as fixed because of permissions.
I have not tested this with the latest Karmic update but the program did
crash when run with root privileges on a then-uptodate Karmic as late as
last week.
--
nvidia-settings crashes when user clicks Save To X Configuration File
https://bugs.launchpad.net/bugs/286424
You received this bug notification because you are a direct subscriber
of the bug.
Status in “nvidia-settings” package in Ubuntu: Confirmed
Status in “nvidia-settings” source package in Intrepid: Confirmed
Bug description:
Binary package hint: nvidia-settings
Clicking "Save To X Configuration File" causes immediate crash of
nvidia-settings, after running sudo nvidia-settings to set up dual
monitors using TwinView.
Not sure if this is due to permissions related to the new X config
scheme (i.e. no longer using xorg.conf for display config)? I am also
confused as to why the repo driver is 177.80, but the repo nvidia-
settings is 177.78?
Error msg: nvidia settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
System: Ubuntu Intrepid Beta 8.10, Intel P4 3.0 (hyperthreaded).
2.6.27-7 kernel. Standard closed-source Nvidia 177 driver from Intrepid
repos, on GeForce 9500GT, installed using Hardware Drivers panel
(jockey).
Installed Nvidia packages are:
177.78-0ubuntu2 ( nvidia-settings )
177.80-0ubuntu2 ( nvidia-glx-177 )
177.80-0ubuntu2 ( nvidia-177-kernel-source )
177.80-0ubuntu2 ( nvidia-177-modaliases )
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nvidia-settings
NonfreeKernelModules: nvidia
Package: nvidia-settings 177.78-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: nvidia-settings
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nvidia-settings
StacktraceTop:
?? ()
?? ()
?? ()
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.27-7-generic i686
UserGroups:
--
nvidia-settings crashes when user clicks Save To X Configuration File
https://bugs.launchpad.net/bugs/286424
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in ubuntu.
Follow ups
References