Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1613854

Summary: black areas in xwd screenshots
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: xorg-x11-appsAssignee: Ben Crocker <bcrocker>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.6   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-15 07:41:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot taken with xwd with black areas
none
desktop screenshot taken with xwd
none
desktop screenshot taken with gnome-screenshot none

Description Tomas Hudziec 2018-08-08 12:22:25 UTC
Created attachment 1474308 [details]
screenshot taken with xwd with black areas

Description of problem:
When taking screenshot with xwd command line tool, some areas of screenshot are black. Particularly these are: desktop background, gnome panels and shadows/borders around windows.

Version-Release number of selected component (if applicable):
xorg-x11-apps-7.7-7.el7.x86_64

How reproducible:
always except desktop with no windows in non-classic gnome-session

Steps to Reproduce:
1. take screenshot of root window with xwd and display it with xwud:
   $ xwd -root | xwud
   or convert it and save to (png|jpg|gif|...) file (requires ImageMagick):
   $ xwd -root | convert xwd:- filename.(png|jpg|gif|...)

Actual results:
desktop background, gnome panels and shadows/borders around windows are black

Expected results:


Additional info:
Happens when using "import" program for taking screenshot from ImageMagick suite of tools. Not sure, if it internally uses xwd.

Comment 3 Tomas Hudziec 2018-09-06 08:42:34 UTC
Created attachment 1481226 [details]
desktop screenshot taken with xwd

happens also in gnome classic session

Comment 4 Tomas Hudziec 2018-09-06 08:43:49 UTC
Created attachment 1481227 [details]
desktop screenshot taken with gnome-screenshot

screenshot taken with gnome-screenshot is correct

Comment 7 RHEL Program Management 2021-02-15 07:41:21 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.