Bug 910158

Summary:	Reassigning same key sequence to key shortcut results in shortcut being removed
Product:	[Fedora] Fedora	Reporter:	Maciek Borzecki <maciek.borzecki>
Component:	xfce4-settings	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	admiller, kevin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 23:02:06 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:

Description Maciek Borzecki 2013-02-11 22:34:01 UTC

Description of problem:
In key shortcut dialog, when I click in the 'shortcut' column for particular entry, and assign the same key sequence as this entry already has, the entry will be removed.

Version-Release number of selected component (if applicable):
xfce4-settings-4.10.0-4.fc18.x86_64


How reproducible:
always

Steps to Reproduce:
1. add entry that runs program Terminal and assign shortcut Ctrl+t
2. once entry is added, click in the shortcut column to change it's key sequence
3. enter the same he sequence as before (Ctrl+t)
4. observe that the entry has been removed from the list
  
Actual results:
entry is removed from the list of assigned key shortcuts

Expected results:
entry remains in the list, key sequence is updated (effectively unchanged)

Additional info:

Comment 1 Kevin Fenzi 2013-02-13 00:28:17 UTC

I can confirm this here too. ;( 

Would you like to report it upstream? Or would you like me to?

Comment 2 Maciek Borzecki 2013-11-13 09:12:47 UTC

Fixed upstream, might already be fixed in Fedora too.

Comment 3 Kevin Fenzi 2013-11-13 16:41:55 UTC

Yeah, sounds like that should be in 4.10.0... 

Can you check and see if you can reproduce it now?

Comment 4 Fedora End Of Life 2013-12-21 15:22:16 UTC

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

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 5 Fedora End Of Life 2014-02-05 23:02:06 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.