Package: goban-ss
Version: 1.1-2
Severity: normal
Tags: patch
After adding to .xscreensaver programs:
goban -root \n\
Running xscreensaver-demo and selecting the Goban entry, the demo window
at the right is all black and an error is printed to the initiating tty,
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 14 (X_GetGeometry)
Resource id in failed request: 0x0
Serial number of failed request: 2842
Current serial number in output stream: 2842
where I hoped it would show a small sample of the goban-ss.
I believe xscreensaver runs a saver program with a window-id such as
-window-id 0xE00465
It works for me to change the debian/patches/decimal-wid.patch to "%i"
to cope with either decimal or hex. In cgoban.c
/* Debian: xscreensaver circa 5.15 passes "-window-id 0xFFFF".
Use sscanf %i to accept either 0x hex or decimal. */
sscanf(clp_getStr(cg->clp, "window-id"), "%i", &wid);
and also it seems similar in goban.c
/* Debian: xscreensaver circa 5.15 passes "-window-id 0xFFFF".
Use sscanf %i to accept either 0x hex or decimal. */
sscanf(clp_getStr(cg->clp, "window-id"), "%i", &g->win->window_id);
I couldn't tell precisely which one is used under which conditions. It
seems they both might be. In any case changing both places seems to
work, as for instance can be exercised by running with a -window-id
which is the root window
/usr/lib/xscreensaver/goban -window-id 0x65
/usr/lib/xscreensaver/goban -window-id 101
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages goban-ss depends on:
ii libc6 2.13-10
ii libx11-6 2:1.5.0-1
Versions of packages goban-ss recommends:
ii goban-original-games 1.1-2
ii xscreensaver 5.15-2
goban-ss suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
