Le jeudi 23 avril 2009 à 08:51 +, teodor_kasap a écrit :
> Hi Mathias
>
> Thanks for the suggestion.
>
> I am only trying to connect my headset to my computer. I was looking for
> a fix and found this forum, I'm not exactly an expert on this...
And as I said, this is not a forum, this is a b
Le jeudi 23 avril 2009 à 02:26 +, teodor_kasap a écrit :
> Small glitch, I need guidance here (ubuntu 8.10 32-bit user)
>
> I have read all the posts here and tried to install the package
> according to the instruction in the installation doc.
>
> when i run the command "./configure" , at the
teodor_kasap [2009-04-23 2:26 -]:
> "configure: error: D-Bus library is required"
Try installing libdbus-1-dev.
--
bluetooth-wizard unable to pair to fixed pin devices
https://bugs.launchpad.net/bugs/284994
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My fixed pin device now works in newest Jaunty release. Holux m1200 :)
On Fri, Mar 20, 2009 at 10:39 AM, GBalage wrote:
> ** Changed in: bluez-gnome (Fedora)
> Status: New => Confirmed
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
>
I think the only change would be to the maximum length (change 4 to 16
with the ... line):
+ hbox_custom = gtk_hbox_new(FALSE, 6);
+ radio_custom =
gtk_radio_button_new_with_label_from_widget(GTK_RADIO_BUTTON(radio_),
_("Custom PIN code:"));
+ entry_custom = gtk_entry_new
Upstream bug, (which is linked in the ubuntu bug) has a patch, but was
not commited.
Bastien commited another patch on gnome-bluetooth (which is a fork of
bluez-gnome), but I'm not sure this is can be integrated as it is in
bluez-gnome.
--
bluetooth-wizard unable to pair to fixed pin devices
http
On mar, 2009-02-10 at 12:01 +, Ed Guenter wrote:
> I could even hear some wav sounds with aplay ... sometimes:
>
> aplay -Dplug:bluetooth /usr/share/sounds/k3b_error1.wav
> Playing WAVE '/usr/share/sounds/k3b_error1.wav' : Unsigned 8 bit, Rate 8000
> Hz, Mono
>
> ==> yes, but one second lat
smertz,
do as the other did, give the output of the following
1) hcitool scan
2) hcitool inq [bluetooth address]
3) The model of your device
thanks
On Thu, Jan 22, 2009 at 2:29 AM, smerz wrote:
> Thank you roberto.
>
> My bluetooth headset (for phone usage) needed pin 1234 instead of
> :-(
Ciao,
Sorry but i am a normal linux user, not a developer or programmer.
I wrote my experience to help anybody to bypass the problem until a fix
is released.
Good look and happy 2009
Daniel Lupulescu ha scritto:
> When do we see a permanent fix for this bug?
>
>
--
bluetooth-wizard unable to
Ciao,
Yes, you have correctly paired the headset, but i can't help how to
use it.
I do not have experience with bluetooth sound device.
Good look
pumber ha scritto:
> I've paired up the headset with my notebook, I believe.(please see the
> picture)
>
> However, how can I ouput the sound
That sounds like a good idea provided:
1. Pincodes are specified to be as long as 16 digits. If you are
going to bother with a random pin, it should be 8 digits by default if
security is not to be just a lesser joke. Apple uses 8. If you have
a PIN entry box, it should allow a max of 16 digits.
CADE20 wrote:
> I modified my patch, I've added a textbox for choosing any pincode.
Please see the upstream dev discussion on how the bluez developer would
solve the issue in a way that seems reasonable:
http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721
Such a patch should be done ac
The problem is many devices use pins other than - I have two that
use and 1234.
My patch pops up a confirmation box. Perhaps you could merge it with
yours so the dialog would pop up only if you checked the box.
On Sat, Nov 22, 2008 at 8:43 AM, CADE20 <[EMAIL PROTECTED]> wrote:
> I've m
To clarify:
Addr | Class | BT hcitool scan name | PIN
00:03:C9:30:97:64 | 0x200404 | BT Headset |
00:06:66:01:45:C3 | 0x001f00 | OBDPros scantool | 1234
00:0B:0D:88:E6:DC | 0x001f00 | G-Rays1 |
00:0A:3A:25:A2:A7 | 0x001f00 | HUDGPS |
--
bluetooth-wizard unable to pair to fixed pin
All of the following I confirmed (and with the exception of the last
one were confirmed before I wrote the patch because I couldn't pair
them at all).
Note I have two GRays-1, neither would pair. I also have a second
Tecom, which I didn't bother trying (since it would be the same)
00:03:C9:30:97
The dirty half-dozen:
00:03:89:C4:30:8B clock offset: 0x3c73class: 0x240404 260Plantronics PIN
00:0A:94:04:FE:95 clock offset: 0x4bc5class: 0x20040c VS600 headset pin
00:03:C9:30:97:64 clock offset: 0x0217class: 0x200404 Tecom ("BT
Headset") headset pin
00:06:66:01:45:C3 clock offse
OK here you are Jonathan. This is the information you requested for my
Qstarz BT-Q880 GPS receiver.
$ hcitool scan
Scanning ...
00:00:00:00:46:7CBT-Q880
$ hcitool inq 00:00:00:00:46:7C
Inquiring ...
00:00:00:00:46:7Cclock offset: 0x7c58class: 0x00
The default PIN for this
Here are the results for my Holux M-241
[EMAIL PROTECTED]:~/Desktop$ hcitool scan
Scanning ...
00:1B:C1:04:F2:BB HOLUX_M-241
[EMAIL PROTECTED]:~/Desktop$ hcitool inq 00:1B:C1:04:F2:BB
Inquiring ...
00:1B:C1:04:F2:BB clock offset: 0x1c6dclass: 0x001f00
[EMAIL PROTECT
And what my patch does is to display the randomly generated PIN (and
most devices will accept longer, more secure ones - 8 is a typical
number). I never suggested replacing them altogether.
The user can leave the random PIN and use it or modify it.
I knew about the paring fail exits problem whic
@ravi:
I assume you meant "With the kernel in Intrepid", not (hardy) Heron.
This might be a separate bug (from the fixed pin problem). If so it
might be better to start a new bug report (and post the number here),
but for now...
Could you try from a intrepid live CD (I'm worried that the
mix-an
I tried this from the ppa and it worked fine with my Holux m-241.
Thank you very much.
On Wed, Nov 12, 2008 at 11:25 AM, Adilson Oliveira <[EMAIL PROTECTED]> wrote:
> @tz
> Thanks, I missed this message. Anyway, I just tested locally and works fine.
> Just sent to my PPA here https://edge.launc
hcitool scan
Scanning ...
[bdaddr]X3 micro
hcitool inq [bdaddr]
Inquiring ...
[bdaddr]clock offset: 0x39fcclass: 0x200404
The correct pin is 1234.
Jonathan Ernst wrote:
> @Daniel Newman
> Could you please provide the output of :
>
> 1) hcitool scan
> 2) hcitool inq [bluetoot
What is the address of your PPA?
I would like to try this with my gps reciever.
Thanks
Wilbur
On Wed, Nov 12, 2008 at 10:34 AM, Adilson Oliveira <[EMAIL PROTECTED]> wrote:
> @tz
> Add your patch as an attachment and not inline (it's breaking the format of
> the patch) and I'll add it to my PPA
The patch works. I don't know if anyone wants to get it into an Ubuntu
update.
On Wed, Nov 12, 2008 at 12:58 PM, matli <[EMAIL PROTECTED]> wrote:
> No, I don't think it's a kernel problem. Just to be sure I just tested
> with my old Hardy kernel (2.6.24-21), and as expected, the bug stil
> occure
CC-ed from the relevant bug discussion. This is my first GTK program
(at least the original modal dialog), so it is probably horrid, but
solves the problem. I don't know how to integrate it with the wizard
gtk objects (it would require either a new PIN selection page, or
something in the existing
I wrote a followup - a web page for every owner of a bluetooth device
that needs a special PIN that would submit it as a new bug report is
possible...
Perhaps Ubuntu can write its own patch - it looks simple enough but I
would need time to add the panel (I've only done Gtk in Python).
The short a
26 matches
Mail list logo
