an interface to bluetooth loud-speakers cannot be established,
although the device seems to be correctly recognised, as show in the in the
Adapters - System Settings - Bluettooth Adapters - Name box as AEG LB 4713,
the search can be left on for 10 minutes, only exit from the wizard is <ctl>+c
system responses are as follows
all packages are current per 12:00 today
any help would be appreciated
thx in advance
cheers
hp-17-p105ng<2016Mär14><~>lsmod |grep blue
bluetooth 532480 38 bnep,btbcm,btusb,rfcomm,btintel
rfkill 28672 8 cfg80211,hp_wmi,bluetooth
hp-17-p105ng<2016Mär14><~>service --status-all | grep rfkill
systemd-rfkill@rfkill0.service loaded active exited Load/Save RF Kill Switch Status of rfkill0
systemd-rfkill@rfkill1.service loaded active exited Load/Save RF Kill Switch Status of rfkill1
hp-17-p105ng<2016Mär14><~>rfkill list 0
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
hp-17-p105ng<2016Mär14><~>service bluetooth status
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Mo 2016-03-14 17:13:15 CET; 7min ago
Docs: man:bluetoothd(8)
Main PID: 779 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
`-779 /usr/lib/bluetooth/bluetoothd
Mär 14 17:13:14 hp-17-p105ng bluetoothd[779]: Bluetooth daemon 5.35
Mär 14 17:13:15 hp-17-p105ng bluetoothd[779]: Starting SDP server
Mär 14 17:13:15 hp-17-p105ng bluetoothd[779]: Bluetooth management interface 1.9 initialized
Mär 14 17:13:15 hp-17-p105ng bluetoothd[779]: Failed to obtain handles for "Service Changed" characteristic
Mär 14 17:13:48 hp-17-p105ng.home bluetoothd[779]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource
Mär 14 17:13:48 hp-17-p105ng.home bluetoothd[779]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink
hp-17-p105ng<2016Mär14><~>dmesg |tail -n 12
14.736103] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
14.736125] Bluetooth: BNEP socket layer initialized
15.239603] ip6_tables: (C) 2000-2006 Netfilter Core Team
15.254378] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
15.259758] ip_tables: (C) 2000-2006 Netfilter Core Team
32.518223] r8169 0000:02:00.0 eth0: link down
48.317591] Bluetooth: RFCOMM TTY layer initialized
48.317606] Bluetooth: RFCOMM socket layer initialized
48.317615] Bluetooth: RFCOMM ver 1.11
48.363057] fuse init (API version 7.23)
50.586393] Bluetooth: hci0 command 0x1003 tx timeout
hp-17-p105ng<2016Mär14><~/Updates/cmds>bluedevil-wizard
bluedevil.wizard: Manager initialized
bluedevil.wizard: Initialize Discover Page
bluedevil.wizard: Starting scanning
bluedevil.wizard: Wizard done: 0
hp-17-p105ng<2016Mär14><17:30><~/Updates/cmds>
Upgrade from 13.2? – KDE?
Check ‘bluedevil’ – possibly it’s the KDE Plasma 4 version.
Possibly need to remove everything, including the libraries, that’s “Bluetooth” and reinstall ‘bluez’ with ‘bluedevil5’ plus the associated helper modules including the pulseaudio Bluetooth module.
expect for libbluetooth3, which was re-install with the force parameter, as Networkmanager is dependent on it,
(all packages deleted then re-installed had the same version number)
to get the same functionality each of the deleted files had to be re-installed
unfortunately the situation remains the same
cheer
PS. and output as follows,
hp-17-p105ng<2016Mär15><18:32><~>grep blue .xsession-errors-\:0
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/bluedevil.so"
kdeinit5: Got EXEC_NEW '/usr/bin/blueberry-tray' from launcher.
kdeinit5: preparing to launch '/usr/bin/blueberry-tray'
bluedevil: Created
bluedevil: ObexManager operational changed false
bluedevil: Bluetooth operational changed true
bluedevil: Agent registered
bluedevil: Requested default Agent
bluedevil: ObexManager operational changed true
bluedevil: ObexAgent registered
systemtray: ST Found DBus-able Applet: "org.kde.plasma.bluetooth" "org.bluez"
ST : DBus service "org.bluez" appeared. Loading "org.kde.plasma.bluetooth"
systemtray: ST new task "org.kde.plasma.bluetooth"
systemtray: Loading applet: "org.kde.plasma.bluetooth" 0
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling..
.
.
.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
hp-17-p105ng<2016Mär15><18:32><~>
On the other hand you seem to be using the Gnome GUI and therefore do not need the KDE components: BlueDevil.
If you get rid of the KDE components and just install the Gnome components (gnome-bluetooth package) what happens then?
Or, yet another Plasma 5 KDE issue: I am also experiencing Plasma 5 Leap 42.1 Lenovo G505s Laptop Bluetooth “not really connected” to a “not very smart” mobile telephone. Will investigate further when another issue has been completed.
No. Last week-end, tried again without success. Everything seems to be correctly installed and works
as it should except when a connection is tried it scans until cancelled.
The assumption is its driver related. On the hp-Pavilion-17-p105ng, to get the wireless to connect,
the driver from Broadcom was installed.
Although its been stated that the new kernels have the correct modules installed its
still no joy with kernels 4.1.21-14-default or 4.6.1-14-default. The new modules must be for the
b43 compatible wireless cards.
I attempted again just now – Leap 42.1 latest (all patches/updates installed) Lenovo G505s (AMD; Atheros Bluetooth (internal USB)).
It works!! – assuming “just hit it!!”.
If I open the KDE Plasma Bluetooth module and “connect” to the mobile telephone (Samsung GSM – not Smart
!), the connection drops after a few seconds. - If I send a file to the phone, the Bluetooth connection opens and the file transfers and lands as expected in the correct folder.
If I select a file in the phone and send it via Bluetooth after offering “known Bluetooth destinations” if the Leap Laptop is selected the phone opens a Bluetooth connection and the file as expected to the directory in the Bluetooth set-up.
Catch-22: I’ve set-up the phone to be “trustworthy” and “automatically accept connections from trustworthy devices”.
Not only the Leap 42.1 machine but, also the Bluetooth device has to be set-up to “trust” the device at the other end of the Bluetooth connection.
[HR][/HR]My mobile telephone always asks for a confirmation that the incoming file to be accepted.
It (the telephone) also has to have the “authorised” flag set for the “other” Bluetooth device in it’s list of “known” Bluetooth devices:
for example, my car (Bluetooth “hands-free” telephony), as well as the Leap 42.1 machine.
If the “authorised” flag is not set against the “Leap 42.1 machine” then, when I push a file from the Leap Laptop to the telephone, the telephone asks twice for confirmation:
once that the Leap Laptop is OK;
and then again for an OK that the file be stored on the telephone.
There is some openSUSE information related to the Broadcom licensing issue:
The licensing issue and the necessary package is mentioned here: <https://software.opensuse.org/package/broadcom-wl>
The ‘broadcom-wl’ package itself is available from the Packman repository under “Essentials”.
There’s some additional information available from this “not openSUSE” site here: <http://opensuse-guide.org/wlan.php>
Will investigate further when another issue has been completed.