Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Can not activate bluetooth

Need help with peripherals or devices?
Message
Author
LarsF
Posts: 10
Joined: 2019-05-26 20:04

Can not activate bluetooth

#1 Post by LarsF »

Hi everyone I have a problem. I have used this wiki https://wiki.debian.org/BluetoothUser but when i open blueman or bluedevil I can not find any devices. Then I run this command

Code: Select all

sudo /etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-05-28 20:11:26 CEST; 30min ago
     Docs: man:bluetoothd(8)
  Process: 2823 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
 Main PID: 2823 (code=exited, status=1/FAILURE)
   Status: "Starting up"

maj 28 20:11:26 Acer systemd[1]: Starting Bluetooth service...
maj 28 20:11:26 Acer bluetoothd[2823]: Bluetooth daemon 5.43
maj 28 20:11:26 Acer bluetoothd[2823]: D-Bus setup failed: Connection ":1.9…file
maj 28 20:11:26 Acer systemd[1]: bluetooth.service: Main process exited, co…LURE
maj 28 20:11:26 Acer systemd[1]: Failed to start Bluetooth service.
maj 28 20:11:26 Acer systemd[1]: bluetooth.service: Unit entered failed state.
maj 28 20:11:26 Acer systemd[1]: bluetooth.service: Failed with result 'exi…de'.
Hint: Some lines were ellipsized, use -l to show in full.
Then I tryed to start bluetooth again.

Code: Select all

sudo /etc/init.d/bluetooth start
[....] Starting bluetooth (via systemctl): bluetooth.serviceJob for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
 failed!

Code: Select all

journalctl -rx
-- Logs begin at Tue 2019-05-28 19:15:30 CEST, end at Tue 2019-05-28 19:42:52 CE
maj 28 19:42:52 Acer sudo[2423]: pam_unix(sudo:session): session closed for user
maj 28 19:42:52 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
maj 28 19:42:52 Acer systemd[1]: bluetooth.service: Unit entered failed state.
maj 28 19:42:52 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
maj 28 19:42:52 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
maj 28 19:42:52 Acer bluetoothd[2435]: Unable to get on D-Bus
maj 28 19:42:52 Acer bluetoothd[2435]: D-Bus setup failed: Connection ":1.79" is
maj 28 19:42:52 Acer bluetoothd[2435]: Bluetooth daemon 5.43
maj 28 19:42:52 Acer systemd[1]: Starting Bluetooth service...
-- Logs begin at Tue 2019-05-28 19:15:30 CEST, end at Tue 2019-05-28 19:42:52 CE
maj 28 19:42:52 Acer sudo[2423]: pam_unix(sudo:session): session closed for user
maj 28 19:42:52 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
maj 28 19:42:52 Acer systemd[1]: bluetooth.service: Unit entered failed state.
maj 28 19:42:52 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
Does anyone have any idea, why bluetooth service dont want to start and what i can do to start it.

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#2 Post by chaanakya »

Some of the lines in the log seem to have been cut off when you pasted them here.
You can do

Code: Select all

sudo systemctl edit bluetooth.service
and put in the following:

Code: Select all

