Cannot do screen capture of xclock window

[ishields]

Binary package hint: x11-apps

Something seems wrong with the window ids of xclock windows. I can use xwininfo to get the id of the frame window and also that of the window displaying the clock. If I use import (from ImageMagick) to capture an image, I can capture the interior using the window id, but if I use the window id of the frame I get a message that says:
$ import -frame -window 0x1281608 xc1.png
import: unable to read X window image `0x1281608': Resource temporarily unavailable @ magick/xwindow.c/XImportImage/4965.

Furthermore, if the clock is on the desktop and I capture the whole desktop using -window root option of import, I get the clock showing with the frame. However, If I open a terminal window and prefix the import command (with -window root) with a sleep 5, so I can drag the xclock over the terminal window, then the resulting image shows only the interior of the xclock over the terminal window. If the xclock window is only partially covering the terminal window, and partially covering the desktop, then the image shows a frame only around the part over the desktop and only the interior for the part over the terminal window.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/xclock
NonfreeKernelModules: fglrx
Package: x11-apps 7.3+4
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: x11-apps
Uname: Linux 2.6.28-16-generic x86_64
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: LENOVO 8810AA1
Package: fglrx-installer (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=4f831ebd-b1c6-461e-8583-5e7354551150 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:

dmi.bios.date: 12/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT49AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.asset.tag: �����������������������
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: dmi:bvnLENOVO:bvr2JKT49AUS:bd12/12/2008:svnLENOVO:pn8810AA1:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.name: 8810AA1
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: LENOVO 8810AA1
Package: fglrx-installer (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=4f831ebd-b1c6-461e-8583-5e7354551150 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:

dmi.bios.date: 12/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT49AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.asset.tag: �����������������������
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: dmi:bvnLENOVO:bvr2JKT49AUS:bd12/12/2008:svnLENOVO:pn8810AA1:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.name: 8810AA1
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: LENOVO 8810AA1
Package: fglrx-installer (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=4f831ebd-b1c6-461e-8583-5e7354551150 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:

dmi.bios.date: 12/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT49AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.asset.tag: �����������������������
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: dmi:bvnLENOVO:bvr2JKT49AUS:bd12/12/2008:svnLENOVO:pn8810AA1:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.name: 8810AA1
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

[Bryce Harrington (bryce)]

Hi ianshields,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[ishields (ianshields)]

/var/log/Xorg.0.log goes back several days prior to the problem. Processes were started on Oct 29. Note log contains frequent messages related to XINPUT as I use a KVM switch and a USB mouse and keyboard. Let me know if you need me to narrow down the log at all. Also if you need any other diagnostics.

Ian.

[ishields (ianshields)]

Do you need additional information?

[Timo Aaltonen (tjaalton)]

Works just fine on 9.04 (nvidia) and 10.04alpha (intel). Maybe some driver option would help?

[Ian (ian-redhat-bugs)]

Created attachment 379140
Incorrect title bar colors with zorder of xclock(top) then gedit then terminal.

Description of problem:

xclock title bar does not change to reflect that xclock window has focus. Using default Fedora 12 setup, title bar should change to blue, but stays off-white/light gray when desktop effects = Compiz is enabled. Not a problem if desktop effects = standard.

Version-Release number of selected component (if applicable):

System AMD X86-64 with Radeon HD3450 graphics using mesa-dri-drivers-experimental-7.6-0.13.fc12.x86_64 and xorg-x11-apps-7.4-8.fc12.x86_64
Linux attic4 2.6.31.6-166.fc12.x86_64 #1 SMP Wed Dec 9 10:46:22 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

Install mesa-dri-drivers-experimental-7.6-0.13.fc12.x86_64
Run xclock
Click on title bar of xclock

Actual results:
Title bar does not hcange color.

Expected results:
Title bar should change to blue (or whatever is appropriate to current theme)

Additional info:

Note the attached screenshot. Even though xclock has been dragged over gedit, alt-print-screen geenrates a file name for the saved screen image as if gedit still has focus. Note also that gedit still has the blue title bar.

[ishields (ianshields)]

I've now seen this bug on Fedora 12 as well. It is not a problem unless desktop effects are enabled. Without desktop effects, running xwininfo and clicking on the title bard gives the same window id as it does if you click ont he clock face. With desktop effects enabled you get two different window ids.I'm attaching two screen shots, both taken using commands like
xwd -screen | convert - xxx.png
xclock-face.png is the image captured by clicking only in the face of hte clock. xclock-title.png is the additional image area that is captured if the click is done in the title bar.

Looks to me like the problem may be in compiz-fusion or similar component rather than in the underlying graphics driver.

[ishields (ianshields)]

And here's xclock-title.png

[Ian (ian-redhat-bugs)]

I had previously reported a related bug against Ubuntu 9.10. On further analysis, I believe the underlying cause is probably the same. The other report is at https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/464031

[Matěj (matj-redhat-bugs)]

Colors of windows is a matter of the window manager. Reassigning to compiz.

[ishields (ianshields)]

Any progress on this?

[ishields (ianshields)]

Just checking on this bug on Karmic (9.10). The problem is not just related to xclock, but seems to occur on windows for lots of programs, including a terminal window and a zenity dialog window. I've found some even more weird behaviour today just using terminal windows. The attachment root-win-marked.png is a picture of my entire desktop with three terminal windows marked as A, B and C, along with some other open windows. I attempted to capture screen shots of window B using commands entered in window A as shown (and annotated below). The sleep commands give me enough time to alt-tab to give B focus after entering the command in A.

ian@attic4:~$ # try capture using import by clicking on title area of B
ian@attic4:~$ sleep 3; import -frame import1.png
import: unable to read X window image `': Resource temporarily unavailable @ xwindow.c/XImportImage/4979.
ian@attic4:~$ # Now try by using convert and clicking in middle of window
ian@attic4:~$ sleep 3; import -frame import1.png
ian@attic4:~$ #That worked but import1.png does not include window frame
ian@attic4:~$
ian@attic4:~$ # Now try using xwd and click on title area
ian@attic4:~$ sleep 3; xwd | convert - xwd-loca-1.png
ian@attic4:~$ # Repeat using xwd and click in middle of window
ian@attic4:~$ sleep 3; xwd | convert - xwd-loca-2.png
ian@attic4:~$ # Now move B so it is over A but not entirely over C
ian@attic4:~$ # Use xwd and click on title
ian@attic4:~$ sleep 3; xwd | convert - xwd-locb-1.png
ian@attic4:~$ # Now move B so it is over both A and C
ian@attic4:~$ # Use xwd and click on title
ian@attic4:~$ sleep 3; xwd | convert - xwd-locc-1.png

