Bluetooth doesn't work after last update.

zyghom · 2009-02-15 07:27:59

as of me I had to comment this line:

install -D -m755 ${startdir}/src/bluez-utils-${pkgver}/daemon/passkey-agent ${startdir}/pkg/usr/bin/passkey-agent || return 1

as there is not "passkey-agent" file in 3.36 anymore
what about pairing then ?

and second: in kde there is dependency missing: kdepim requires pilot-link, and pilot-link : bluez>=4.25

.:B:. · 2009-02-15 15:55:22

You'll have to roll back everything that depends on the new packages... Can be quite the pain in the proverbial *rse.

My bluez-utils build broke on the passkey too, I'll try to find out later on.

.:B:. · 2009-02-15 21:19:19

Okay - passkey-agent seems to be a reference implementation not meant for use by normal users:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382768

So I guess it's not a problem it's not there anymore.

I just took out the line and it builds fine, I also updated bluez-gnome to the latest compatible version for anyone interested - here's the PKGBUILD:

# $Id$
# Maintainer: Roman Kyrylych <roman@archlinux.org>

pkgname=bluez-gnome
pkgver=0.28
pkgrel=1
pkgdesc="bluetooth PIN helper application"
arch=('i686' 'x86_64')
url="http://www.bluez.org/"
license=('GPL')
depends=('hal' 'libnotify>=0.4.4-1' 'gconf>=2.18.0.1-4' 'obex-data-server'
         'bluez-utils' 'desktop-file-utils' 'hicolor-icon-theme')
