[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#639670: marked as done (bluedevil: Manual Pin option in the add device wizard does not work)

Your message dated Tue, 6 Jun 2017 16:42:51 +0200
with message-id <20170606144240.rkpnxlug42tzk3u3@neoptolemo.gnuservers.com.ar>
and subject line Re: Bug#639670: bluedevil: Manual Pin option in the add device wizard does not work
has caused the Debian Bug report #639670,
regarding bluedevil: Manual Pin option in the add device wizard does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
639670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639670
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: bluedevil
Version: 1.1-1
Severity: normal


Some bluetooth devices without keyboards have a hardcoded pin code on them used for pairing. (The device I'm testing with has a hardcoded code of 1234)

For such a device you are supposed to manually set a pin while pairing to match the one hardcoded into the device.

However when clicking 'Add Device...' in the kde bluetooth wizard and ticking Manual PIN: and setting the pin to 1234 on the next step in the wizard I'm instead presented with a randomly generated pin number (just like I'd get if I'd not ticked the Manual PIN option).   From what I can see in my testing the 'Manual PIN:' option has no effect at all on how the wizard functions.    

It looks like upstream have looked at this (https://bugs.kde.org/show_bug.cgi?id=277878) but I'm not seeing a working patch there currently based on the reporters feedback in that bug report.    


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages bluedevil depends on:
ii  bluez                         4.96-1     Bluetooth tools and daemons
ii  kdebase-runtime               4:4.6.5-1  runtime components from the offici
ii  libbluedevil1                 1.9-1      A Qt wrapper for bluez
ii  libc6                         2.13-18    Embedded GNU C Library: Shared lib
ii  libgcc1                       1:4.6.1-8  GCC support library
ii  libkdecore5                   4:4.6.5-2  KDE Platform Core Library
ii  libkdeui5                     4:4.6.5-2  KDE Platform User Interface Librar
ii  libkfile4                     4:4.6.5-2  File Selection Dialog Library for 
ii  libkio5                       4:4.6.5-2  Network-enabled File Management Li
ii  libqt4-dbus                   4:4.7.3-7  Qt 4 D-Bus module
ii  libqtcore4                    4:4.7.3-7  Qt 4 core module
ii  libqtgui4                     4:4.7.3-7  Qt 4 GUI module
ii  libstdc++6                    4.6.1-8    GNU Standard C++ Library v3
ii  obex-data-server              0.4.5-1+b2 D-Bus service for OBEX client and 
ii  obexd-client                  0.42-1     D-Bus OBEX client

bluedevil recommends no packages.

Versions of packages bluedevil suggests:
pn  pulseaudio-module-bluetooth | <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1.2.3-1

¡Hola Jason!

El 2011-08-29 a las 21:47 +1200, Jason Alasola escribió:
Some bluetooth devices without keyboards have a hardcoded pin code on them used for pairing. (The device I'm testing with has a hardcoded code of 1234)
For such a device you are supposed to manually set a pin while pairing to match the one hardcoded into the device.
However when clicking 'Add Device...' in the kde bluetooth wizard and ticking Manual PIN: and setting the pin to 1234 on the next step in the wizard I'm instead presented with a randomly generated pin number (just like I'd get if I'd not ticked the Manual PIN option). From what I can see in my testing the 'Manual PIN:' option has no effect at all on how the wizard functions.
It looks like upstream have looked at this (https://bugs.kde.org/show_bug.cgi?id=277878) but I'm not seeing a working patch there currently based on the reporters feedback in that bug report.
The upstream fix was released with the 1.1.1, I'm closing the issue with the version currently in oldstable. 

Happy hacking,
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: