Comment 22 for bug 1634802

I installed the fix from zesty, and it loads into the kernal fine, and I can set the resolution that I want.

However...

Since before now I could not get nvidia-304 to work, I had been using nouveau.
I had been able to start the panorama program Hugin, but when I tried to open the images to stitch together, the graphics driver nouveau crashed and I had to do a hard-shutdown.

Now that I have a working nvidia-304, Hugin crashes with some sort of a x-window error when it tries to start up.

"
The program 'hugin' 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 541 error_code 2 request_code 154 minor_code 24)
  (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.)
"

I don't know if it is the mere presence of nvidia-304, or THIS PARTICULAR
nvidia-304. I don't know if it is the FIX that caused it, or something else.
I can see that the version of nvidia-304 that I had been using under Lubuntu
16.04 (and which I used with Hugin with no problem) was 304.131xxx instead of
.132.

From this output, can anyone say if it is a bug in nvidia-304, or Hugin that is
the problem?

Say...

I see that there is a .131 for Xenial Xerus. at the same site I got the fixed .132 ...
Does anyone think there is likely to be a problem if I try to load that version of nvidia-304?
I am inclined to try it...