Bug 692821 - Pin editing does not work as expected
Summary: Pin editing does not work as expected
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 10:10 UTC by Vít Ondruch
Modified: 2011-05-18 16:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-18 16:51:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2011-04-01 10:10:30 UTC
Description of problem:
When I tried to enter my own pin, I was not able to delete any character already entered. Later, even when I entered my own pin, the autogenerated pin was shown and requested during pairing. The pin dialog is not well designed and should be replaced by additional step in pairing wizard.


Steps to Reproduce:
(not sure about the exact names, since my home appears in Czech language)
1. Add new device
2. Enter pin
3. Choose "own pin"
4. Try to use "del" or "backspace"
  
Actual results:
Editing doesn't work, only new numbers can be entered.

Expected results:
Pin can be edited.

Comment 1 Bastien Nocera 2011-05-18 16:51:34 UTC
It's been broken for a while:
http://git.gnome.org/browse/gnome-bluetooth/tree/wizard/main.c#n604

It's been broken since 2009 in fact. Fix will be in the next stable and unstable releases of gnome-bluetooth.

commit 68f6c0fdf118a8880f6da41c920f57d488507290
Author: Bastien Nocera <hadess>
Date:   Wed May 18 17:49:34 2011 +0100

    wizard: Fix backspace, tab, etc. not working
    
    In the custom PIN entry. We weren't eating all the events, including
    escape, backspace, etc. instead of just the non-numerical printable
    characters.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=692821


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