nvidia-settings >=319 segfaults on close

[Silviu C.]

After installation of the latest updates of the nvidia proprietary blob from 310.14 to 319.32 nvidia-settings crashes when pressing the quit button.

dmesg shows this:

[ 95.183668] nvidia-settings[2292]: segfault at 7f650be5c8a0 ip 00007f650be5c8a6 sp 00007fff69e6f5b8 error 7 in libpixbufloader-xpm.so[7f650be58000+6000]

and this:

[ 459.549845] nvidia-settings[3534]: segfault at 7f88dba4c8a0 ip 00007f88dba4c8a6 sp 00007ffff61e6b98 error 7 in libpixbufloader-xpm.so[7f88dba48000+6000]

Crash reports are caught by apport and sent (I hope) to Canonical

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-settings-experimental-310 319.32-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
Uname: Linux 3.5.0-39-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Tue Aug 20 20:48:24 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-settings-319-updates
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Phil Wyett (u-k-i-t)]

I also get this crash as the report states after an upgrade to the nvidia-319 driver and settings set.

I also get the issue but after removing a hdd and installing 12.04 fresh onto a new ssd then installing the nvidia-319 driver and settings set.

[Martin Spacek (mspacek)]

I just marked a few other bugs as duplicates of this. As I wrote in one of them, I see this in nvidia-settings 331.20 on my Thinkpad W510 (Nvidia Quadro FX 880M) on Xubuntu 12.10, using the xorg-edgers PPA, which brings in Linux 3.7.0.7-generic. I'm pretty sure I don't see this on Xubuntu 13.10, with the same version 331.20 of nvidia-settings, using the ubuntu-x-swat/x-updates PPA. Maybe this suggests the specific version of some pixbuf library is the culprit. User ssm suggests it's gtk2-engines-pixbuf (https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1268027/comments/21).

Here's what I get in Xubuntu 12.10 while running it in gdb and then hitting close:

user@box:~$ gdb nvidia-settings
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nvidia-settings...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/nvidia-settings
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecb5d700 (LWP 3402)]
[New Thread 0x7fffe7fff700 (LWP 3403)]

Program received signal SIGILL, Illegal instruction.
0x00007fffd6e46909 in ?? ()
   from /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
(gdb) q
A debugging session is active.

 Inferior 1 [process 3399] will be killed.

Quit anyway? (y or n) y

[Martin Spacek (mspacek)]

seems to apply to all versions since 319

[Fink Nottle (finknottle)]

The official version of nvidia-settings-304 in the precise-updates repository points to version 331. So if you have precise-updates enabled, even if you try to install the 304 version, it will install 331 by default. One needs to manually select an older version to get around this bug.