Bug 133669 - Cant remove shortcut in KDE 3.2
Summary: Cant remove shortcut in KDE 3.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdeadmin
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-25 23:58 UTC by sverrejon john
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-19 15:09:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description sverrejon john 2004-09-25 23:58:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera 
7.54  [en]

Description of problem:
i can't turn of the shortcut i added with a mistake. It is on command 
shortcuts. The shortcut is a end everytime i push a the konqueror 
pops up.
The character "a" doesn't work so i hve to copy/paste evry a i write.
..
I hve tried to push default and remove the shortcut, but it doesn't 
work. If i remove it and restart the computer the a doesn't work and 
the konqueror doesn't popup...

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


How reproducible:
Always

Steps to Reproduce:
1. i push the character "a"
2. the konqueror pops up
3. the character "a" doesn't work.
    

Actual Results:  konqueror pops up. And "a" doens't work,-

Expected Results:  The character "a" should come.

Additional info:

Comment 1 Matthew Miller 2005-04-26 15:18:41 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 Than Ngo 2005-07-19 15:09:40 UTC
i cannot reproduce this problem with KDE-3.4.x in FC4 release anymore.



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