Using import and clicking on title bar failed as previously reported.
Using import and clicking in interior of window captures interior but no frame, even though -frame option was specified. (import1.png)
Using xwd and clicking on title bar captures frame area, but it is corrupted. The title area shows part of the command being executed in Window A and the frame edge is corrupted by text from Window C (xwd-loca-1.png)
Using xwd and clicking on the interior of the window is similar to using convert in the same way - no frame at all (xwd-loca-2.png)
Next I ran a command in B and then moved it so the title is entirely over A. All of the captured area that shoudl be title is now from A and the only part of the frame that is not corrupted is that part not over either A or C (although it is over another window) (xwd-locb-1.png)
Finally, I moved B so it is entirely over both A and C. Add the -screen option to xwd to capture anything that should be over the window being captured. Again, the title bar of B is entirely over A. Give focus to C, then give focus to A and enter command, then alt-tab to give focus to B. Now what should be the title area of B is actually from A and what should be the interior of B is actually from C. (xwd-locc-1.png).

This is definitely not working in any reasonable way.

[ishields (ianshields)]

BTW, what does status "incomplete" mean? Do I need to provide additional information? And should this still be assigned to fglrx-installer rather than possibly compiz?

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi ishields,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 464031

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 464031 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/464031

[ishields (ianshields)]

I am the original reporter. On a quick check on another systme, I believe the problem still exists. Will download 10.04 and try it out. May take a few days to get everything done.

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

apport information

[ishields (ianshields)]

I still have the problem on Lucid, even on a system which has Intel GMA and does not have fglrx-installer installed.
$ dpkg -l "fglrx*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-========================-========================-================================================================
ii fglrx-modaliases 2:8.723.1-0ubuntu3 Identifiers supported by the ATI graphics driver

The apport-collect command fails:
$ sudo apport-collect 464031
/usr/share/apport/apport-gtk:178: PangoWarning: Invalid UTF-8 string passed to pango_layout_set_text()
  response = self.w('dialog_bugreport').run()

One simple illustration of at least one aspect of the problem is to use alt-f2 to take a screen shot of a terminal window. According to the setting for System->Preferences->Appearance->Visual effects, you get an image that includes the frame if 'None' is selected and an image that does not include the frame is either 'Normal" or "Extra" is selected.

$ identify shot-none.png shot-normal.png shot-extra.png
shot-none.png PNG 660x469 660x469+0+0 8-bit DirectClass 12.4KiB 0.010u 0:00.009
shot-normal.png[1] PNG 658x437 658x437+0+0 8-bit DirectClass 29.3KiB 0.000u 0:00.010
shot-extra.png[2] PNG 658x437 658x437+0+0 8-bit DirectClass 28.7KiB 0.010u 0:00.009

