Bug 485610 - crash and/or skip special characters on auto-typing
Summary: crash and/or skip special characters on auto-typing
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: keepassx
Version: 10
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL: http://www.keepassx.org/changelog
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-15 09:48 UTC by bee
Modified: 2009-03-05 16:28 UTC (History)
1 user (show)

Fixed In Version: 0.3.4-1.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-05 16:28:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description bee 2009-02-15 09:48:56 UTC
Description of problem:
crash and/or skip special characters on auto-typing.

Version-Release number of selected component (if applicable):
Keepassx 0.3.3 (2008-08-11)

How reproducible:
Run the auto-typing with an email address as username (like "honey").


Steps to Reproduce:
1. Username: set any email address (because "@" is a special char)
2. Ctrl+V (auto-typing)
3. it'll skip to type "@" or crash


Expected results:
to work properly!!!!! 
that was simple!!!


Additional info:
http://www.keepassx.org/changelog
0.3.4 (2008-11-09)
    * fixed crash when auto-typing special characters (Bug #2111588)
    * only allow plain text in comment 


**************************
**************************
**************************
IF YOU UPDATE THE RPM TO THE LAST VERSION OF KEEPASSX, IT'LL BE SOLVED!! (looks like!!)
**************************
**************************
**************************

Comment 1 Aurelien Bompard 2009-02-16 07:18:14 UTC
For some reason I wasn't notified of the new release of KeepassX.
I'll update it ASAP. Thanks for reporting.

Comment 2 Fedora Update System 2009-03-05 16:28:16 UTC
keepassx-0.3.4-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


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