Hi Roland (and anyone else who cares to partake of this discussion!)
I've noticed a problem with LDCad (1.6d) and the latest graphics card drivers that my system updates manager wants me to install.
After upgrading my nvidia drivers from 390.116-0ubuntu0.18.04.3 to 390.132-0ubuntu0.18.04.1, I find that LDCad won't start. Running it in my terminal, I get the following error message:
I am almost certain this message was produced by some software other than LDCad, perhaps something in the desktop management stack. Certainly adding the --sync flag didn't change anything.
I've had a look at LDCad's logfiles, and can't see anything immediately wrong. It goes through setting up the color bins etc, and then just stops. The last line in the logfile is:
When it's working, the next logfile lines are all about setting up the rendering engine, which would be problematic if there's some incompatibility with the graphics card driver.
It's no real difficulty to roll back to the old version of the driver (fortunately, it was only a day or so ago that I installed these updates - it's possible that I could have gone for quite some time before noticing the problem), but I wondered if you had any thoughts as to what might be the root cause.
In short, I'm not really expecting you to fix my problem, but if, as the message suggests, there's a bug in LDCad, I figured you ought to know!
I hope you're keeping well in these interesting times.
Owen.
I've noticed a problem with LDCad (1.6d) and the latest graphics card drivers that my system updates manager wants me to install.
After upgrading my nvidia drivers from 390.116-0ubuntu0.18.04.3 to 390.132-0ubuntu0.18.04.1, I find that LDCad won't start. Running it in my terminal, I get the following error message:
Code:
$ /usr/bin/LDCad
The program 'LDCad' 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 459 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've had a look at LDCad's logfiles, and can't see anything immediately wrong. It goes through setting up the color bins etc, and then just stops. The last line in the logfile is:
Code:
00257 | 2020-05-10_15:01:09 | Progress | Validating inventories. | done.It's no real difficulty to roll back to the old version of the driver (fortunately, it was only a day or so ago that I installed these updates - it's possible that I could have gone for quite some time before noticing the problem), but I wondered if you had any thoughts as to what might be the root cause.
In short, I'm not really expecting you to fix my problem, but if, as the message suggests, there's a bug in LDCad, I figured you ought to know!
I hope you're keeping well in these interesting times.
Owen.