Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1655893 - Shortcut Ctrl + Q has no effect
Summary: Shortcut Ctrl + Q has no effect
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-screenshot
Version: 8.0
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Matthias Clasen
QA Contact: Desktop QE
Depends On: 1417658
Blocks: 1481731
TreeView+ depends on / blocked
Reported: 2018-12-04 08:32 UTC by Michal Odehnal
Modified: 2020-02-24 17:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1417658
Last Closed: 2020-02-24 17:47:52 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-screenshot issues 73 0 None None None 2020-02-07 16:00:50 UTC

Description Michal Odehnal 2018-12-04 08:32:39 UTC
+++ This bug was initially created as a clone of Bug #1417658 +++

Description of problem:
Shortcut Ctrl + Q has no effect.

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

How reproducible:

Steps to Reproduce:
1. Start gnome-screenshot
2. Press key combo <Ctrl><Q>

Actual results:
Application still running.

Expected results:
Application quits.

Additional info:

--- Additional comment from Fedora End Of Life on 2017-11-16 13:48:32 EST ---

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

--- Additional comment from Fedora End Of Life on 2017-12-12 05:36:28 EST ---

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

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

Comment 2 Matthias Clasen 2020-02-24 17:47:52 UTC
we didn't get around to this

Note You need to log in before you can comment on or make changes to this bug.