Your message dated Sun, 6 Jun 2010 11:18:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#413229: nvclock-gtk: The program 'nvclock_gtk'
received an X Window System error.
has caused the Debian Bug report #413229,
regarding nvclock-gtk: The program 'nvclock_gtk' received an X Window System
error.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
413229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413229
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvclock-gtk
Version: 0.8b2-1
Severity: important
nvclock_gtk crashes every time I run it:
eckert:~# nvclock_gtk
The program 'nvclock_gtk' 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 43 error_code 2 request_code 146 minor_code 3)
(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.)
eckert:~#
And the instructions don't work. A breakpoint on gdk_x_error never
trigger.
nvclock and nvclock_qt works fine. I've got an Geforce 256 DDR and
use the legacy driver, version 1.0.7184-3. I use fvwm 2.5.18-2 as
window-manager.
How can I help debugging this?
/ Anders
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (51,
'testing-proposed-updates'), (50, 'unstable'), (40, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.3
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to sv_SE.UTF-8)
Versions of packages nvclock-gtk depends on:
ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra
ii libfontconfig1 2.4.2-1 generic font configuration library
ii libglib2.0-0 2.12.4-2 The GLib library of C routines
ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface
ii libpango1.0-0 1.14.8-5 Layout and rendering of internatio
ii libx11-6 2:1.0.3-5 X11 client-side library
ii libxcursor1 1.1.7-4 X cursor management library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio
ii libxi6 1:1.0.1-4 X11 Input extension library
ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library
ii libxrender1 1:0.9.1-3 X Rendering Extension client libra
nvclock-gtk recommends no packages.
-- debconf information:
* nvclock-gtk/warning:
--- End Message ---
--- Begin Message ---
Version: 0.8b4-1
On Tuesday, 14. August 2007 23:30:25 Anders Boström wrote:
> I found the problem:
>
> I had an old auto-created .nvclock/config, making nvclock_gtk crash.
I can't reproduce the crash with your "buggy" config file and the current
version. Also the changelog for 0.8b4 mentions:
"Fixed NV-CONTROL crash in nvclock_gtk"
so I assume this bug was fixed upstream and I'm closing this report
accordingly.
Andreas
--- End Message ---
