Thanks for all the hints!
Please check whether the problem has been solved for you, too.
MJ
]]>Another fix can be found in this thread that I started. I think this fix is a little less destructive to the interworkings of Gnome.
https://bbs.archlinux.org/viewtopic.php?id=197482
The upstream bug is also here, feel free to comment:
https://bugzilla.gnome.org/show_bug.cgi?id=749208
Thanks! I will give this a try.
]]>The upstream bug is also here, feel free to comment:
https://bugzilla.gnome.org/show_bug.cgi?id=749208
I now have GDM/Gnome and fully functioning Bluetooth.
Thanks for your help ! :-x
]]>I will try playing with downgrading bluez rather than disabling gdm (I want to use gdm's lock-screen features with Gnome Shell).
It turns out the cause of the problem is different. Look at my next post.
I dual boot two installs of Arch Linux ... one stable, one testing ... the second I hack and play and configure and experiment .... so .....
Following your experience, I disabled GDM and installed LightDM, I also followed this guide from the Manjaro Linux forums .. (be sure to follow the links in Step 3 on setting up your ~/.xinitrc file) to Auto-Login in without a Display Manager ..
In both instances, Pulseaudio instantly found my Samsung Home Audio bluetooth connection ...
@rainpl Good find ! ... I am not experienced enough with linux to know why this is happening ... I can only assume it's the way that the session is started by GDM
For now I will live without GDM ... I am liking the Auto Login tbh :-)
]]>UPDATE: I can replicate this!
If you disable GDM:
sudo systemctl disable gdm
reboot the machine and start X then bluetooth audio works flawlessly again!
]]>Strangely, if I unplug the Bluetooth dongle and re-plug it, PulseAudio detects the speakers. Pulse module-bluetooth-discover is loaded at start up and I would assume working, as the speakers are detected after the re-plug.
I have subscribed to this thread in the hope of finding a solution. Thanks for any help
]]>Anyway, after some "recent" update, I lost this functionality: even if the connection seems to complete (from the bluetooth connection window in Gnome), as far as I go to the audio settings, the proper output isn't created (only speaker available).
I try to get some meaningful log.
This is what happen when the bluetooth service is started (i.e.: the toggle is switched to "enable" in the bluetooth window):
apr 27 22:38:30 Okinawa systemd[1]: Reached target Bluetooth.
apr 27 22:38:30 Okinawa systemd[1]: Starting Bluetooth.
apr 27 22:38:30 Okinawa systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill3...
apr 27 22:38:30 Okinawa systemd[1]: Started Load/Save RF Kill Switch Status of rfkill3.
apr 27 22:38:30 Okinawa bluetoothd[360]: Failed to obtain handles for "Service Changed" characteristic
apr 27 22:38:30 Okinawa bluetoothd[360]: Failed to register org.bluez.LEAdvertisingManager1
apr 27 22:38:30 Okinawa bluetoothd[360]: Failed to register LEAdvertisingManager1 interface for adapter
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Error adding Link Loss service
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Current Time Service could not be registered
apr 27 22:38:30 Okinawa bluetoothd[360]: gatt-time-server: Input/output error (5)
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Not enough free handles to register service
apr 27 22:38:30 Okinawa bluetoothd[360]: Sap driver initialization failed.
apr 27 22:38:30 Okinawa bluetoothd[360]: sap-server: Operation not permitted (1)
apr 27 22:38:30 Okinawa bluetoothd[360]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
apr 27 22:38:31 Okinawa systemd-coredump[2469]: Process 2461 (gnome-control-c) of user 1003 dumped core.
apr 27 22:38:31 Okinawa bluetoothd[360]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource
apr 27 22:38:31 Okinawa bluetoothd[360]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink
apr 27 22:38:31 Okinawa bluetoothd[360]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSource
apr 27 22:38:31 Okinawa bluetoothd[360]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSink
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> BT device Nexus 4 (98:D6:F7:B4:01:36) added (NAP)
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> (98:D6:F7:B4:01:36): new Bluetooth device (driver: 'bluez' ifindex: 0)
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> (98:D6:F7:B4:01:36): exported as /org/freedesktop/NetworkManager/Devices/4
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> (98:D6:F7:B4:01:36): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> (98:D6:F7:B4:01:36): preparing device
apr 27 22:38:31 Okinawa NetworkManager[364]: <info> (98:D6:F7:B4:01:36): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
At this point, I open the dialog for the bluetooth speaker and enable its connection, this is what happens:
apr 27 22:40:16 Okinawa kernel: Bluetooth: Failed to start inquiry: status 12
apr 27 22:40:18 Okinawa bluetoothd[360]: /org/bluez/hci0/dev_FC_58_FA_BE_32_F1/fd1: fd(22) ready
apr 27 22:40:18 Okinawa rtkit-daemon[521]: Supervising 4 threads of 2 processes of 2 users.
apr 27 22:40:18 Okinawa rtkit-daemon[521]: Successfully made thread 2719 of process 520 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
apr 27 22:40:18 Okinawa rtkit-daemon[521]: Supervising 5 threads of 2 processes of 2 users.
apr 27 22:40:18 Okinawa kernel: input: FC:58:FA:BE:32:F1 as /devices/virtual/input/input14
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (II) config/udev: Adding input device FC:58:FA:BE:32:F1 (/dev/input/event12)
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) FC:58:FA:BE:32:F1: Applying InputClass "evdev keyboard catchall"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) FC:58:FA:BE:32:F1: Applying InputClass "system-keyboard"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 35 paused 0
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (II) Using input driver 'evdev' for 'FC:58:FA:BE:32:F1'
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) FC:58:FA:BE:32:F1: always reports core events
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) evdev: FC:58:FA:BE:32:F1: Device: "/dev/input/event12"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (--) evdev: FC:58:FA:BE:32:F1: Vendor 0 Product 0
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (--) evdev: FC:58:FA:BE:32:F1: Found keys
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (II) evdev: FC:58:FA:BE:32:F1: Configuring as keyboard
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input14/event12"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (II) XINPUT: Adding extended input device "FC:58:FA:BE:32:F1" (type: KEYBOARD, id 13)
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) Option "xkb_rules" "evdev"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) Option "xkb_model" "pc104"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: (**) Option "xkb_layout" "it"
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: The XKEYBOARD keymap compiler (xkbcomp) reports:
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: > Ignoring extra symbols
apr 27 22:40:18 Okinawa /usr/lib/gdm/gdm-x-session[675]: Errors from xkbcomp are not fatal to the X server
and.. no "bluetooth speaker output" in the audio setting (I just tried pavucontrol and nothing appears there, too).
In my recent system upgrades I have:
[2015-04-04 19:30] [ALPM] upgraded pulseaudio (5.0-1 -> 6.0-1)
and:
[2015-04-04 19:12] [ALPM] upgraded bluez (5.28-1 -> 5.30-1)
[2015-04-04 19:12] [ALPM] upgraded bluez-libs (5.28-1 -> 5.30-1)
[2015-04-04 19:12] [ALPM] upgraded bluez-utils (5.28-1 -> 5.30-1)
[2015-04-11 11:14] [ALPM] upgraded gnome-bluetooth (3.14.0-1 -> 3.16.0-1)
[2015-04-20 23:21] [ALPM] upgraded gnome-bluetooth (3.16.0-1 -> 3.16.1-1)
I hope these info are enough for someone. Unfortunately, I can't get any help from Google.
May I ask for your help?
Thank you in advance!
]]>