[elrepo] nvidia-setting segfault on CentOS 6.5 x86_64

Sun Jul 6 13:39:33 EDT 2014

Thanks Phil

The crash occurs each time I just quit nvidia-setting, so even if I
don't change anything in it (no need to change a specific thing).
In the attachment I provide you the export of the current nvidia
settings (done via "save current configuration" function of the
utility), but as I said, it seems that any configuration leads to
segfault after quitting it.
By the way, one does not notice it through the system behavior, but it
is always present in the log.

Best regards
Bojan

> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 06 Jul 2014 08:42:18 +0100
> From: Phil Perry <phil at elrepo.org>
> To: elrepo at lists.elrepo.org
> Subject: Re: [elrepo] nvidia-setting segfault on CentOS 6.5 x86_64
> Message-ID: <53B8FDDA.6060205 at elrepo.org>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hi Bojan,
> 
> Welcome to the list.
> 
> On 05/07/14 11:56, Bojan Radovic wrote:
> > Hello
> > 
> > I am glad to join the ELRepo mailing list.
> > I use a desktop PC with an nVidia GPU and CentOS-6.5 x86_64.
> > The GPU model is : (output of lspci | grep VGA)
> > 
> > 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS
> > 290] (rev a1)
> > 
> > So I have installed the NVIDIA driver kernel module from ELREPO, like
> > explained here : http://elrepo.org/tiki/kmod-nvidia
> > 
> > Now the driver seems to work more or less well, but each time I use
> > nvidia-setting utility, after quitting it there is a segfault series of
> > error messages in /var/log/messages :
> > 
> > Jul  5 12:47:38 Linux kernel: nvidia-settings[8876]: segfault at
> > 3918201510 ip 0000003918201510 sp 00007fffb1200518 error 14
> > Jul  5 12:47:39 Linux abrtd: Directory 'ccpp-2014-07-05-12:47:38-8876'
> > creation detected
> > Jul  5 12:47:39 Linux abrt[8878]: Saved core dump of pid 8876
> > (/usr/bin/nvidia-settings)
> > to /var/spool/abrt/ccpp-2014-07-05-12:47:38-8876 (49676288 bytes)
> > Jul  5 12:47:39 Linux abrtd: Package 'nvidia-x11-drv' isn't signed with
> > proper key
> > Jul  5 12:47:39 Linux abrtd: 'post-create' on
> > '/var/spool/abrt/ccpp-2014-07-05-12:47:38-8876' exited with 1
> > Jul  5 12:47:39 Linux abrtd: Deleting problem directory
> > '/var/spool/abrt/ccpp-2014-07-05-12:47:38-8876'
> > Jul  5 12:47:48 Linux kernel: nvidia-settings[8882]: segfault at
> > 3918201510 ip 0000003918201510 sp 00007fff04e7d9d8 error 14
> > Jul  5 12:47:49 Linux abrt[8892]: Not saving repeating crash in
> > '/usr/bin/nvidia-settings'
> > 
> > 
> 
> I am unable to replicate this issue. Please could you describe exactly
> what you changed in nvidia-settings to trigger the crash. Does it crash
> every time, only if you change something, only if you change a specific
> thing?
> 
> > To install the ELRepo for CentOS-6  I had followed these instructions :
> > http://elrepo.org/tiki/tiki-index.php
> > so I wonder when I see that the nvidia-x11-drv' isn't signed with proper
> > key
> > 
> 
> ABRT is Red Hat's Automatic Bug Reporting Tool. On RHEL, ABRT would be
> expecting the package to be signed by Red Hat but as nvidia-x11-drv
> isn't part of the disto that is not the case.
> 
> I'm not sure why CentOS ship abrt, perhaps they have patched abrt so
> automatic bug reports are sent to them, thus one might assume on CentOS
> abrt expects to see a package signed by the CentOS key.
> 
> Either way, this warning is safe to ignore. What is of more concern is
> the crash itself.
> 
> Regards,
> 
> Phil
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20140706/ba7ac6a3/attachment.html>
-------------- next part --------------
#
# nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Sun Jul  6 19:33:58 2014
#

# ConfigProperties:

RcFileLocale = C
ToolTips = Yes
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = No
ShowQuitDialog = No
UpdateRulesOnProfileNameChange = Yes
Timer = PowerMizer_Monitor_(GPU_0),Yes,1000
Timer = Thermal_Monitor_(GPU_0),Yes,1000
Timer = Memory_Used_(GPU_0),Yes,3000

# Attributes:

0/SyncToVBlank=0
0/LogAniso=0
0/FSAA=0
0/TextureSharpen=0
0/TextureClamping=1
0/FXAA=0
0/AllowFlipping=1
0/FSAAAppControlled=1
0/LogAnisoAppControlled=1
0/OpenGLImageSettings=2
0/FSAAAppEnhanced=0
0/XVideoSyncToDisplayID=DVI-I-0
[DPY:DVI-I-0]/Dithering=0
[DPY:DVI-I-0]/DitheringMode=0
[DPY:DVI-I-0]/DitheringDepth=0
[DPY:DVI-I-0]/SynchronousPaletteUpdates=0
[DPY:DVI-I-1]/Dithering=0
[DPY:DVI-I-1]/DitheringMode=0
[DPY:DVI-I-1]/DitheringDepth=0
[DPY:DVI-I-1]/SynchronousPaletteUpdates=0
[DPY:DVI-I-2]/RedBrightness=0.000000
[DPY:DVI-I-2]/GreenBrightness=0.000000
[DPY:DVI-I-2]/BlueBrightness=0.000000
[DPY:DVI-I-2]/RedContrast=0.000000
[DPY:DVI-I-2]/GreenContrast=0.000000
[DPY:DVI-I-2]/BlueContrast=0.000000
[DPY:DVI-I-2]/RedGamma=1.000000
[DPY:DVI-I-2]/GreenGamma=1.000000
[DPY:DVI-I-2]/BlueGamma=1.000000
[DPY:DVI-I-2]/Dithering=0
[DPY:DVI-I-2]/DitheringMode=0
[DPY:DVI-I-2]/DitheringDepth=0
[DPY:DVI-I-2]/DigitalVibrance=0
[DPY:DVI-I-2]/ColorSpace=0
[DPY:DVI-I-2]/ColorRange=0
[DPY:DVI-I-2]/SynchronousPaletteUpdates=0
[DPY:DVI-I-3]/Dithering=0
[DPY:DVI-I-3]/DitheringMode=0
[DPY:DVI-I-3]/DitheringDepth=0
[DPY:DVI-I-3]/SynchronousPaletteUpdates=0