Bug 317014 - bluedevil, bluedevil active or not, bluetooth dongle always active
Summary: bluedevil, bluedevil active or not, bluetooth dongle always active
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: bluetooth (show other bugs)
Version: 4.10.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 08:25 UTC by Philippe ROUBACH
Modified: 2014-01-12 17:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2013-03-19 08:25:05 UTC
since kernel 3.5 (no with kernel <= 3.4)

1. Mandriva 2010.2 i586 kde 4.8.5, kernel 3.5.7, bluedevil 1.3rc2

when i start pc
then
i open a kde session
then
i see :
- the bluetooth dongle flashes, indicating it is active
- bluedevil icon is "bluetooth is not active" (by default i put in this state bluedevil)

if with bluedevil you activate or inactivate
then
- bluedevil switches to the required state
- dongle stays active

if you run "bluetoohd stop" or "bluetoohd start"
then
- bluedevil stays in its current states
- dongle stays active

if you run "hciconfig hci0 up" or "hciconfig hci0 down"
then
- bluedevil switches to "active" or not "active"
- dongle stays active

2. openSUSE 12.3 x86_64 , kde 4.10, bluedevil 1.3
2.1
when i start pc
then
i open a kde session
then
i see :
- the bluetooth dongle does not flashes, indicating it is inactive
- bluedevil icon is "bluetooth is active"
then
if you required to bluedevil to switches to "inactive"
then
- bluedevil stays "active"
- bluetooth dongle stays inactive
then
if you run "hciconfig hci0 up"
then
- bluedevil stays active
- bluetooth dongle swithes to active
- now you can switches bluedevil to "active" or "inactive" but bluetooth dongle stays "active"

2.2.

once you reach the state "bluetooth dongle is active

if with bluedevil you activate or inactivate
then
- bluedevil switches to the required state
- dongle stays active

if you run "bluetoohd stop"
then
- bluedevil swithes to "bluetooth inactivated"
- dongle stays active

if you run "hciconfig hci0 down
then
- bluedevil does not change its state
- dongle stays active


Reproducible: Always
Comment 1 Philippe ROUBACH 2013-03-21 07:33:31 UTC
to sum up :

- bluetooth dongle is activated at startup and we can't unactivate it
or
- bluetooth dongle is not activated at startup and we can't activate it

in the case of"bluetooth dongle is not activated at startup and we can't activate it"
there is a subproblem :
bluedevil is blocked in the false state "bluetooth is activated"

to unblock it we must run ""hcicongi hci0 up"
even unblocked we can't activate bluetooth dongle
Comment 2 Alex Fiestas 2013-03-24 17:34:49 UTC
can you paste the output of:
rfkill list

thanks !
Comment 3 Philippe ROUBACH 2013-03-25 08:42:31 UTC
mandriva 2010.2 i586

[root@localhost ~]# rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
[root@localhost ~]# 

i will try with opensuse 12.3
Comment 4 Philippe ROUBACH 2013-03-25 08:51:32 UTC
openSUSE 12.3 x86_64

linux-ia9o:~ # rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
linux-ia9o:~ #
Comment 5 Philippe ROUBACH 2013-03-25 08:56:24 UTC
openSUSE 12.3

there is something different with mandriva 2010.2 i586

mandriva 2010.2 i586 : a daemon bluetoothd with the command bluetooth stop
opensuse 12.3 x86_64 : a daemon bluetoothd with the command bluetooth -n
Comment 6 Alex Fiestas 2013-03-25 10:39:11 UTC
Mandriva is using an unsupported BlueDevil version, and from the name (2010) possibly an unsupported BlueZ version, let's focus on opensuse.
Comment 7 Alex Fiestas 2013-03-25 10:54:03 UTC
We have fixed a bunch of stuff related to this in the incoming 1.3.1, are you able to grab a snapshot made of master?

If not, we better wait until 1.3.1 before doing more testing.
Comment 8 Philippe ROUBACH 2013-03-25 11:08:33 UTC
with mandriva i am very easy to compile and to test. it's not the case with opensuse

but i can try to compile bluedevil 1.3.1

where to grab it and how ?
Comment 9 Alex Fiestas 2013-03-25 13:37:20 UTC
git clone git://anongit.kde.org/libbluedevil
and 
git clone git://anongit.kde.org/bluedevil
Comment 10 Philippe ROUBACH 2013-03-25 13:57:38 UTC
(In reply to comment #9)
> git clone git://anongit.kde.org/libbluedevil
> and 
> git clone git://anongit.kde.org/bluedevil

2 times ??????

what is the the command to compile because i don't know anything about cmake.
Comment 11 Philippe ROUBACH 2013-03-25 13:59:36 UTC
ok i didn't read well
Comment 12 Philippe ROUBACH 2013-03-25 14:01:02 UTC
also what is the command to install ?

thanks
Comment 13 Philippe ROUBACH 2013-03-25 14:05:37 UTC
opensuse bluetooth packets: 

bluez 4.101
openobex 1.5
obex-data-server 0.4.6
obexd 0.45
obexd-client 0.45
Comment 14 Miguel Camargo 2013-04-22 21:46:05 UTC
Hello,

I have same problem in openSUSE 12.3 (openSUSE 12.3 x86_64 , kde 4.10.2, bluedevil 1.3-2.1.2)

If i could help sending any info, please, tell me.

Thanks a lot,
Miguel
Comment 15 Philippe ROUBACH 2013-05-16 14:01:03 UTC
today bluedevil has been updated to 1.3.1 with opensuse 12.3 x86_64


pb still there
Comment 16 Philippe ROUBACH 2013-05-22 06:49:27 UTC
there is same pb as opensuse 12.3 x86_64 with Rosa fresh EE 2012.1 x86_64 :

- during pc boot the dongle is not activated
- bluedevil is blocked to state "activated"
- if i unblock bluedevil with "hciconf hci0 up"
then
with bluedevil in state "activated" or "not activated" then the dongle stays "activated"

it seems this is a general pb
Comment 17 Philippe ROUBACH 2013-05-22 07:16:20 UTC
Rosa Fresh EE 2012.1 x86_64 bluetooth packets :

bluedevil 1.3
lib64bluedevil 1.9.2

bluez 4.101
lib64usb-compat0.1_4  0.1.4
openobex 1.6
obex-data-server 0.4.6
obexd 0.46
obexftp 0.23
lib64dbus-glib-1.2 0.98

according to this document
http://www.linuxfromscratch.org/blfs/view/svn/general/obex-data-server.html
i see one version pb
lib64dbus-glib-1.2 must be 0.100 and it is 0.98 version
Comment 18 Philippe ROUBACH 2013-07-24 12:43:12 UTC
i wonder if the pb is that since kernel 3.4 there is a new way to manage
bluetooth.

i read this "BlueZ only supports the new Bluetooth Management kernel interface
that was introduced in Linux 3.4"

here http://www.bluez.org/release-of-bluez-5-0/

or this "BlueZ developers have recently added the Bluetooth Management (MGMT)
Interface to the Linux Kernel, which significantly improves the Bluetooth
experience on Linux."

here http://padovan.org/blog/2013/02/the-big-changes-of-bluez-5/

i wonder if the solution is to update to bluez 5
Comment 19 Philippe ROUBACH 2014-01-12 17:02:29 UTC
too old
i close