>>>>> "AB" == Anders Boström <[EMAIL PROTECTED]> writes:
AB> nvclock_gtk crashes every time I run it:
AB> eckert:~# nvclock_gtk
AB> The program 'nvclock_gtk' received an X Window System error.
AB> This probably reflects a bug in the program.
AB> The error was 'BadValue (integer parameter out of range for operation)'.
AB> (Details: serial 43 error_code 2 request_code 146 minor_code 3)
AB> (Note to programmers: normally, X errors are reported asynchronously;
AB> that is, you will receive the error a while after causing it.
AB> To debug your program, run it with the --sync command line
AB> option to change this behavior. You can then get a meaningful
AB> backtrace from your debugger if you break on the gdk_x_error()
function.)
AB> eckert:~#
AB> And the instructions don't work. A breakpoint on gdk_x_error never
AB> trigger.
AB> nvclock and nvclock_qt works fine. I've got an Geforce 256 DDR and
AB> use the legacy driver, version 1.0.7184-3. I use fvwm 2.5.18-2 as
AB> window-manager.
I found the problem:
I had an old auto-created .nvclock/config, making nvclock_gtk crash.
I have never edited .nvclock/config. This means that nvclock_gtk can't
even manage it's own old auto-created config-file. The config-file
making nvclock_gtk crash is attached.
/ Anders
#This is NVClock's config file. Don't edit the hw and general section!
general.cards=1
gtk.save_opengl_changes=1
gtk.show_tooltips=1
gtk.use_lowlevel_backend=0
hw0.basefreq=14318
hw0.card=257
hw0.mpll=5377
hw0.nvpll=125965
opengl.aniso=0
opengl.aniso_app_controlled=1
opengl.cpu=0
opengl.flipping=1
opengl.fsaa=0
opengl.fsaa_app_controlled=1
opengl.texclamping=0
opengl.texsharpen=0
opengl.vsync=0
