Your message dated Tue, 19 Jan 2021 22:18:25 -0500 with message-id <cab4xwxw2fyr0tjwvqqnn+j6-1r2uh5zdwayczbntoo1h0z+...@mail.gmail.com> and subject line Re: Bug#749567: gkrellm: Crashes with 'BadRRCrtc (invalid Crtc parameter)' X Window System error has caused the Debian Bug report #749567, regarding gkrellm: Crashes under ssh -Y with 'BadRRCrtc (invalid Crtc parameter)' 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.) -- 749567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749567 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gkrellm Version: 2.3.5-6 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Just trying to run gkrellm ... * What exactly did you do (or not do) that was effective (or ineffective)? This is a headless system (serial console only) so I log in using "ssh -Y ...". Then I try to run "gkrellm". * What was the outcome of this action? I always (100% reproducable) get this error message: The program 'gkrellm' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRRCrtc (invalid Crtc parameter)'. (Details: serial 49 error_code 146 request_code 139 minor_code 20) (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.) * What outcome did you expect instead? I'd expect that a window with a display of the statistcs data opens. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 3.14.3-00003-g043fe0d (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gkrellm depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.18-7 ii libcairo2 1.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgnutls-openssl27 3.2.14-1 ii libgnutls26 2.12.23-15 ii libgtk2.0-0 2.24.23-1 ii libice6 2:1.0.8-2 ii libntlm0 1.4-2 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-0 1.36.3-1 ii libsensors4 1:3.3.5-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-2 gkrellm recommends no packages. gkrellm suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Fri, 13 Jun 2014 09:41:36 +0300 Damyan Ivanov <[email protected]> wrote: > Control: severity -1 normal > Control: retitle -1 gkrellm: Crashes under ssh -Y with 'BadRRCrtc (invalid > Crtc parameter)' X Window System error > > -=| Wolfgang Denk, 28.05.2014 08:34:42 +0200 |=- > > Package: gkrellm > > Version: 2.3.5-6 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > * What led up to the situation? > > > > Just trying to run gkrellm ... > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > This is a headless system (serial console only) so I log in using > > "ssh -Y ...". Then I try to run "gkrellm". > > gkrellm works just fine when run locally. Bug retitled and severity adjusted. > > gkrellm updates its window many times per second, so running it via > ssh -X is not such a good idea anyway. I'd run the gkrellmd on the > headless system and then use 'gkrellm -s $host' on the desktop. Damyan provided a solution 6 years ago and OP never followed up, closing
--- End Message ---
