nvidia-settings window expands to extremely wide size, crashing metacity

[Delan Azabani]

In natty with nvidia-settings 260.19.21-0ubuntu2, clicking the 'X Server Display Configuration' item makes the nvidia-settings window extremely wide, and metacity crashes. Metacity won't restart without crashing until nvidia-settings is closed. This doesn't appear to be a problem with nvidia-settings itself as no update for it has been released for a while now. Attached is a photo of my screens when it happens; unfortunately I was unable take a real screenshot.

[Delan Azabani (azabani)]

It certainly seems that the extreme width of the nvidia-settings window is causing metacity to crash.

[Delan Azabani (azabani)]

Metacity output:

delan@delan1:~$ metacity --replace
Window manager warning: Log level 16: Native children wider or taller than 65535 pixels are not supported
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Window manager warning: Log level 8: apply_alpha: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Bug in window manager: Unexpected X error: BadAlloc (insufficient resources for operation) serial 19527 error_code 11 request_code 53 minor_code 0)
Aborted

[Delan Azabani (azabani)]

nvidia-settings output:

delan@delan1:~$ nvidia-settings

Gdk-ERROR **: The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 979 error_code 11 request_code 53 minor_code 0)
  (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.)
aborting...
Trace/breakpoint trap

[Fabio Marconi (fabiomarconi)]

I assign to nvidia settings, but actually in 20101225 i cannot reproduce it with a nvidia graphic card gpu6100, window is regular after and before reboot

[Bryce Harrington (bryce)]

"Window manager warning: Log level 16: Native children wider or taller than 65535 pixels are not supported"

From that error message it sounds like a bug in metacity actually.

Please run 'apport-collect 691037'.

[Bryce Harrington (bryce)]

The Gdk-ERROR message in comment #4 is just a standard error that's printed when an X call fails in a gtk program, it doesn't actually provide any diagnostic information.

The one issue that might be particular to nvidia-settings is why the dialog window was so wide to begin with? Did it size itself to that, or was it adjusted to that with manually? I assume the latter but if not, that might be worth investigation as an nvidia-settings bug.

But regardless, metacity shouldn't be crashing in this case. I'll refile against metacity for further analysis.

You might try seeing if you can reproduce the metacity crash with other gtk programs when resized very wide. Also, you should run apport-collect 691037 to add required debug info to the bug report.

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version. Thanks in advance and sorry for the late response.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!