When reconnecting a bluetooth keyboard to a different computer (already paired with the keyboard) then the computer prompts for a PIN to be entered on the computer for subsequent entry on the bluetooth keyboard. The field into which to enter the PIN on the computer is blank. If the field is clicked then the field is filled with 8 spaces. Why must the user enter the PIN first on the computer and then on the keyboard when reconnecting instead of just having the computer display a (readonly) PIN to enter on the keyboard - as it does when pairing? Alternatively, why is the field blank instead of showing a suggested PIN as default - or was that the intention with click in the field except it is filled with 8 spaces rather than a real number? Also, when the window prompting for introduction of the PIN is displayed then also the temporarily displayed connection confirmation window is prematurely shown and on top of the PIN prompting window mostly hiding it. Also, the PIN prompting window is dismissed after the necessary click on OK but should stay up for reference until the PIN has been entered on the keyboard in order not to leave the user to have to remember the PIN - again as is the case when pairing. Also, when OK is clicked in the PIN prompting window after clicking in the field thereby filling it with 8 spaces then a window appears titled "A Problem has Occurred" with the body text "A problem in the bluedevil-1.3-0.5.rc2.fc17 package has been detected". Reproducible: Always Steps to Reproduce: requirements are 2 computers and a keyboard all supporting bluetooth. 1. pair (and connect) the keyboard with computer no. 1 2. pair (and connect) the keyboard with computer no. 2 3. reconnect the keyboard with computer no. 1 as follows - press the bluetooth button on the keyboard. its bluetooth light starts blinking. - click connect for the keyboard in the bluetooth menu in the tray. two windows appear "KDE Workspace" and "BlueDevil" with the former partly hiding the latter. - select the "BlueDevil" window (or wait for the "KDE Workspace" window to disappear). "BlueDevil" appears in front. - click "Introduce PIN" in the "BlueDevil" window. Window "BlueDevil" disappears and window "Introduce PIN" appears with a blank PIN entry field. - click in the PIN field. The PIN field is filled with 8 spaces. - click OK (or press Enter). Window "Introduce PIN" disappears and Window "A Problem has Occurred" appears.
Sorry for the delay replying here. I can confirm the 8 spaces bug, will try to fix. For the rest, I will need to reproduce this and see exactly what needs to be improved.
Can you attach the output of bluedevil-wizard when pairing this device? Also, the output of kded4 will be nice. I can't reproduce this with the bluetooth keyboard I use for testing :/
I dont know how to go about getting output from kded4 (can it be stopped and started from konsole?) but here's the output from bluedevil-wizard. I started all over as follows: click "Configure Bluetooth" in tray. Window "Configure - KDE Control Module" opens. click keyboard in list in window. Keyboard highlights. click "Remove". Confirmation popup opens. click "Yes" in confirmation popup. Confirmation popup closes and keyboard disappears from list. click "Ok". Window closes. turn on BT keyboard and press the BT keyboards bluetooth button. launch bluedevil-wizard from konsole. Window "Bluetooth Device Wizard" opens listing the keyboard. click on BT keyboard in list in window. Keyboard highlights. click "Next". Window changes to listing a 6 digit PIN. enter PIN on BT keyboard. Message "Error response: "Authentication Canceled"" shows in konsole before entry of all digits of the PIN is finished. It appears that there is an expiration timer on entry of the PIN, that the error message displays on expiration and that expiration is approx 8 secs. 8 secs is far too little. Why so tight? The way I enter such PINs on my little fiddly portable BT keyboard is that I read a digit and enter that, read the next digit and enter that, etc. And that takes time. The other thing is that the user gets no notification on error and therefore has no clue as to what happened. On Sun, Mar 10, 2013 at 7:59 PM, Alex Fiestas <afiestas@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=304945 > > Alex Fiestas <afiestas@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|CONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Alex Fiestas <afiestas@kde.org> --- > Can you attach the output of bluedevil-wizard when pairing this device? > > Also, the output of kded4 will be nice. > > I can't reproduce this with the bluetooth keyboard I use for testing :/ > > -- > You are receiving this mail because: > You reported the bug. >
I see that kded4 has .xession-errors open so here's the increment in that file from when "Next" is clicked until the error message shows [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31muint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu [31mQMenu* DBusMenuImporterPrivate::menuForId(int) const[0m: Condition failed: action [31mvoid DBusMenuImporter::GetLayoutCallback(int, QDBusPendingCallWatcher*)[0m: Condition failed: menu On Mon, Mar 11, 2013 at 11:58 AM, Claus Olesen <ceolesen@gmail.com> wrote: > I dont know how to go about getting output from kded4 (can it be stopped > and started from konsole?) but here's the output from bluedevil-wizard. > > I started all over as follows: > > click "Configure Bluetooth" in tray. Window "Configure - KDE Control > Module" opens. > click keyboard in list in window. Keyboard highlights. > click "Remove". Confirmation popup opens. > click "Yes" in confirmation popup. Confirmation popup closes and keyboard > disappears from list. > click "Ok". Window closes. > > turn on BT keyboard and press the BT keyboards bluetooth button. > > launch bluedevil-wizard from konsole. Window "Bluetooth Device Wizard" > opens listing the keyboard. > click on BT keyboard in list in window. Keyboard highlights. > click "Next". Window changes to listing a 6 digit PIN. > enter PIN on BT keyboard. Message "Error response: "Authentication > Canceled"" shows in konsole before entry of all digits of the PIN is > finished. > > It appears that there is an expiration timer on entry of the PIN, that the > error message displays on expiration and that expiration is approx 8 secs. > 8 secs is far too little. Why so tight? The way I enter such PINs on my > little fiddly portable BT keyboard is that I read a digit and enter that, > read the next digit and enter that, etc. And that takes time. The other > thing is that the user gets no notification on error and therefore has no > clue as to what happened. > > > > > On Sun, Mar 10, 2013 at 7:59 PM, Alex Fiestas <afiestas@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=304945 >> >> Alex Fiestas <afiestas@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Status|CONFIRMED |NEEDSINFO >> Resolution|--- |WAITINGFORINFO >> >> --- Comment #2 from Alex Fiestas <afiestas@kde.org> --- >> Can you attach the output of bluedevil-wizard when pairing this device? >> >> Also, the output of kded4 will be nice. >> >> I can't reproduce this with the bluetooth keyboard I use for testing :/ >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > >
Hi, is this bug still happening? If so, can you: 1-Execute kdebugdialog and enable bluedevil wizard 2-Execute bluedevil-wizard in a terminal 3-Copy paste the output here. Thanks and sorry for the delay replying.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!