Hi Dmitry,
> T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=13d3 ProdID=3494 Rev= 2.00
> S: Manufacturer=Realtek
> S: Product=Bluetooth Radio
> S: SerialNumber=00e04c01
> C:* #Ifs= 2 Cfg#= 1 Atr=e0
Hi Dmitry,
> T: Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#= 5 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=04ca ProdID=3018 Rev=00.01
> C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> I:
Hi Dmitry,
> BugLink: https://bugs.launchpad.net/bugs/1535802
>
> T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=04ca ProdID=3011 Rev=00.01
> C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I: If#= 0 Alt= 0
Hi Jesse,
btusb would not take care of this device without its id in the table.
If the output of usb-devices is still needed, please let me know.
yes, I just wanna see usb-devices and not go through 3 pages of verbose
lsusb output since that is not helping me.
Regards
Marcel
--
You
Hi Jesse,
Add a new entry (413c:8197) to device ID table.
Signed-off-by: Wen-chien Jesse Sung jesse.s...@canonical.com
---
drivers/bluetooth/btusb.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index
I can't find your patch in that package. However if you remove allow
send_interface=org.bluez.Agent/ then you break it again. All other
send_interface can go, but that one has to stay. It is _not_ insecure.
--
D-Bus Policy needs checking
https://bugs.launchpad.net/bugs/318740
You received this
Keep in mind that the send_interface is limited to the root user
context. Protecting that makes no sense anyway since we can just go
ahead and change the policy if you wanna mess with it. The receiving
side has to ensure here that the caller is valid. And at least bluez-
gnome does this.
--
This is not a question. This is a real bug. Evolution stops working for
me with Ubuntu 8.10 and it clearly uses the wrong port. With 8.04 the
same setup was working.
--
Connection refused since it tries to connect to port 143 instead of 993
https://bugs.launchpad.net/bugs/292385
You received
Public bug reported:
Starting with Ubuntu 8.10 the org.freedesktop.Hal.Device.KillSwitch
interfaces are missing. Previously my X61 laptop showed a Bluetooth
killswitch from the thinkpad_acpi driver and a WLAN killswitch from the
iwl4965 driver when calling hal-device. With 8.10 these are no
Public bug reported:
After the upgrade to Ubuntu 8.10 I can't check my emails anymore using
Evolution. I always get a connection refused message. The mailserver
is using IMAPS on port 993, but Evolution keeps trying port 143.
Pressing F5 for folder refreshing works, but retrieving the actual
Filing wish lists within Launchpad doesn't get you anywhere. You should
talk to upstream.
--
bluetooth-sendto should remember last directory
https://bugs.launchpad.net/bugs/284311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The Debian naming scheme is broken. You did it right, but now you are
falling back to something totally broken while Fedora and OpenSuSE get
it right.
Tell the Debian maintainers to follow upstream proposal and stop messing
around with things they have no clue about.
--
Look into switching to
ALSA has no enumeration for virtual devices and every Bluetooth headset
is a virtual device. We discussed this at PlumbersConf and might get
into the direction to allow enumeration via the hint API with plugins
to enumerate virtual devices, but we are not there yet.
This also means that these
The init script should be /etc/init.d/bluetooth and not bluetoothd,
please use what all other distros are using and not try to make up
something.
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Bugs,
The problem with HID pairing (mouse/keyboard) has nothing to do with the
btusb driver. They are not related at all.
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The upcoming 2.6.27 kernel has support for Bluetooth 2.1, but would need
at least bluez-utils-3.36 or better bluez-4.x for a full experience.
Also bluez-gnome-1.x is required.
--
Add Bluetooth 2.1 support
https://bugs.launchpad.net/bugs/221685
You received this bug notification because you are a
The timeout change is only fixing a symptom. If you wanna disable the
timeout you can have a one-line patch that does so. The real fix for
this is a kernel patch to the hidp.ko driver that I posted to the bluez-
devel mailing list.
--
Bluetooth Mouse looses connection after some time of
Patches for this needs to be submitted via the bluez-devel mailing list.
It has to be fixed upstream first.
--
imprecision in hciconfig manpage
https://bugs.launchpad.net/bugs/192668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If you have obex-data-server-0.3 and bluez-gnome-0.23 then you don't
need gnome-bluetooth. You can enable OBEX Push and FTP services via
bluetooth-properties and use bluetooth-sendto to actually send files.
--
Install gnome-bluetooth by default to enable receiving files via bluetooth
It will work with obex-data-server-0.3 and bluez-gnome-0.23. Check out
the code!
--
Install gnome-bluetooth by default to enable receiving files via bluetooth
https://bugs.launchpad.net/bugs/72033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't know who in the end decided to move bluetoothd-service-audio
into its own package. That is totally stupid and makes no real sense.
The audio service can exist without any ALSA or GStreamer plugin and
could as so be perfectly part of bluez-utils package. Having separate
bluez-alsa and
It makes sense to split bluez-alsa and bluez-gstreamer, because their
dependency chain is big. However if you use ALSA you don't wanna have
the dependencies on GStreamer and vice-versa. Also an embedded system
with SCO over PCM (like the Nokia tablets) might wanna use only the
audio service and
These applications are not ready for mainline right now. The bluez-gnome
upstream _doesn't_ install these on purpose.
--
Missing apps in bluez-gnome
https://bugs.launchpad.net/bugs/180222
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
The bluez-gnome upstream using a mailing list like a lot of old fashion
projects :)
Anyway, I fixed it upstream now. So next release should have it.
--
System-Preferences-Bluetooth Preferences menu item name is redundant
https://bugs.launchpad.net/bugs/176664
You received this bug notification
This one should have been fixed within bluez-utils-3.22, but don't ask
me for the exact patch. The audio guys fixed it.
--
bluetoothd-service-audio crashed with SIGSEGV
https://bugs.launchpad.net/bugs/141479
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
This one has no information in it. So no idea why this crash happened.
--
[apport] hcid crashed with SIGSEGV
https://bugs.launchpad.net/bugs/116769
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
These kind of bugs should be reported to the upstream project. Post
things like this to the bluez-devel mailing list in the future.
--
typo in bluez-utils/audio/manager.c
https://bugs.launchpad.net/bugs/159737
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If you are not running D-Bus, then you can't use Bluetooth. Period.
And btw. D-Bus is _not_ reconfiguring your network devices.
NetworkManager is doing this.
--
hcid coupled with dbus
https://bugs.launchpad.net/bugs/151845
You received this bug notification because you are a member of Ubuntu
Period, because the decision to use D-Bus as inter-process communication
for Bluetooth has been made a long time ago. This means it is a purely
technical decision. And yes, I am not even going to argue about it.
There is no other sane way except you wanna live in the stone age of
Unix operating
If you wanna use Bluetooth then you have to use D-Bus. However
minimalist doesn't mean that you can't have D-Bus. Actually D-Bus itself
is really small. As mentioned before, it is only a simple inter-process
communication protocol.
Actually with all applications using D-Bus to communicate with
That is probably as simple bug in hidd. It happen if you try to connect
a device which is not working according to the HID specification. These
are all devices that are not a mouse, keyboard or in some cases a mobile
phone.
--
Gusty: Not seeing bluetooth services even after pairing
I have no idea why this happens. I was using the Bluetooth GStreamer
plugin all the time and never had a problem. Didi something in the
GStreamer API changed? Can gst_type_find_peek() return NULL?
--
totem crashed with SIGSEGV in sbc_typefind()
https://bugs.launchpad.net/bugs/144748
You received
This will happen. It is the plan to include it, but might not happen as
quickly as you want.
--
missing an obex way to send/receive files
https://bugs.launchpad.net/bugs/144751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
It has been like this for a while. Even in Feisty. With the new version
we know enforce using D-Bus more and slowly reduce the importance and
need of hcid.conf.
--
Wrong /var/lib/bluetooth/BD address/config prevents setting correct hci class
https://bugs.launchpad.net/bugs/144544
You received
The mode discoverable is non-sense. Only mode connectable is needed.
When calling hciconfig and it doesn't show pscan then no HID device
can re-connect.
--
[feisty] bluetooth mouse doesn't connect automatically
https://bugs.launchpad.net/bugs/84541
You received this bug notification because you
This means that hid2hci needs an update to detect this dongle. Should be
fixed when using bluez-utils-3.19. I don't have the MX5000 and so I
can't confirm it.
--
Bluetooth dongle (Logitech diNovo Laser) not found by bluez, runs as USB-Hub
https://bugs.launchpad.net/bugs/83484
You received this
The HCI versus HID mode has nothing to do with report mode versus boot
mode. That are two total different things.
--
Bluetooth mouse doesn't work.
https://bugs.launchpad.net/bugs/29506
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Don't touch hcid.conf at all. The values from the /var/lib/bluetooth wll
overwrite any settings done in hcid.conf and this is on purpose. If you
wanna change your class of device, use the D-Bus methods or bluetooth-
properties.
--
Wrong /var/lib/bluetooth/BD address/config prevents setting
Switching Bluetooth on and off should be integrated with the rfkill
switch framework. This is out of the scope of BlueZ and we decided not
to handle it. It should always be done through HAL.
--
Menu entry to turn device off completly
https://bugs.launchpad.net/bugs/144075
You received this bug
The hidd --connect ... command needs to be used only once. After that
there is not need to use it ever again. The same applies to hidd
--search What you are doing is attempting to make something work,
but with no idea how Bluetooth HID is designed. Stop messing around and
make only sure that
This makes no sense at all. The connected state has nothing to do with
the capability of sending or receiving files. The connections will be
created on demand and as needed.
--
Ubuntu should make obex sending/receiving work by default
https://bugs.launchpad.net/bugs/107942
You received this bug
You always need to start a program for that task if you split UI code
and actual profile implementation. However the D-Bus service activation
should take care of this in the background.
--
Ubuntu should make obex sending/receiving work by default
https://bugs.launchpad.net/bugs/107942
You
This is not a kernel issue. The SCO flow control patch was never
approved by upstream and actually the new audio service from bluez-utils
doesn't require this patch at all. Using some old btsco or plugz package
might fail. Go with the audio support that is supported by the upstream
BlueZ
I tried to talk to the Debian guys to make them clean up the package and
actually enable the new services (they are off by default even if they
are stable enough). So far I haven't seen a fixed up Debian package.
The main issue is DEB_CONFIGURE_EXTRA_FLAGS. The --enable-obex part is
not needed
These race conditions are all fixed now. The hcid will start other
services like network service (which replaced pand).
--
pand in /etc/init.d/bluetooth fails with Failed to connect to the local SDP
server. Connection refused(111) error. Solution included
https://bugs.launchpad.net/bugs/121915
The 2.6.22 kernel is perfectly fine. No need to apply any of my -mh1
patches. Actually they will de-stabilize the kernel since they contain a
lot of experimental stuff.
--
HID only supports boot protocol
https://bugs.launchpad.net/bugs/86826
You received this bug notification because you are a
I have no idea. This could be an issue with GLib and its GIOChannel with
libdbus.
--
[apport] hcid crashed with SIGSEGV
https://bugs.launchpad.net/bugs/117397
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
The Introspection support is missing. We added this with bluez-
utils-3.10 for the first time. No easy backport will be possible.
--
/org/bluez/hci0 does not exist in dbus
https://bugs.launchpad.net/bugs/111846
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This will happen within the next bluez-utils releases. The headsetd from
plugz with its ALSA plugins will be merged into the Bluetooth audio
service. This is work in progress and should be ready for Feisty+1. The
setup of Headset will be done through D-Bus. The API specification for
that has
Maybe this is Logitech specific. However I only have the old diNovo
desktop and that one works perfectly fine for me. Even the re-connect
has no problems.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because
The sdpd is no longer needed you can start hcid with -s and it will
start the SDP server.
--
Sdpd is missing in the package bluez-utils
https://launchpad.net/bugs/96916
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
The sdpd process is no longer needed. All the functionality are
provided by hcid -s. No idea what KDE is trying to do, but this looks
like a bug in KDE and not bluez-utils.
--
Failed to connect to SDP server (bluetooth)
https://launchpad.net/bugs/97297
--
ubuntu-bugs mailing list
If KDE checks for the sdpd process, then this is a KDE bug. Running
hcid -s provides the same functionality as sdpd.
--
Sdpd is missing in the package bluez-utils
https://launchpad.net/bugs/96916
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Actually someone needs to finally fix these UI components. The Linux
kernel and the D-Bus API for Bluetooth work perfectly fine with higher
inquiry modes.
--
Inquring for devices from GUI doesn't work due to misconfiguration
https://launchpad.net/bugs/92866
--
ubuntu-bugs mailing list
Don't put --connect in HIDD_OPTIONS. This will fully mess with your
system and whoever proposed this strange settings is wrong. In general
the option --server is fully enough and HIDD_ENABLE must be on.
The --search or --connect needs only to be issued once. After that the
mouse or keyboard will
Ask your notebook manufacturer. All Bluetooth adapters for the laptops
are USB so far. So I guess that is no different for yours. However all
of them will not appear on the USB bus until you tell them so. And that
is the magic that needs to be found. Sometimes it is done via software
and other
Try sudo hciconfig hci0 inqmode 0.
--
Bluetooth Scans Return Empty in Edgy; Worked in Dapper
https://launchpad.net/bugs/72685
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I think it is worth trying bluez-utils-3.9. I am pretty sure that this
has been fixed.
--
[apport] hcid crashed with SIGSEGV
https://launchpad.net/bugs/85307
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The bluez-libs-3.9 requirement was me just being lazy. It will compile
perfectly against bluez-libs-3.8 and also work without problems, but
don't tell anyone ;)
As a side note. You can compile it with --disable-sdpd and modify the
init script to not start sdpd and instead give hcid the -s to use
Check with hciconfig and lsusb if the Bluetooth adapter is really
recognized.
--
bluetooth not working on X72IA6 laptop
https://launchpad.net/bugs/83419
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Then you need to find the switch to activate the device. It might be a
soft or ACPI related switch.
--
bluetooth not working on X72IA6 laptop
https://launchpad.net/bugs/83419
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Installing bluez-utils-3.9 should solve all the race conditions on
system boot and then HIDD_OPTIONS=--master --server should be enough.
--
[feisty] bluetooth mouse doesn't connect automatically
https://launchpad.net/bugs/84541
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The bluez-utils-3.9 fixes are race condition in the initialization
routine of the adapter. So this problem should be gone now.
--
Bluetooh is off sometimes when i wake from suspend
https://launchpad.net/bugs/44706
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This might be caused by the adapter initialization race condition that
has been fixed with bluez-utils-3.9. The bluetooth-applet only display
what it gets told by the hcid.
--
[feisty] bluetooth applet reports device is off when turned on
https://launchpad.net/bugs/83374
--
ubuntu-bugs mailing
I think it is worth having a test-drive with bluez-utils-3.9 and the
latest D-Bus low-level library. It might be fixed or we have a really
ugly bug sleeping somewhere.
--
hcid crashdump
https://launchpad.net/bugs/79666
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I think all these problems on Apple based system are caused by a race
condition in the startup and init routines for the Bluetooth adapter. I
am pretty sure that I finally fixed this. At least my Quad G5 running
Edgy now has no problems anymore.
The main problem was that the command for setting
The kernel should have been fixed to handle that properly. It is part of
the 2.6.19-rc3 kernel and later. It fixes similar issues in BNEP and
CMTP support.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
You have to switch to the old inquiry mode with sudo hciconfig hci0
inqmode 0. Starting with bluez-utils-3.x the best available inquiry
mode will be selected by default and this is not gonna change. You have
to fix gnome-bluetooth.
--
gnome-obex-send cannot find devices
The Logitech HID proxy switching has been always some kind of blackbox
magic, because we don't know how it actually works. Neverless, this
patch has been accepted upstream.
--
hcitool scan and dev return empty although BT works
https://launchpad.net/bugs/66884
--
ubuntu-bugs mailing list
I am not the upstream author of gnome-bluetooth. Otherwise, I would have
already fixed this. The proper interface to use is the new D-Bus based
API. It will take care of all this stuff.
--
gnome-obex-send cannot find devices
https://launchpad.net/bugs/70718
--
ubuntu-bugs mailing list
The bluez-passkey-gnome package was a packing mistake and should be
fully removed. The package that contains all GNOME related applications
is bluez-gnome. This is the name of the source package and should also
be the name of the binary package. It is now fixed in Debian.
--
bluez-passkey-gnome
Starting with bluez-utils-3.x we set the adapter into Inquiry with RSSI
if it supports it and most Bluetooth 1.2 or later ones do. So in this
mode you will see HCI_Inquiry_Result_With_RSSI and no longer
HCI_Inquiry_Result events. Since the gnome-bluetooth and kdebluetooth
only listen to later one,
You must make sure that you have a passkey agent running. Otherwise the
system will reject any paring requests for security reasons. Install the
bluez-passkey-gnome package for Edgy or go with the passkey-agent.c
example.
--
Can't pair phone and pc by bluetooth
https://launchpad.net/bugs/45776
This is a bug in the gnome-bluetooth code. You can issue hciconfig hci0
inqmode as root to set your device back into the inquiry results mode
for Bluetooth 1.1 devices. Then it should find remote devices again.
To be 100% clear, this is a gnome-bluetooth bug and not an issue of the
functionality
If you log into the GNOME desktop, the passkey agent will ask you to
enter the PIN code and everything will work as expected. With the latest
updated packages you will see a Bluetooth icon in the status bar and you
need to click it to open the input dialog for the PIN. Otherwise check
Starting with bluez-gnome-0.6 all this is possible. It introduces a
Bluetooth preferences application that lets you select the icon display
policy, configure your device name and class of device. It also makes it
possible to switch between connectable and discoverable mode.
--
Die systray icon
The request for entering a passkey are not D-Bus signals. So you might
wanna start hcidump -X -V to capture the traffic on the HCI and check
if a pairing request really happens.
--
No PIN request - no pairing possible
https://launchpad.net/bugs/68460
--
ubuntu-bugs mailing list
Syncing the full source of bt-applet is a better idea. There exists
another problem with the current use of the D-Bus proxy objects and
attaching signal handlers. It is enough to attach the adapter signals
once per lifetime of bt-applet. It doesn't matter if the adapter get
removed or reattached.
I personally have never seen a crash with bt-applet. The D-Bus proxy
object has the weird behavior that I described, but that's it. I have to
make some small adjustments for the icon display policy and then I will
release a new version. Postponing this to edgy-updates should be fine.
--
Problem
As far as I know, there exists no keyutils in Debian unstable at the
moment. I have seen that package in Fedora Core 5 and so some
distributions are packaging it already.
--
Missing keyutils package
https://launchpad.net/bugs/66427
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: anjuta
When using the Scintilla editor component of Anjuta the application
crashes with the following error:
(anjuta:18074): libgnomevfs-CRITICAL **:
gnome_vfs_format_uri_for_display_internal: assertion `uri != NULL' failed
*** glibc detected ***
Public bug reported:
The keyutils tool and library are missing in Edgy. The source can be
found here:
http://people.redhat.com/~dhowells/keyutils/
This package is needed by the userspace daemon and tools for eCryptFS.
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
I am not sure when I have the time to release a new upstream version,
but until then you can apply the attached patch.
** Attachment added: Implement icon policy settings
http://librarian.launchpad.net/4822238/implement_icon_policy_settings.patch
--
Die systray icon die!
I think that I forgot to mention that my patch fixes another problem
with the D-Bus proxy handling and it brings it in sync with upstream.
You might wanna check the upstream CVS log.
--
Die systray icon die!
https://launchpad.net/bugs/65645
--
ubuntu-bugs mailing list
If your local Bluetooth adapter supports inquiry with RSSI, then the
current gnome-bluetooth version is not capable of handling these inquiry
results. As a workaround you can call hciconfig hci0 inqmode 0.
--
Unable to detect bluetooth phone using gnome tools
https://launchpad.net/bugs/65938
--
This has been fixed in the CVS version and the icon display policy is
controllable via a GConf entry.
--
Die systray icon die!
https://launchpad.net/bugs/65645
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The passkey-agent.c example source code is now installed under
/usr/share/doc/bluez-utils/examples/ together with a simple Makefile to
compile it if needed. Remember that this is an example code on how to
write a passkey agent. Every desktop environment should provide its own
default passkey
Starting with bluez-utils-3.7 it defaults to security user and this
means that if no passkey agent has been registered all pairing attempts
will be rejected.
--
Default PIN is a security issue
https://launchpad.net/bugs/52422
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The bluez-sdp package has been deprecated a long time ago and bluez-
utils is a full replacement.
--
[UNMETDEPS] bluez-sdp has unmet dependencies
https://launchpad.net/bugs/65410
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This must be a weird race condition in the upgrade path. The binary
package has the init script listed as executable:
# dpkg --contents bluez-utils_3.7-1ubuntu2_amd64.deb | grep init
drwxr-xr-x root/root 0 2006-10-11 15:39 ./etc/init.d/
-rwxr-xr-x root/root 6963 2006-10-11 15:39
Hi Daniel,
We will need at least bluez-libs 3.5 for that. Debian has 3.7 of both at
the moment.
best is to go for 3.7 for both versions. The bluez-libs-3.7 from Debian
is clean and should make no problems at all. The bluez-utils-3.7 from
Debian is finally a lot cleaner than before. Thanks to
92 matches
Mail list logo
