Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9415 - kdebluetooth 1.0_beta8-2

Attached to Project: Arch Linux
Opened by John Miller (Borelia) - Thursday, 31 January 2008, 12:17 GMT
Last edited by Thomas Bächler (brain0) - Friday, 01 February 2008, 10:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:I can see my bluetooth is loading during boot, but it is not working when kdm x-server is up and running. But if I run /etc/rc.d/bluetooth start it works. I wonder why it doesn't write an error here, should be restart right. Anyway if I put the line /etc/rc.d/bluetooth start in my /etc/rc.local everything works just fine.


Additional info:
* package version(s) bluez-libs 3.24-1 bluez-utils 3.24-2 kdebluetooth 1.0_beta8-2

MODULES=(8139cp 8139too mii slhc ac97_bus snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-mid
i-event snd-seq snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-mpu401-uart snd-ac97-codec snd-via82x
x hci_usb soundcore)

DAEMONS=(syslog-ng network netfs autofs crond @samba @alsa @hal @fam bluetooth kdm)

Steps to reproduce:
This task depends upon

Closed by  Thomas Bächler (brain0)
Friday, 01 February 2008, 10:45 GMT
Reason for closing:  Not a bug
Comment by Roman Kyrylych (Romashka) - Friday, 01 February 2008, 10:18 GMT
Maybe dbus is not loaded at that time yet? dbus is started by rc.d/hal, but hal is started in background, so there's no garantee dbus is running when bluetooth starts. Try to remove @ before hal.
Comment by Thomas Bächler (brain0) - Friday, 01 February 2008, 10:45 GMT
dbus has to be started before bluetooth. Put dbus before the @hal, then you can change bluetooth to @bluetooth if you like. I won't change anything in this behaviour until we get a clear policy for handling daemon dependencies, as the way it is handled in hal is not right IMO. Closing.

Loading...