https://bugs.kde.org/show_bug.cgi?id=489260
Bug ID: 489260
Summary: Ctrl+Ins generates error message . . . change to
keyboard shortcut not retained
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: i...@shaw.ca
Target Milestone: ---
SUMMARY
KMyMoney KF5
NOTE: I have used KMyMoney in the past in Windows and other versions of Linux .
. . Ctrl+Ins has always been the standard keyboard shortcut for entering a new
transaction into a ledger.
Currently, Ctrl+Ins generates an error message indicating a conflict (same
shortcut assigned as an alternate shortcut for "copy').
Deleting or changing the conflicting alternate shortcut for "copy" will correct
the conflict for the session, but it reverts to the conflict for next session.
Currently running KMyMoney in MX23 Linux
Have experimented using it in Peppermint Linux with the same result.
STEPS TO REPRODUCE
1. Open KMyMoney
2. Open a ledger
3. Input "Ctrl+Ins" to initiate a new entry into the ledger
OBSERVED RESULT
As noted above:
Ctrl+Ins generates an error message indicating a conflict (same shortcut
assigned as an alternate shortcut for "copy').
Deleting or changing the conflicting alternate shortcut for "copy" will correct
the conflict for the session, but it reverts to the conflict for next session.
EXPECTED RESULT
Ctrl+Ins to generate a new field for entering a new transaction in the ledger.
OR:
Corrected Keyboard Shortcut to be retained for subsequent sessions.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/XFCE
ADDITIONAL INFORMATION
If I change the keyboard shortcut for a new entry to "Ctrl+Up" for example, the
new shortcut will be retained for future sessions. I imagine I could use other
combinations (just not "Ctrl+Ins") as a new entry shortcut. However, I am
puzzled as to why the alternate command for "Copy" cannot be eliminated on an
ongoing basis. If this could be done, the traditional function of "Ctrl+Ins"
could be restored.
I see Bug ID 434851 reflects much of what I have noted. However, as I am using
MX23/Xfce, I do not think that it is a Plasma issue as speculated in Bug ID
434851. Therefore, I submit a semi-redundant report with the hope that this
new information will help to resolve the issue.
I have chosen to be on the mailing list for updates. Best wishes on resolving
this.
--
You are receiving this mail because:
You are watching all bug changes.
