Hello, Martin:
Thank you for logs.
I have not investigated the logs you provided in detail, however:
martin f krafft wrote, at 11/21/2012 11:47 PM +9:00:
also sprach TASAKA Mamoru <mtas...@fedoraproject.org> [2012.10.19.1427 +0200]:
I cannot reproduce this, either, so to debug this issue your help is
really appreciated.
I am sorry, I did not see this e-mail until now.
Can you try below?
* launch xscreensaver like below from a terminal:
$ xscreensaver -verbose -log xscreensaver_output_log
Log file attached.
* Now really gain the window information like
----------------------------------------------------------
$ env DISPLAY=:0.0 xwininfo 0x1e001ad
Attached. Unlike you, I just get "screensaver" as title.
* Then try debugging "xscreensaver-getimage <root id> <root id> with gdb,
with setting break point on XPutImage and _XError, and getting backtrace
when xscreensaver-getimage reaches XPutImage or _XError function like:
Attached a typescript. Is this enough?
xscreensaver_output_log:
xscreensaver: 15:39:31: 0: visual 0x21 (TrueColor, depth: 24, cmap: default)
xscreensaver: 15:39:31: 0: saver window is 0x2e00001.
xscreensaver: 15:39:39: 0: xscreensaver-gl-helper: GL visual is 0x21 (default).
xscreensaver: 15:39:39: 0: visual 0x5e (TrueColor, depth: 32, cmap: 256)
xwininfo:
Depth: 32
xscreensaver.script
(gdb) whatis image
type = XImage *
(gdb) p *image
$1 = {width = 256, height = 64, xoffset = 0, format = 2, data = 0x7ffff7f74010
"", byte_order = 1, bitmap_unit = 32, bitmap_bit_order = 1, bitmap_pad = 32,
depth = 24, <=============== bytes_per_line = 1024, bits_per_pixel = 32,
red_mask = 16711680, green_mask = 65280, blue_mask = 255, obdata = 0x0, f = {
So "depth" mismatches between the "window" and the "image", which is perhaps
causing the issue you see (c.f. man XPutImage and the explanation of when
"BadMatch" error occurs). Need work to handle this...
Regards,
Mamoru
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
