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.

Description of problem:

Screenshot and screencast contain ':' which is invalid character on vfat. That means that file has to be renamed manually to get better compatibility for non-linux users.

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

How reproducible:

Always.


Steps to Reproduce:
1. Create a screenshot or screencast.

Actual results:

File name contain ':', which is invalid character on other filesystems (vfat) and for that reason it cannot be attached to some tools, such as JIRA

Expected results:

File name does not contain ':'. Or pattern is not hardcoded but can be modified externally via dconf/tweek tool.


Additional info:
https://bugzilla.gnome.org/show_bug.cgi?id=698740
https://issues.jboss.org/browse/ORG-2091


Upstream Gnome is not able to fix this issue for a long time. Is there a chance that we could fix that in RHEL? Or can we kindly ask upstream to force it?

Still happens on gnome-screenshot-3.14.0-1.el7.x86_64, fixed later on in https://git.gnome.org/browse/gnome-screenshot/commit/?id=51485cf6bf8a8794150be0b8dff61fd573ae1512

Verified on gnome-settings-daemon-3.14.4-7.el7.x86_64 and gnome-screenshot-3.14.0-2.el7.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2215.html