This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
With Linux ubuntu 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux nothing has changed.
However, this behaviour is also interesting:
After hibernate and resume, the status is correct, and enabling /
disabling using bluez works. After a second hibernate /
Is this a bluez bug or a kernel bug? As it seems at least tighlty related to
ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
I would guess it's a kernel issue. It's still present in 3.7. btw.
(tried upstream mainline)
--
You received this bug notification because you are a member of
Bluetooth acting strangely here, in Ubuntu 12.10. Led is always on, no
matter if I disable or enable bluetooth via applet, however syslog tells
me the device is enabled/disabled and the rfkill softblock state is
altered. The hardware bluetooth led worked fine in Ubuntu 12.04.
I am unable to use
My fear is that the bug I reported is also related to
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/277211
which complicates things a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072118
After some more investigations I can come up with this consistent
behaviour:
If I reboot the laptop of with bluetooth enabled, it will come up the
next time working. Working means the status is correctly recognized by
the Kubuntu applet and bluetooth is working.
If I disable Bluetooth, the
However, if I unpower the device using the Kubuntu applet (it's relaibly
not working, draining 5 Watts less)
/etc/init/rfkill-store
will save the state as enabled
/var/rfkill/saved-state
contains
hci0 0
after a boot. So it seems the device remembers it's last state and not
bluetoothd. With
service bluetooth start/stop command only works in sudo mode in
kubuntu 12.10 quantal 64 bit.
System - Dell Inspiron N5050
Processor Intel Pentium(R) CPU B960 @ 2.2 GHz
2 Gb RAM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072118
Title:
The underlying problems seems to be:
The described behaviour is only visible, when shutting down with bluetooth
disabled.
If I leave bluetooth enabled, bluetooth works when rebooting. It seems as the
initial state of bluetooth is not correctly determined on startup or applet
initialisation,
10 matches
Mail list logo