makedepends=('perlxml')
install=bluez-gnome.install
source=(http://bluez.sourceforge.net/download/${pkgname}-${pkgver}.tar.gz)
md5sums=('f2afcb04e998fdc6aa545633190bc941')
options=('!emptydirs')

build() {
  cd ${startdir}/src/${pkgname}-${pkgver}
  ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
    --disable-desktop-update --disable-mime-update --disable-icon-update
  make || return 1
  make GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 DESTDIR=${startdir}/pkg install

  mkdir -p ${startdir}/pkg/usr/share/gconf/schemas
  gconf-merge-schema ${startdir}/pkg/usr/share/gconf/schemas/${pkgname}.schemas \
    ${startdir}/pkg/etc/gconf/schemas/*.schemas
  rm -f ${startdir}/pkg/etc/gconf/schemas/*.schemas
}

dhave · 2009-02-15 22:48:55

I see that bluez-4.30 has just shown up in the repos. Has anyone tried it to see if it fixes the problems? I don't have my bluetooth mouse with me, so I can't test. I'd just like to know. Thanks.

.:B:. · 2009-02-15 23:01:18

As I pointed out in a previous post, for me it does not (I immediately built 4.30 and upgraded to it). I suspect the bluetoothd daemon has something to do with it; hcid has disappeared from 3.x to 4.x and bluetoothd is now the running daemon. It doesn't take too many options though.

dhave · 2009-02-15 23:06:55

B wrote:

As I pointed out in a previous post, for me it does not (I immediately built 4.30 and upgraded to it). I suspect the bluetoothd daemon has something to do with it; hcid has disappeared from 3.x to 4.x and bluetoothd is now the running daemon. It doesn't take too many options though.

Sorry, I didn't see that before. Oh, well. I guess I'll make do. Usually when one release follows so soon after the previous one, it means that a bad bug had been fixed. Not in this case, apparently.

MAC!EK · 2009-02-15 23:29:50

I managed to pair my phone with laptop:
Hardware:
- SonyEricsson k800i
- Lenovo Thinkpad R61
Software:
- bluez bluez 4.30-1
- kdebluetooth 4.0.3-1

1. I stopped the bluetooth services:
/etc/rc.d/bluetooth stop
2. Removed everythin in: /var/lib/bluetooth/*
3. edited the /etc/conf.d/bluetooth config file:
DAEMON_ENABLE="true"
HIDD_ENABLE="true"
all other option left default (also all defaults in /etc/bluetooth/*)
4. started bluetooth
/etc/rc.d/bluetooth start
5. started kbluetooth (showed an error but worked fine)
6. From kbluetooth Device manager I paired the phone with the notebook (watch the logs /var/log/everything.log, some info is placed there by bluetoothd)

.:B:. · 2009-02-16 01:27:07

An excerpt from the bluetooth configuration file in the new unified bluez package:

# Run the bluetoothd daemon (default: true)
#DAEMON_ENABLE="false"

which means the daemon (bluetoothd) is enabled by default. The /etc/conf.d/bluetooth file is not that much different from 3.x to 4.x, and hidd has always been disabled by default, both in the old and the new bluetooth package(s). You do need it enabled for human interface devices like mice and keyboards, and I assume most people already had that enabled before the switch to the unified package, so I do not think that is the issue here. What actually does seem to be the issue is functionality that hcid handled, and which (presumably) would have been inherited by bluetoothd.

biloky · 2009-02-16 03:45:06

Finally managed to have GNOME bluetooth work using Bluez 4.x.

From extra:
- bluez 4.30-1
- gnome-bluetooth 0.11.0-3
- libbtctl 0.10.0-2

Custom compiled:
- obex-data-server 0.4.4 (newer version)
- openobex 1.3 (older version: see http://tadas.dailyda.com/blog/2009/02/0 … rver-044/)
- nautilus-sendto 1.1.1 (newer version)
- bluez-gnome 1.8 (patch applied: http://bugs.gentoo.org/attachment.cgi?id=171712)
- gvfs 1.0.3 (patch applied: http://bugs.gentoo.org/attachment.cgi?id=174955)

Working:
- pairing
- sending files (via applet and via nautilus-sendto)
- receiving files (need to launch Bluetooth File Sharing)
- browsing via Nautilus (obex://[xx.xx.xx.xx.xx.xx])

Not working (since bluez 3.x):
- Nautilus still does not recognize obex:/// (maybe intentional, not sure)
- In Nautilus, copying from phone to pc works, not the other way around.

EDIT: Just came across this "closed" bug report http://bugs.archlinux.org/task/11502. The above gentoo patches for gvfs and bluez-gnome were already mentioned in the comments.

EDIT (again): No need to downgrade openobex to 1.3. The one in extra works fine (1.4)

Last edited by biloky (2009-02-17 04:45:33)

clarence · 2009-02-16 04:12:54

nice work biloky. can you sure your PKGBUILD's please?

biloky · 2009-02-16 05:24:53

Sure.

obex-data-server 0.4.4
- PKGBUILD (http://pastebin.com/f53d7fa24)

openobex 1.3
- PKGBUILD (http://pastebin.com/f5682340d)

nautilus-sendto 1.1.1
- PKGBUILD (http://pastebin.com/f624b6b4a)
- nautilus-sendto.install (http://pastebin.com/f409188c5)

bluez-gnome 1.8
- PKGBUILD (http://pastebin.com/fc1fe1e5)
- bluez-gnome-1.8-ODS-API.patch (http://pastebin.com/f45b0537f)
- bluez-gnome.install (http://pastebin.com/f732fbfb1)

gvfs 1.0.3
- PKGBUILD (http://pastebin.com/f3c012a7c)
- gvfs-obexftp-updated-apis-2.patch (http://pastebin.com/f383b5a81)
- gvfs.install (http://pastebin.com/f7c55ad97)

zyghom · 2009-02-16 05:37:00

as I don't use gnome but kde for me bluez 4.30 is still an issue
everytime I switch on my laptop, I have to pair the mouse again
on old bluez-utils/libs it was not a case
this is making me frustrated already

evdvelde · 2009-02-16 08:49:37

Same problem here... I always have to pair again, which is really annoying since it is my mouse... I cannot click on kdebluetooth without mouse and I cannot pair with it in KDE without clicking on kdebluetooth
It worked automatically with bluez-utils.

zyghom · 2009-02-16 10:14:33

but who shall we send it to as bug ? bluez.org ?

.:B:. · 2009-02-16 11:39:34

You can always try . If it's not an upstream problem then you'll know soon enough . Better report a bug too many than one too few and be stuck with it.

Zibi1981 · 2009-02-16 13:38:09

For an unknown reason rfcomm isn't being loaded automatically after system starts, as it was before this ill-fated update. Anyone could explain to me why?

zyghom · 2009-02-16 13:41:50

on site http://www.bluez.org/ I cannot find bug tracker

mao(tm) · 2009-02-16 18:29:37

Zibi1981
You can turn on it by hand two ways:
1. edit /etc/rc.d/bluetooth;
2. edit /etc/conf.d/bluetooth.

Uncomment in both cases rows begin RFCOMM.

zyghom wrote:

I cannot find bug tracker

Aditionally there are two IRC channels available on freenode.net where you can find developers and other users of BlueZ:
* #bluez (development related topics)
* #bluez-users (non-development related topics)

Link

P.S. Please excuse me for my poor English...

Last edited by mao(tm) (2009-02-16 18:50:23)

zyghom · 2009-02-16 18:36:03

ok, but isn't irc online ? I'm not online same time when they might be - bugzilla is the tool for such, documented etc

mao(tm) · 2009-02-16 19:00:13

zyghom
Bugzilla isn't exist on bluez.org, therefore I posted this quote from their site... No other way report about our problems.

Last edited by mao(tm) (2009-02-16 19:51:23)

zyghom · 2009-02-16 19:05:36

I know, I've seen this on their site too

panosk · 2009-02-16 20:53:54

I managed to make my bt mouse autoconnect on system startup by doing these:

edited /etc/rc.d/bluetooth so it reads like this:

DAEMON_ENABLE="true"
HID2HCI_ENABLE="false"
HIDD_ENABLE="true"
RFCOMM_ENABLE="true"
DUND_ENABLE="false"
PAND_ENABLE="false"

Also, after I found out my mouse address, I added this:

HIDD_OPTIONS="--connect 00:1D:D8:96:3A:9B"

Also, my /etc/conf.d/bluetooth contains these:

# Bluetooth configuraton file

# Bluetooth services (allowed values are "true" and "false")

# Run the bluetoothd daemon (default: true)
#DAEMON_ENABLE="false"

# Run hid2hci (default: false)
HID2HCI_ENABLE="true"

# Run the sdp daemon (default: false)
# If this is disabled, hcid's internal sdp daemon will be used
#SDPD_ENABLE="true"

# Run the bluetooth HID daemon (default: false)
HIDD_ENABLE="true"

# Activate rfcomm ports (default: false)
RFCOMM_ENABLE="true"

# Run bluetooth dial-up networking daemon (default: false)
#DUND_ENABLE="true"

# Run bluetooth PAN daemon (default: false)
#PAND_ENABLE="true"

# rfcomm configuration file (default: /etc/bluetooth/rfcomm.conf)
#RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"

# Options for hidd, dund and pand (default: none)
HIDD_OPTIONS="--connect 00:1D:D8:96:3A:9B"
#DUND_OPTIONS=""
#PAND_OPTIONS=""

I hope it will work for you too.

.:B:. · 2009-02-16 20:56:38

Does it stick after a reboot, suspending, hibernating or a long period of inactivity?

Do you use the rfcomm service? It seems to provide serial port emulation, not what one would need for a bluetooth mouse I'd say... Did you do anything special to get it all to autoconnect (initial setup)? I see you have the HID2HCI service enabled too?

panosk · 2009-02-16 22:11:43

B wrote:

Does it stick after a reboot, suspending, hibernating or a long period of inactivity?
Do you use the rfcomm service? It seems to provide serial port emulation, not what one would need for a bluetooth mouse I'd say... Did you do anything special to get it all to autoconnect (initial setup)? I see you have the HID2HCI service enabled too?

You are right. No need to enable rfcomm and HID2HCI (I lost track of the changes I was making), so I restored the default values for these services. Still, my mouse autoconnects after reboot and suspend . Apart from these changes, I didn't do anything else (I always had the bluetooth daemon in my rc.conf, but I don't know if that makes any difference).
One thing I noticed is that the cursor of the bt mouse runs much faster than it did before the update and the new configuration, and I don't know how to apply different settings without affecting the synaptics touchpad. Also, kbluetooth still displays error code 127 when it starts, but it seems to run fine.

biloky · 2009-02-17 02:07:57

I took out my Genius Navigator 900 bluetooth mouse from the shelf, used the Gnome bluetooth applet to pair the mouse, and it worked... and it also auto-connects on reboot. (Didn't tried suspend or hibernate though, since this desktop pc had issues of not coming back from a suspend.) That's all I did, made no modifications to the config files.

There's a new kdebluetooth in extra. Maybe it might fix the problem for KDE users.

Arch Linux

#26 2009-02-15 07:27:59

Re: Bluetooth doesn't work after last update.

#27 2009-02-15 15:55:22

Re: Bluetooth doesn't work after last update.

#28 2009-02-15 21:19:19

Re: Bluetooth doesn't work after last update.

#29 2009-02-15 22:48:55

Re: Bluetooth doesn't work after last update.

#30 2009-02-15 23:01:18

Re: Bluetooth doesn't work after last update.

#31 2009-02-15 23:06:55

Re: Bluetooth doesn't work after last update.

#32 2009-02-15 23:29:50

Re: Bluetooth doesn't work after last update.

#33 2009-02-16 01:27:07

Re: Bluetooth doesn't work after last update.

#34 2009-02-16 03:45:06

Re: Bluetooth doesn't work after last update.

#35 2009-02-16 04:12:54

Re: Bluetooth doesn't work after last update.

#36 2009-02-16 05:24:53

Re: Bluetooth doesn't work after last update.

#37 2009-02-16 05:37:00

Re: Bluetooth doesn't work after last update.

#38 2009-02-16 08:49:37

Re: Bluetooth doesn't work after last update.

#39 2009-02-16 10:14:33

Re: Bluetooth doesn't work after last update.

#40 2009-02-16 11:39:34

Re: Bluetooth doesn't work after last update.

#41 2009-02-16 13:38:09

Re: Bluetooth doesn't work after last update.

#42 2009-02-16 13:41:50

Re: Bluetooth doesn't work after last update.

#43 2009-02-16 18:29:37

Re: Bluetooth doesn't work after last update.

#44 2009-02-16 18:36:03

Re: Bluetooth doesn't work after last update.

#45 2009-02-16 19:00:13

Re: Bluetooth doesn't work after last update.

#46 2009-02-16 19:05:36

Re: Bluetooth doesn't work after last update.

#47 2009-02-16 20:53:54

Re: Bluetooth doesn't work after last update.

#48 2009-02-16 20:56:38

Re: Bluetooth doesn't work after last update.

#49 2009-02-16 22:11:43

Re: Bluetooth doesn't work after last update.

#50 2009-02-17 02:07:57

Re: Bluetooth doesn't work after last update.

Board footer