** Tags added: eol feisty kubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/89291
Title:
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to
work
To manage notifications abo
** Changed in: kdebluetooth (Debian)
Status: New => Fix Released
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://bugs.launchpad.net/bugs/89291
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I have been doing a little more experimenting and noticed that the
bluetooth stack on my Sony Ericsson can crash from time to time. So if
my procedure for accessing your phone files via OBEX does not work
anymore all of a sudden, don't blame it on the Linux bluetooth stack,
blame it on the phone's
One more thing: make sure you first install the following obex utilities
(especially gnome-vfs-obexftp) before trying to exchange files between
your laptop and bluetooth phone:
[EMAIL PROTECTED]:~$ apts obex
i cobex - Connector
for mobile
Hi,
Here is a small procedure I have written that allows pairing bluetooth
telephone with Kubuntu, that allows using the bluetooth phone as a
remote control for Kubuntu and describes how to exchange files with a
bluetooth phone using bluetooth protocol
1. Make sure /usr/sbin/hcid is running by en
I can confirm this bug, passkey agent must be started by hand, it is not
started during KDE startup.
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://bugs.launchpad.net/bugs/89291
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Maybe this can help someone:
https://answers.launchpad.net/ubuntu/+question/8379
(trayer is not needed if you use kicker)
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://bugs.launchpad.net/bugs/89291
You received this bug notification because you are a membe
on feisty fawn beta i confirm that the pinhelper wouldnt show up,
pairing is not possible
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://bugs.launchpad.net/bugs/89291
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
on feisty fawn beta i confirm that the pinhelper wouldnt show up,
pairing is not possible
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://bugs.launchpad.net/bugs/89291
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Any passkey agent has to be started in the user session. Starting a
passkey agent at boot time is totally wrong. This is a KDE bug. GNOME
handles this correctly.
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing
I have the same issue with passkey-agent not being started at boot.
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I was able to pair with my phone starting passkey-agent by hand. So the
problem is that passkey-agent is not started on boot. Which script is in
charge of starting the passkey-agent?
Software versions:
bluez-utils 3.9-0ubuntu2
bluez-pin 0.30-2.1ubuntu3
kdebluetooth 0.99+1.0beta2-1ubuntu5
--
Kubu
It is working flawlessly here. I'm using bluez-utils 3.9-0ubuntu2 and
kdebluetooth 0.99+1.0beta2-1ubuntu5. Answering gpothier: /usr/bin
/passkey-agent --default /usr/lib/kdebluetooth/kbluepin
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/
Still no luck after restarting the machine. I do not see any pinhelper
or passkey-agent process (tried 'ps aux |grep pin' and 'ps aux |grep
pass'). When is the pin helper started? How can I start it by hand?
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://lau
chaging status for bluez-utils too, as the patch is there.
** Changed in: bluez-utils (Ubuntu)
Status: Confirmed => Fix Released
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
changing to fix-released as it works for everyone but gpothier, probably
local issue or just needs passkey-agent to be restarted
** Changed in: kdebluetooth (Ubuntu)
Status: Confirmed => Fix Released
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://lau
gpothier : pinhelper is not restarted with kbluepin.
What happens after you restart your computer ?
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
In today's updates there was a mention of a change regarding pin helper
in bluetooth packages:
debian/patches/010-kubuntu-pin-helper.patch:
- updated for with 3.9
As far as I'm concerned I still cannot pair with my bluetooth phone
(SonyEricsson K700i).
I also tried "security auto" in hcid.c
Confirmed.
Doesn't work here too.
The interface for PIN helpers changed with bluez 3.x, and broke kbluepin.
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I can confirm this bug too. Tried with a few phones aswell, and
pin_helper doesnt show.
Anyone know what has changed between edgy and feisty regarding bluetooth
(dbus?) ?
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bu
I marked this bug as confirmed because it already has duplicate.
** Changed in: kdebluetooth (Ubuntu)
Status: Unconfirmed => Confirmed
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I marked this bug as confirmed because it already has duplicate.
** Changed in: bluez-utils (Ubuntu)
Status: Unconfirmed => Confirmed
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Changed in: kdebluetooth (Debian)
Status: Unknown => Unconfirmed
--
Kubuntu Feisty does not ask for bluetooth pin. Pinhelpers seem not to work
https://launchpad.net/bugs/89291
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Just a hint: The debian package kdebluetooth_0.99+1.0beta2-3_i386.deb
works good for the pin helper thing. But I had to use --force-overwrite
because it overwrites pinhelper which is also in bluez-utils.
I'm sorry I can't you provide more information on this.
--
Kubuntu Feisty does not ask for b
** Bug watch added: Debian Bug tracker #382771
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382771
** Also affects: kdebluetooth (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382771
Importance: Unknown
Status: Unknown
--
Kubuntu Feisty does not ask for bluetoo
There are already there is already an bug in the kde bt:
http://bugs.kde.org/show_bug.cgi?id=133634
and at least two bugs in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383877
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382771
Hope this helps
--
Kubuntu Feisty does not ask fo
26 matches
Mail list logo
