Your message dated Fri, 08 May 2020 13:12:01 +0800
with message-id <0ea239623b45aed21f226ed98d544...@debian.org>
and subject line Re: Bug#959946: grace: fails to start: failed request: 12
(X_ConfigureWindow)
has caused the Debian Bug report #959946,
regarding grace: fails to start: failed request: 12 (X_ConfigureWindow)
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 ow...@bugs.debian.org
immediately.)
--
959946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grace
Version: 1:5.1.25-8
Severity: grave
Justification: renders package unusable
On a clean installation, grace fails to launch:
$ xmgrace
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 12 (X_ConfigureWindow)
Value in failed request: 0x0
Serial number of failed request: 2821
Current serial number in output stream: 2822
This happens both with the latest official build from the archive and
with a fresh local rebuild.
backtrace from gdb adds a reference to libthread_db.so:
Starting program: /usr/bin/xmgrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
X Error of failed request: BadValue (integer parameter out of range for
operation)
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages grace depends on:
ii fontconfig 2.13.1-4
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4
ii libc6 2.30-7
ii libfftw3-double3 3.3.8-2
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libnetcdf18 1:4.7.4-1
ii libpng16-16 1.6.37-2
ii libx11-6 2:1.6.9-2+b1
ii libxbae4m 4.60.4-7+b11
ii libxm4 2.3.8-2
ii libxmhtml1.1 1.1.10-3
ii libxmu6 2:1.1.2-2+b3
ii libxpm4 1:3.5.12-1
ii libxt6 1:1.1.5-1+b3
ii xterm 356-1
Versions of packages grace recommends:
ii xfonts-100dpi 1:1.0.4+nmu1
ii xfonts-75dpi 1:1.0.4+nmu1
Versions of packages grace suggests:
ii gconf2 3.2.6-6
ii ghostscript 9.52~dfsg-1
pn texlive-extra-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2020-05-08 04:38, Nicholas Breen wrote:
I cannot reproduce this on any of three systems. If you have a
residual
/etc/X11/app-defaults/XMgrace, can you try removing it?
It's a fresh installation, there's no /etc/X11/app-defaults/XMgrace
Can you
generate a log with xtrace?
Hmm, actually xtrace isn't working either...time for a reboot.
...
After the reboot, xmgrace is now launching fine. Still don't know what
the problem was, but it's gone now, so I'll close this bug.
Strangely, xtrace is still not working:
$ xtrace xmgrace
No display name to create specified, trying :9
Error parsing xauth list data: less than three things in a line!
Says it can't find a display, even though DISPLAY is defined. I suspect
it might be a problem with Wayland, which is now used by default in
fresh installations with Gnome.
Anyway, xmgrace is now working. Can worry about xtrace elsewhere.
Thanks for checking for the bug.
Drew
--- End Message ---
