Bug 1615047 - Backspace Key Inoperable After Ctrl+V
Summary: Backspace Key Inoperable After Ctrl+V
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnucash
Version: 30
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-11 18:53 UTC by Bryan Mason
Modified: 2020-05-26 14:39 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:39:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Proposed Patch (1.55 KB, patch)
2018-08-11 18:53 UTC, Bryan Mason
no flags Details | Diff

Description Bryan Mason 2018-08-11 18:53:37 UTC
Created attachment 1475249 [details]
Proposed Patch

Description of problem:

  After using cut/copy/paste (Ctl-X/Ctl-C/Ctl-V on an account ledger field,
  the Backspace and Delete keys no longer work (pressing them does
  nothing.

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

  gnucash-3.2-1.fc28

How reproducible:

  100%

Steps to Reproduce:

  1. Open any account ledger
  2. Click on the description field for a new transaction.
  3. Type something
  4. Press Ctl-A/Ctl-X to cut the something you just typed.
  5. Type something else.
  6. Press Backspace to remove what you typed.

Actual results:

  Nothing happens when you press Backspace

Expected results:

  Letters should be removed when you press Backspace

Additional info:

Reported upstream:
https://bugs.gnucash.org/show_bug.cgi?id=796665

Fixed upstream:
https://github.com/Gnucash/gnucash/commit/6011749151793399727371db335a0e3dd9723d81#diff-ed07adb31752b07d14f78a8366e02406

Attaching patch from upstream fix.  I verified that the patch resolves the issue when added to current Fedora 28 gnucash (gnucash-3.2.1-1.fc28).  I will continue testing and will report any issues with the patch.

Comment 1 Ben Cotton 2019-05-02 19:22:43 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 2 Ben Cotton 2019-05-02 20:15:53 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 3 Ben Cotton 2019-05-28 23:20:36 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
bug.

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

Comment 4 Yann Soubeyrand 2019-05-29 13:19:43 UTC
Hi,

This bug is still present in Fedora 30. However I cannot change the affected version of this bug report.

Regards

Comment 5 Ben Cotton 2020-04-30 21:53:49 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.

Comment 6 Kevin L. Mitchell 2020-04-30 22:21:37 UTC
This bug appears to be corrected in Fedora 31 as of today.

Comment 7 Ben Cotton 2020-05-26 14:39:05 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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
bug.

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


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