[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/bluetoothd --debug -n
Now, if you do a

Code: Select all

sudo systemctl daemon-reload
and then

Code: Select all

sudo systemctl start bluetooth
you'll get more debugging output in the journal.

kevinthefixer
Posts: 190
Joined: 2018-05-05 22:30

Re: Can not activate bluetooth

#3 Post by kevinthefixer »

Lars, you haven't given us any details at all about your hardware, or for that matter your OS. My first guess is that you are missing firmware for your Bluetooth device but that guess is based on a near-total lack of information! Do you have firmware-linux-nonfree installed?

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Can not activate bluetooth

#4 Post by GarryRicketson »

Post the output of:

Code: Select all

lsb_release -a 
and show us some better details on you system, please.

I can think of at least 1 other reason, besides missing firmware, but it all depends on what Debian Version it is, if it is even Debian.

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#5 Post by LarsF »

chaanakya wrote:Some of the lines in the log seem to have been cut off when you pasted them here.
You can do

Code: Select all

sudo systemctl edit bluetooth.service
and put in the following:

Code: Select all

[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/bluetoothd --debug -n
Now, if you do a

Code: Select all

sudo systemctl daemon-reload
and then

Code: Select all

sudo systemctl start bluetooth
you'll get more debugging output in the journal.

Code: Select all

sudo systemctl edit bluetooth.service
Is empty. I wrote in the lines, and then

Code: Select all

sudo systemctl daemon-reload
Unknown operation deamon-reload.

Code: Select all

sudo systemctl start bluetooth
Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
kevinthefixer wrote:Lars, you haven't given us any details at all about your hardware, or for that matter your OS. My first guess is that you are missing firmware for your Bluetooth device but that guess is based on a near-total lack of information! Do you have firmware-linux-nonfree installed?
My system is a Acer aspire E5-571-59AX with Debian 9 (Stretch). Bluetooth adapter is built-in Qualcomm Atheros AR956X. I have installed firmware-linux-nonfree for Qualcomm Atheros AR956X. At the beginning there was a fail of loading firmware on boot, that has changed when I installed the firmware. But then the fail to start came.
GarryRicketson wrote:Post the output of:

Code: Select all

lsb_release -a 
and show us some better details on you system, please.

I can think of at least 1 other reason, besides missing firmware, but it all depends on what Debian Version it is, if it is even Debian.
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.9 (stretch)
Release: 9.9
Codename: stretch
Last edited by LarsF on 2019-06-07 20:02, edited 1 time in total.

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#6 Post by chaanakya »

LarsF wrote: Unknown operation deamon-reload.
That's odd. You're definitely using a systemd system, so I'm confused as to why that didn't work. Please make sure you didn't make a typo.
LarsF wrote: Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
Right. You should have gotten more output in the journal, so you should do

Code: Select all

sudo journalctl -xe -u bluetooth.service
to see if there's more output there.

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#7 Post by LarsF »

Sorry what is a typo?

Code: Select all

$ sudo journalctl -xe -u bluetooth.service
-- Support: https://www.debian.org/support
-- Logs begin at Fri 2019-06-07 17:20:33 CEST, end at Sat 2019-06-08 01:52:51 CE
jun 07 17:20:45 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:46 Acer bluetoothd[525]: Bluetooth daemon 5.43
jun 07 17:20:46 Acer bluetoothd[525]: D-Bus setup failed: Connection ":1.10" is 
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:46 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:20:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:59 Acer bluetoothd[1031]: Bluetooth daemon 5.43
jun 07 17:20:59 Acer bluetoothd[1031]: D-Bus setup failed: Connection ":1.46" is
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:01 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:01 Acer bluetoothd[1538]: Bluetooth daemon 5.43
jun 07 17:22:01 Acer bluetoothd[1538]: D-Bus setup failed: Connection ":1.77" is
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:01 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:50 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:50 Acer bluetoothd[2095]: Bluetooth daemon 5.43
jun 07 17:22:50 Acer bluetoothd[2095]: D-Bus setup failed: Connection ":1.83" is
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:50 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:28:35 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:28:35 Acer bluetoothd[2419]: Bluetooth daemon 5.43
jun 07 17:28:35 Acer bluetoothd[2419]: D-Bus setup failed: Connection ":1.89" is
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:28:35 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 20:00:38 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 20:00:38 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 21:28:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 21:28:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 21:28:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Logs begin at Fri 2019-06-07 17:20:33 CEST, end at Sat 2019-06-08 01:52:51 CE
jun 07 17:20:45 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:46 Acer bluetoothd[525]: Bluetooth daemon 5.43
jun 07 17:20:46 Acer bluetoothd[525]: D-Bus setup failed: Connection ":1.10" is 
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:46 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:20:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:59 Acer bluetoothd[1031]: Bluetooth daemon 5.43
jun 07 17:20:59 Acer bluetoothd[1031]: D-Bus setup failed: Connection ":1.46" is
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:01 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:01 Acer bluetoothd[1538]: Bluetooth daemon 5.43
jun 07 17:22:01 Acer bluetoothd[1538]: D-Bus setup failed: Connection ":1.77" is
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:01 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:50 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:50 Acer bluetoothd[2095]: Bluetooth daemon 5.43
jun 07 17:22:50 Acer bluetoothd[2095]: D-Bus setup failed: Connection ":1.83" is
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:50 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:28:35 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:28:35 Acer bluetoothd[2419]: Bluetooth daemon 5.43
jun 07 17:28:35 Acer bluetoothd[2419]: D-Bus setup failed: Connection ":1.89" is
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:28:35 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 20:00:38 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 20:00:38 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 21:28:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 21:28:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 21:28:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Logs begin at Fri 2019-06-07 17:20:33 CEST, end at Sat 2019-06-08 01:52:51 CE
jun 07 17:20:45 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:46 Acer bluetoothd[525]: Bluetooth daemon 5.43
jun 07 17:20:46 Acer bluetoothd[525]: D-Bus setup failed: Connection ":1.10" is 
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:46 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:46 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:20:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:20:59 Acer bluetoothd[1031]: Bluetooth daemon 5.43
jun 07 17:20:59 Acer bluetoothd[1031]: D-Bus setup failed: Connection ":1.46" is
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:20:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:20:59 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:01 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:01 Acer bluetoothd[1538]: Bluetooth daemon 5.43
jun 07 17:22:01 Acer bluetoothd[1538]: D-Bus setup failed: Connection ":1.77" is
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:01 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:01 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:22:50 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:22:50 Acer bluetoothd[2095]: Bluetooth daemon 5.43
jun 07 17:22:50 Acer bluetoothd[2095]: D-Bus setup failed: Connection ":1.83" is
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:22:50 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:22:50 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 17:28:35 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 17:28:35 Acer bluetoothd[2419]: Bluetooth daemon 5.43
jun 07 17:28:35 Acer bluetoothd[2419]: D-Bus setup failed: Connection ":1.89" is
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 17:28:35 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 17:28:35 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 20:00:38 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 20:00:38 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 20:00:38 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 21:28:59 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 21:28:59 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 21:28:59 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 21:28:59 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 21:28:59 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod
jun 07 21:47:02 Acer systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has begun starting up.
jun 07 21:47:02 Acer systemd[1]: bluetooth.service: Main process exited, code=ex
jun 07 21:47:02 Acer systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
jun 07 21:47:02 Acer systemd[1]: bluetooth.service: Unit entered failed state.
jun 07 21:47:02 Acer systemd[1]: bluetooth.service: Failed with result 'exit-cod

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#8 Post by chaanakya »

LarsF wrote:Sorry what is a typo?
I meant that

Code: Select all

sudo systemctl daemon-reload
is a valid command, so if it complained saying that it's an unknown option, maybe you made a typo when typing it?

[edit] Sorry, didn't realize you were asking what a typo is. It's when you make a mistake when typing something out, so you type "sudo systemctl deamon-reload" instead of "sudo systemctl daemon-reload" and systemd doesn't know what to do.

As for the logs, it seems that when you're copy-pasting the journal output, it's getting cut off.

Can you please do:

Code: Select all

sudo journalctl -xea -u bluetooth.service > logs.txt
and upload the text file (do not copy-paste the contents of the file, just attach it to your reply)?
Last edited by chaanakya on 2019-06-08 01:31, edited 1 time in total.

kevinthefixer
Posts: 190
Joined: 2018-05-05 22:30

Re: Can not activate bluetooth

#9 Post by kevinthefixer »

Lars, "typo" is slang for "typographical error". Some of us backwoods rednecks call it "fat-fingering".

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#10 Post by LarsF »

chaanakya wrote:
LarsF wrote:Sorry what is a typo?
I meant that

Code: Select all

sudo systemctl daemon-reload
is a valid command, so if it complained saying that it's an unknown option, maybe you made a typo when typing it?

[edit] Sorry, didn't realize you were asking what a typo is. It's when you make a mistake when typing something out, so you type "sudo systemctl deamon-reload" instead of "sudo systemctl daemon-reload" and systemd doesn't know what to do.

As for the logs, it seems that when you're copy-pasting the journal output, it's getting cut off.

Can you please do:

Code: Select all

sudo journalctl -xea -u bluetooth.service > logs.txt
and upload the text file (do not copy-paste the contents of the file, just attach it to your reply)?
Sorry It was a typo
but it made no difference to the

Code: Select all

sudo systemctl start bluetooth
still the same error.

When I try to upload an attachment I get an error The extension txt is not allowed.

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#11 Post by LarsF »

kevinthefixer wrote:Lars, "typo" is slang for "typographical error". Some of us backwoods rednecks call it "fat-fingering".
Okay Thanks for the info.

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#12 Post by chaanakya »

LarsF wrote:When I try to upload an attachment I get an error The extension txt is not allowed.
Hmm, okay. Could you upload it to a site like https://textuploader.com/ and paste the URL here? I just don't want the forum or your copy-pasting to strip out valuable info.

kevinthefixer
Posts: 190
Joined: 2018-05-05 22:30

Re: Can not activate bluetooth

#13 Post by kevinthefixer »

chaanakya wrote:
LarsF wrote:When I try to upload an attachment I get an error The extension txt is not allowed.
Hmm, okay. Could you upload it to a site like https://textuploader.com/ and paste the URL here? I just don't want the forum or your copy-pasting to strip out valuable info.
Or put it into a .zip file.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: Can not activate bluetooth

#14 Post by Head_on_a_Stick »

chaanakya wrote:As for the logs, it seems that when you're copy-pasting the journal output, it's getting cut off.
The OP can use the --no-pager option to output plain text to the terminal, this will ease copy&pasting to the boards.
deadbang

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#15 Post by LarsF »

chaanakya and kevinthefixer here is a link to textuploader http://txt.do/1dmyf

kevinthefixer
Posts: 190
Joined: 2018-05-05 22:30

Re: Can not activate bluetooth

#16 Post by kevinthefixer »

What a surprise, permissions problems. Not being a guru, I can't tell if "the configuration file" is for dbus or bluez, but that's where I'd start looking.

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#17 Post by LarsF »

chaanakya wrote:
LarsF wrote:When I try to upload an attachment I get an error The extension txt is not allowed.
Hmm, okay. Could you upload it to a site like https://textuploader.com/ and paste the URL here? I just don't want the forum or your copy-pasting to strip out valuable info.
Here is a link to textuploader http://txt.do/1dmyf

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#18 Post by chaanakya »

Did you modify /usr/share/dbus/system-services/org.bluez.service? Could you try the following?

Code: Select all

sudo apt purge bluez && sudo apt install bluez
That should hopefully reset the security policy and hopefully fix the issue.

LarsF
Posts: 10
Joined: 2019-05-26 20:04

Re: Can not activate bluetooth

#19 Post by LarsF »

chaanakya wrote:Did you modify /usr/share/dbus/system-services/org.bluez.service? Could you try the following?

Code: Select all

sudo apt purge bluez && sudo apt install bluez
That should hopefully reset the security policy and hopefully fix the issue.
That didn't work.

I dont know if it is related but I made a

Code: Select all

sudo apt update && sudo apt upgrade
and that also made fail

Code: Select all

Havde:1 http://security.debian.org/debian-security stretch/updates InRelease
Ignorerer:2 http://ftp.dk.debian.org/debian stretch InRelease                  
Ignorerer:3 http://ppa.launchpad.net/enlightenment-git/ppa/ubuntu eoan InRelease
Havde:4 http://ftp.dk.debian.org/debian stretch-updates InRelease
Havde:5 http://ftp.dk.debian.org/debian stretch Release                       
Fejl:6 http://ppa.launchpad.net/enlightenment-git/ppa/ubuntu eoan Release
  404  Not Found
Indlæser pakkelisterne... Færdig                
E: Arkivet »http://ppa.launchpad.net/enlightenment-git/ppa/ubuntu eoan Release« har ikke en udgivelsesfil.
N: Opdatering, fra et sådant arkiv, kan ikke udføres sikkert og er derfor deaktiveret som standard.
N: Se apt-secure(8)-manualsiden for detaljer om arkivoprettelse og brugerkonfiguration.
Sorry it is in danish. Is there any way to get it in english, else If there is something I should translate just let me know.

chaanakya
Posts: 26
Joined: 2011-10-17 15:03

Re: Can not activate bluetooth

#20 Post by chaanakya »

This is sort of unrelated, but you added a PPA (which is for Ubuntu) to Debian. You made a FrankenDebian. Enlightenment exists in the Debian repositories, and you should directly pull from their git repository if you want a newer version (or switch to Testing or Unstable). Don't use PPAs in Debian.

As for bluez, I'm not really sure, since purging and reinstalling should have reset the security policy. What is the output of the following?

Code: Select all

cat /usr/share/dbus-1/system-services/org.bluez.service
How about this?

Code: Select all

systemctl cat bluetooth.service
Did you change anything bluetooth related, like the systemd service or the D-Bus policy?

Post Reply