"apply" of multi-monitor setting results in crash

Bug #1273652 reported by Markus J Schmidt
70
This bug affects 15 people
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Confirmed
High
Unassigned

Bug Description

After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore.
After configuration of "X Server Display Configuration" hit hit the "apply" button and then the program simply quit.

A workaround is to click on "Save to X Configuration file" and restart the computer.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-settings 331.20-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Tue Jan 28 12:51:27 2014
InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Markus J Schmidt (smiddy84) wrote :
Revision history for this message
Alberto Milone (albertomilone) wrote :

Please enable Apport's crash reporting, and attach a dump of the crash:

See the "Enable Apport" section on this page:
https://wiki.ubuntu.com/Testing/EnableProposed

Changed in nvidia-settings (Ubuntu):
status: New → Incomplete
Revision history for this message
Markus J Schmidt (smiddy84) wrote :

That is not possble! My system do not recognize the crash an no report is created!

Revision history for this message
Alberto Milone (albertomilone) wrote :

did you follow the instructions in the link?

Revision history for this message
Markus J Schmidt (smiddy84) wrote :

Yes apport is configured correctly I tried the test with sh -c 'kill -SEGV $$' and could successfully produce a crash report...

There is no crash occuring when I hit "apply". It seems the program is simply closing.

I tried to use to old version 304.88-0ubuntu0.0.2 but could not change the monitors.

Revision history for this message
Alberto Milone (albertomilone) wrote :

maybe try launching the panel from the command line by typing "nvidia-settings" in a terminal and attach the output (if any)

Revision history for this message
Markus J Schmidt (smiddy84) wrote :

Indeed I receive an output:

--------------------------------
smiddy@3000-N200:~$ nvidia-settings

ERROR: Error querying target relations

The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 676 error_code 2 request_code 140 minor_code 25)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
smiddy@3000-N200:~$

--------------------------------

The line with the ERROR:... comes up when launching the program, while the other lines come up when clicking on "apply" . I tried the command "nvidia-settings --- sync", but the result was identical.

I attached my xsession-errors as well.

Revision history for this message
Clayton Bonser (clay-m) wrote :

I'm having the same problem too. This is recent, so I suspected an update may be the culprit. I have tried reverting to a previous version of nvidia driver, but that made no difference.
Error message is substantially the same-

ERROR: Error querying target relations

The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 82 error_code 1 request_code 154 minor_code 29)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Changed in nvidia-settings (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michal Illich (a-list-l) wrote :

I confirm this too. I have Kubuntu 12.04, kept up to date.
The last update of nvidia-settings changed few things (e.g. instead of "TwinView" the choice is called "xscreen 0") and it started to behave exactly as Markus described - crash on Apply, works only with save+restart.

Revision history for this message
Markus J Schmidt (smiddy84) wrote :

Hi Michal,

could you please click on "This bug affects me" that we get a higher rating?

Revision history for this message
Jim Smith (jim7fl) wrote :

Any solution in sight? or perhaps a workaround?

Revision history for this message
Jim Smith (jim7fl) wrote :

This is from my terminal window

......................../home/jim# nvidia-settings

ERROR: Error querying target relations

ERROR: Error querying target relations

Segmentation fault (core dumped)
root@jim-dt500:/home/jim# nvidia-settings

ERROR: Error querying target relations

ERROR: Error querying target relations

Segmentation fault (core dumped)

Revision history for this message
Markus J Schmidt (smiddy84) wrote :

After upgrading to xubuntu 14.04 the bug is still present. I still get the following error:

ERROR: Error querying target relations

The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 740 error_code 2 request_code 158 minor_code 25)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

tags: added: trusty
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

It affects an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse).

Changed in nvidia-settings (Ubuntu):
importance: Undecided → High
Revision history for this message
Galvatron (megatron) wrote :

I have the same issue with a single display.

- Ubuntu 12.04.4 32-bit
- "Saucy" HWE stack
- 7300GT
- Drivers 304.88

In my case the solution was to downgrade nvidia-settings back to 304.88.

Should I issue a new bug report?

Revision history for this message
Roberto González Correa (rob-e-gonzlez) wrote :

I have a similar issue with Ubuntu 14.04 (64 bits) and Nvidia driver 304.117 (please, refer to Bug #1388430 for details).
I spoke to Nvidia Customer Care support and they are requesting me to install another driver version (304.123) from Nvidia web site. Unfortunately, installation instructions are hard for me to follow, so I would need some help in order to test this driver version and give the technicians a proper feedback. If someone thinks that this could help to solve the issue, please feel free to e-mail me and I'll do my best to colaborate.

Revision history for this message
Roberto González Correa (rob-e-gonzlez) wrote :

Regarding the issue I commented above, I could fix it by manually installing driver 304.123. Please, refer to Bug #1388430 for details.

I hope this can help you.

Revision history for this message
Jason Smith (sddfdds) wrote :

I believe the problem is a mismatch between the driver and the settings app. The nvidia-settings attached to driver 304 is actually 331...if you manually install nvidia-settings 304 (the deb for which you can dig up somewhere on the nvidia-settings launchpad/files page) all is ok

Revision history for this message
Jason Smith (sddfdds) wrote :

I don't remember precisely where I found it but nvidia-settings-304-updates_304.88-0ubuntu0.0.3_i386.deb is what i installed.

Revision history for this message
Mark (mark-k) wrote :

I also see this problem with Lubuntu 14.10 x86-64, a clean install. nvidia-settings version 331 is broken when used with version 304 of the Nvidia binary driver (nvidia-304).

Running nvidia-settings, changing refresh rate and clicking Apply causes nvidia-settings to crash with this console output:

The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 655 error_code 2 request_code 158 minor_code 25)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

My laptop has an Nvidia Geforce Go 7300. Version 304 of the driver is the last which works with Geforce 7000-series GPUs. I installed the Nvidia binary driver using Additional Drivers. That installs version 304 of the driver and version 331 of nvidia-settings.

There are packages called (for example) nvidia-settings-304 in the repository, but they just cause v331 to be installed.

I previously used Lubuntu 12.04, and there I was able to downgrade to nvidia-settings 304 (using Package->Force Version... in Synaptic) which works correctly, but that's not possible with 14.10.

Presumably this is an upstream (Nvidia) bug/incompatibility. However as a workaround, here are some suggested fixes which should be quite easy for the Ubuntu side:
 - Add nvidia-settings-304 real package to the 14.10 repository. Then the user can manually force that version.
 - Make nvidia-304 recommend nvidia-settings-304 and conflict with nvidia-settings-331.

tags: added: utopic
Revision history for this message
Mark (mark-k) wrote :

I was able to manually install nvidia-settings-304 in from the precise repository by downloading the .deb file from
http://packages.ubuntu.com/precise/amd64/nvidia-settings/download
and installing it.

Revision history for this message
Mark (mark-k) wrote :

It seems nvidia-settings 346.59 (available from utopic-backports) works better with nvidia-driver-304. I can change the desktop resolution or refresh rate without a crash.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.