I've attached the three screen shots as alt-print-screen-shots.zip. Please advise how to overcom the apport-collect bug so I can get the other information you need.

[ishields (ianshields)]

Sorry. Looks like most of the files that apport-collect was trying to upload are now uploaded in triplicate. If there's anything missing, let me know. I forgot to mention that, as originally reported, xwininfo still gives two different window ids (depending on whether you click on title bar or interior) when desktop effects is enabled and only one id when desktop effects is disabled. And, as before, the import command fails if you click on the title bar of a window to select it and you have desktop effects enabled.

[ishields (ianshields)]

For the record, I see the same errors still on my AMD system when I install Lucid. If you need any of the logs, let me know.

Despite the title of this bug report, the problem is not restricted to xclock. I think a more accurate characterization of the issue might be:

When desktop effects are enabled screen capture using alt-print screen fails to capture the frame. Programs such as import also fail if they are asked to copy the frame (e.g. by clicking on the title bar) with an error like
ian@attic4:~$ sleep 3; import shot-ff.png
import: unable to read X window image `': Resource temporarily unavailable @ xwindow.c/XImportImage/5020.

xwininfo -children also reports very different results if you click on the title bar of a wind and desktop effects are not enabled vs. the results if you have desktop effects enabled. Two examples for the Firefox window I am using to enter this information.

Without desktop effects:

ian@attic4:~$ xwininfo -children

xwininfo: Please select the window about which you
          would like information by clicking the
          mouse in that window.

xwininfo: Window id: 0x3a000b4 "Bug #464031 in fglrx-installer (Ubuntu): “Cannot do screen capture of xclock window” - Mozilla Firefox"

  Root window id: 0x142 (the root window) (has no name)
  Parent window id: 0x480002f (has no name)
     2 children:
     0x3a00124 (has no name): () 1171x994+0+0 +1+51
     0x3a000b5 (has no name): () 1x1+-1+-1 +0+50

With desktop effects
ian@attic4:~$ xwininfo -children

xwininfo: Please select the window about which you
          would like information by clicking the
          mouse in that window.

xwininfo: Window id: 0x460010e (has no name)

  Root window id: 0x142 (the root window) (has no name)
  Parent window id: 0x142 (the root window) (has no name)
     19 children:
     0x120159e (has no name): () 1x1+0+0 +0+24
     0x120159d (has no name): () 1x1+0+0 +0+24
     0x120159c (has no name): () 1x1+0+0 +0+24
     0x120159b (has no name): () 1x1+0+0 +0+24
     0x120159a (has no name): () 1x1+0+0 +0+24
     0x1201599 (has no name): () 1x1+0+0 +0+24
     0x1201598 (has no name): () 1x1+0+0 +0+24
     0x1201597 (has no name): () 20x20+30+4 +30+28
     0x1201596 (has no name): () 20x20+50+4 +50+28
     0x1201595 (has no name): () 20x20+10+4 +10+28
     0x1201594 (has no name): () 16x20+1157+1006 +1157+1030
     0x1201593 (has no name): () 1141x5+16+1021 +16+1045
     0x1201592 (has no name): () 16x20+0+1006 +0+1030
     0x1201591 (has no name): () 1x964+1172+42 +1172+66
     0x1201590 (has no name): () 1171x1019+1+4 +1+28
     0x120158f (has no name): () 1x964+0+42 +0+66
     0x120158e (has no name): () 16x42+1157+0 +1157+24
     0x120158d (has no name): () 1141x4+16+0 +16+24
     0x120158c (has no name): () 16x42+0+0 +0+24

[ishields (ianshields)]

Any progress on this? Any further information you need?

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Ian (ian-redhat-bugs)]

The bug is reproducible on Fedora 13 with desktop effects enabled on an AMD X86_64 system with Nvidia graphics.

[Bug (bug-redhat-bugs)]

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Ian (ian-redhat-bugs)]

Not sure why this was closed as I reported that it was reproducible in Fedora 13. I expected the version number to be changed as a result of that report.

[Matěj (matj-redhat-bugs)]

(In reply to comment #6)
> Not sure why this was closed as I reported that it was reproducible in Fedora
> 13. I expected the version number to be changed as a result of that report.

I am sorry, I missed that.

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Ian (ian-redhat-bugs)]

This problem still exists on Fedora 14, so should not be automatically closed.

[Bug (bug-redhat-bugs)]

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.