Announcement

Collapse
No announcement yet.

Bluetooth - no systray icon? Another systray problem or???

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bluetooth - no systray icon? Another systray problem or???

    I've been using 15.04 daily for a couple weeks. Latest adventure is trying to figure out where the systray bluetooth icon is. It's not available (there, but hidden) and bluetooth doesn't show in services in System Settings > Startup.. > Background... Here's my last syslog from boot (bluetooth only)

    Code:
    May 28 13:08:41 office bluetoothd[994]: Bluetooth daemon 4.101
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Bluetooth daemon 4.101
    May 28 13:08:41 office bluetoothd[994]: Starting SDP server
    May 28 13:08:41 office bluetoothd[994]: DIS cannot start: GATT is disabled
    May 28 13:08:41 office bluetoothd[994]: Failed to init deviceinfo plugin
    May 28 13:08:41 office bluetoothd[994]: Failed to init proximity plugin
    May 28 13:08:41 office bluetoothd[994]: Failed to init time plugin
    May 28 13:08:41 office bluetoothd[994]: Failed to init alert plugin
    May 28 13:08:41 office bluetoothd[994]: Failed to init thermometer plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Starting SDP server
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: DIS cannot start: GATT is disabled
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init deviceinfo plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init proximity plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init time plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init alert plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init thermometer plugin
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Failed to init gatt_example plugin
    May 28 13:08:41 office bluetoothd[994]: Failed to init gatt_example plugin
    May 28 13:08:41 office bluetoothd[994]: Bluetooth Management interface initialized
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: Bluetooth Management interface initialized
    May 28 13:08:41 office bluetoothd[994]: hci0: Load Long Term Keys (0x0013) failed: Not Supported (0x0c)
    May 28 13:08:41 office bluetoothd[994]: bluetoothd[994]: hci0: Load Long Term Keys (0x0013) failed: Not Supported (0x0c)
    May 28 13:08:41 office bluemon[1222]: * Starting bluemon...
    May 28 13:08:41 office bluemon[1222]: disabled in /etc/default/bluemon
    May 28 13:08:42 office NetworkManager[1002]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
    May 28 13:08:42 office bluetoothd[994]: Adapter /org/bluez/994/hci0 has been enabled
    May 28 13:08:42 office bluetoothd[994]: bluetoothd[994]: Adapter /org/bluez/994/hci0 has been enabled
    May 28 13:08:55 office bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/HFPAG
    May 28 13:08:55 office bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/HFPHS
    May 28 13:08:55 office bluetoothd[994]: bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/HFPAG
    May 28 13:08:55 office bluetoothd[994]: bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/HFPHS
    May 28 13:08:55 office bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/A2DPSource
    May 28 13:08:55 office bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/A2DPSink
    May 28 13:08:55 office bluetoothd[994]: bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/A2DPSource
    May 28 13:08:55 office bluetoothd[994]: bluetoothd[994]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/BlueZ4/A2DPSink
    It appears to be starting, it's there in processes. I verified the packages that are needed are installed (and then some). I have three other programs that won't use the systray properly, so it could just be a tray thing again.

    Anyone else getting different results?

    Please Read Me

    #2
    For comparison, here's the syslog fr0m my 14.04 install where it works:
    Code:
    May  6 08:48:45 office bluetoothd[734]: hci0: Remove UUID (0x0011) failed: Busy (0x0a)May 28 12:11:23 office bluetoothd[711]: input-headset driver probe failed for device F8:E0:79:8A:06:D1
    May 28 12:11:23 office bluetoothd[711]: hci0: Load Long Term Keys (0x0013) failed: Not Supported (0x0c)
    May 28 12:11:23 office bluetoothd[711]: Adapter /org/bluez/711/hci0 has been enabled
    May 28 12:11:26 office NetworkManager[1882]: <info> (F8:E0:79:8A:06:D1): new Bluetooth device (driver: 'bluez' ifindex: 0)
    May 28 12:11:46 office bluetoothd[711]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/HFPAG
    May 28 12:11:46 office bluetoothd[711]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/HFPHS
    May 28 12:11:46 office bluetoothd[711]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSource
    May 28 12:11:46 office bluetoothd[711]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSink
    May 28 12:12:11 office bluetoothd[711]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/HFPAG
    May 28 12:12:11 office bluetoothd[711]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/HFPHS
    May 28 12:12:11 office bluetoothd[711]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource
    May 28 12:12:11 office bluetoothd[711]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink

    Please Read Me

    Comment


      #3
      There's no Plasma 5 widget or control panel for Bluetooth yet.

      Code:
      steve@x250:~$ [B]kcmshell5 --list |grep -i blue[/B]
      kf5.kservice.sycoca: Trying to open ksycoca from "/home/steve/.cache/ksycoca5"
      
      steve@x250:~$ [B]kcmshell4 --list |grep -i blue[/B]
      bluedeviladapters      - Configure Bluetooth adapters
      bluedevildevices       - Manage Bluetooth devices
      bluedeviltransfer      - Configure Bluetooth file sharing and transfers
      
      steve@x250:~$ [B]kcmshell4 bluedeviladapters[/B]   [I]<-- seems to work[/I]
      
      steve@x250:~$ [B]kcmshell4 bluedevildevices[/B]   [I]<-- seems to work[/I]
      
      steve@x250:~$ [B]kcmshell4 bluedeviltransfer[/B]   [I]<-- seems to work[/I]
      Also:
      http://www.omgubuntu.co.uk/2015/04/k...-kubuntu-15-04
      Bluetooth applet currently not available to Kubuntu upgraders

      Comment


        #4
        Originally posted by Teunis
        I've got the Blueman applet installed, it shows.
        That's for GNOME. I'd rather wait for the applet to get ported...

        Comment


          #5
          That's about what I figured, but wanted verification, thanks. I'll wait.

          Guess that's what I get for being an early adopter...

          Please Read Me

          Comment


            #6
            If you type "Bluetooth" in the kmenu or kicker, you can configure bt and run whatever program provides the tray icon - which will appear. I'm at work and can't remember if the app is stll bluedevil or not. It's there but does not autostart, and is not present in system settings.

            Comment


              #7
              Originally posted by claydoh View Post
              If you type "Bluetooth" in the kmenu or kicker, you can configure bt and run whatever program provides the tray icon - which will appear. I'm at work and can't remember if the app is stll bluedevil or not. It's there but does not autostart, and is not present in system settings.
              not so @here.

              Code:
              stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ Bluetooth
              Bluetooth: command not found
              stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ bluetooth
              No command 'bluetooth' found, did you mean:
               Command 'bluetoothd' from package 'bluez' (main)
              bluetooth: command not found
              stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$
              "Bluetooth" in Kmenu results in a blank stare... nothing in the menu relating to Bluetooth.

              Please Read Me

              Comment


                #8
                Ahhh, If I run

                kcmshell4 bluedeviladapters

                I get an ibus error, but the program opens up. After setting the bluetooth device to "always visible" I get a tray icon.

                Please Read Me

                Comment


                  #9
                  Originally posted by claydoh View Post
                  If you type "Bluetooth" in the kmenu or kicker, you can configure bt and run whatever program provides the tray icon - which will appear. I'm at work and can't remember if the app is stll bluedevil or not. It's there but does not autostart, and is not present in system settings.
                  This fails for me, too. I do have a /usr/bin/bluetooth, but this comes from the tlp power management package.

                  Originally posted by oshunluvr View Post
                  Ahhh, If I run kcmshell4 bluedeviladapters I get an ibus error, but the program opens up. After setting the bluetooth device to "always visible" I get a tray icon.
                  That's interesting. No ibus error here, because I purged all those packages. However, I never see any Bluetooth device entry added to the system tray.



                  Comment


                    #10
                    Odd. Here it's listed under Entries and is now visible...
                    Attached Files

                    Please Read Me

                    Comment


                      #11
                      Steve, how do you purge ibus? @Here, the 4 ibus packages are dependencies of bluedevil...

                      Please Read Me

                      Comment


                        #12
                        Originally posted by oshunluvr View Post
                        Steve, how do you purge ibus? @Here, the 4 ibus packages are dependencies of bluedevil...
                        Remove these packages: inputattach, ibus-qt4, im-config, plasma-widget-kimpanel, libibus-1.0-5, libibus-qt1.

                        Where are you showing any Bluedevil-ibus dependencies? I'm not seeing any:
                        Code:
                        steve@x250:~$ [B]sudo apt-cache depends bluedevil[/B]
                        bluedevil
                          Depends: kde-runtime
                          Depends: libbluedevil1
                          Depends: libc6
                          Depends: libkdecore5
                          Depends: libkdeui5
                          Depends: libkfile4
                          Depends: libkio5
                          Depends: libqt4-dbus
                          Depends: libqtcore4
                          Depends: libqtgui4
                          Depends: libstdc++6
                          Depends: bluez
                            bluez:i386
                          Depends: obexd-client
                          Depends: obex-data-server
                         |Suggests: pulseaudio-module-bluetooth
                          Suggests: bluez-alsa
                          Conflicts: bluedevil:i386

                        Comment


                          #13
                          When I tried to remove ibus-qt4 (and others) it "offered" to remove bluedevil... using Muon. Here's the console result;
                          Code:
                          stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ sudo apt-get remove ibus-qt4Reading package lists... Done
                          Building dependency tree       
                          Reading state information... Done
                          You might want to run 'apt-get -f install' to correct these:
                          The following packages have unmet dependencies:
                           bluedevil : Depends: obex-data-server but it is not going to be installed
                          E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
                          stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ sudo apt-get -f insta;;
                          bash: syntax error near unexpected token `;;'
                          stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ sudo apt-get -f insta;;ll
                          bash: syntax error near unexpected token `;;'
                          stuart@office:/mnt/samsung/@Kubuntu_14_04/var/log$ sudo apt-get -f install
                          Reading package lists... Done
                          Building dependency tree       
                          Reading state information... Done
                          Correcting dependencies... Done
                          The following packages were automatically installed and are no longer required:
                            linux-headers-3.19.0-16 linux-headers-3.19.0-16-generic linux-image-3.19.0-16-generic linux-image-extra-3.19.0-16-generic
                          Use 'apt-get autoremove' to remove them.
                          The following packages will be REMOVED:
                            bluedevil
                          0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
                          After this operation, 2,657 kB disk space will be freed.
                          Do you want to continue? [Y/n] n
                          Abort.

                          Please Read Me

                          Comment


                            #14
                            Well, I removed bluedevil, removed obexd-sever. then all the ibus stuff, then reinstalled bluedevil along with obex-data-server. I'll let you know what if anything changes.

                            Right now tho, I got J.T. playin' over my Bose Mini Soundbar and that boy sounds good, lol...

                            Please Read Me

                            Comment


                              #15
                              Weird. Glad your Bluetooth is working. Wish I could figure out why it isn't here...

                              On your machine, what's the output of
                              Code:
                              dpkg -l | grep -i blu

                              Comment

                              Working...
                              X