Description of problem: I would be very nice if could add a desktop file for bluedevil in xdg autostart folder. For f20 mate desktop comes without mate-bluetooth which isn't ported to bluez5. https://lists.fedoraproject.org/pipermail/devel/2013-September/189169.html A alternative for mate users is to use bluedevil which is ported to bluez5 and provide a systray applet. For f21 i expect that mate-bluetooth is ported to bluez5, so this is only a temporary solution. To avoid that the applet starts in kde automaticly you can add an entry 'OnlyShowIn=MATE' to the desktop file. I did already add icons for bluedevil to mate-icon-theme and add bluedevil to mate's optinal comps group. Thank you in advance Wolfgang Ulbrich
After one year.....any news?
Sorry, had forgotten about it, I'll try to look into it this week.
Did you check bluedevil package if it's possible?
Mind doing a quick test? cp /usr/share/applications/kde4/bluedevil-monolithic.desktop /etc/xdg/autostart/ and optionally: echo "OnlyShowIn=MATE;" >> /etc/xdg/autostart/bluedevil-monolithic.desktop and restart your session, would something like that suffice?
It starts now under mate, but isn't displayed in the panel :/ [rave@mother ~]$ ps aux | grep blue rave 1695 0.1 0.3 425832 25332 ? S 18:20 0:00 bluedevil-monolithic root 1817 0.0 0.0 30200 4152 ? Ss 18:20 0:00 /usr/libexec/bluetooth/bluetoothd rave 2240 0.0 0.0 112692 2364 pts/0 S+ 18:21 0:00 grep --color=auto blue The right icon is in mate-icon-theme and i see bluedevil-monolithic in the menu. I have only a bluez adapter, not a device. But i remember that it was working well w/o a device in my first test when i opened this report.
Try: qdbus org.kde.kded /kded org.kde.kded.loadModule bluedevil does that help ?
No, [rave@mother ~]$ qdbus org.kde.kded /kded org.kde.kded.loadModule bluedevil Cannot find 'org.kde.kded.loadModule' in object /kded at org.kde.kded Or is there a typo?
Was bluedevil-monolithic running when you tried it? (hint: it won't work if kded4 daemon isn't running, which usually autostarts when kde apps are running) Otherwise try: kdeinit4 && qdbus org.kde.kded /kded org.kde.kded.loadModule bluedevil
After a session start. [rave@mother ~]$ ps aux | grep blue root 1817 0.0 0.0 30200 4152 ? Ss 18:20 0:00 /usr/libexec/bluetooth/bluetoothd rave 5085 0.2 0.3 425824 25468 ? S 20:59 0:00 bluedevil-monolithic rave 5396 0.0 0.0 112692 2344 pts/0 S+ 21:00 0:00 grep --color=auto blue [rave@mother ~]$ qdbus org.kde.kded /kded org.kde.kded.loadModule bluedevil Cannot find 'org.kde.kded.loadModule' in object /kded at org.kde.kded [rave@mother ~]$ kdeinit4 && qdbus org.kde.kded /kded org.kde.kded.loadModule bluedevil Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... true Seems that bluedevil-monolithic doesn't start kdeinit4 [rave@mother ~]$ kill -15 5085 [rave@mother ~]$ ps aux | grep kde root 35 0.0 0.0 0 0 ? S 18:20 0:00 [kdevtmpfs] rave 5402 0.0 0.1 298992 15320 ? Ss 21:00 0:00 kdeini 4 rave 5405 0.0 0.3 507388 27356 ? Sl 21:00 0:00 kded4 rave 5422 0.0 0.1 226320 11280 ? Ss 21:00 0:00 kdeinit Running... rave 5427 0.0 0.1 230716 13708 ? S 21:00 0:00 klauncher [kdeinit] --new-startup rave 5429 0.0 0.1 239372 15796 ? S 21:00 0:00 kded --new-startup rave 5436 0.0 0.1 228784 12456 ? S 21:00 0:00 kio_file [kdeinit] file /tmp/ksocket-r rave 5662 0.0 0.0 112692 2304 pts/0 S+ 21:05 0:00 grep --color=auto kde [rave@mother ~]$ bluedevil-monolithic QSystemTrayIcon::setVisible: No Icon set Et voila, the icon is in systray. :) But when bluedevil-monolithic don't start kdeinit4 or kdeinit4 needs to be started first, i'm bit in doubt about my request. I have kdeinit (3) in autostart because i use good old and best kaffeine-0.8 for viewing dvb-c/t. Can this be cause the issue? I will check this.
Ok, it doesn't matter if kdenit (3) is in autostart or not. If using both in autostart the applet is invisible after session start, but [rave@mother ~]$ ps aux | grep kde root 35 0.0 0.0 0 0 ? S 18:20 0:00 [kdevtmpfs] rave 7355 0.1 0.1 298984 15360 ? Ss 21:22 0:00 kdeini 4 rave 7366 0.1 0.1 226312 11196 ? Ss 21:22 0:00 kdein rave 7383 0.4 0.2 426436 24356 ? S 21:22 0:00 kded4 rave 7395 0.1 0.1 239728 15512 ? S 21:22 0:00 kded rave 7655 0.0 0.0 112692 2360 pts/0 S+ 21:23 0:00 grep --color=auto kde [rave@mother ~]$ ps aux | grep blue root 1817 0.0 0.0 30200 4152 ? Ss 18:20 0:00 /usr/libexec/bluetooth/bluetoothd rave 7346 0.1 0.3 425824 25464 ? S 21:22 0:00 bluedevil-monolithic rave 7657 0.0 0.0 112692 2304 pts/0 S+ 21:23 0:00 grep --color=auto blue [rave@mother ~]$ killall bluedevil-monolithic [rave@mother ~]$ bluedevil-monolithic QSystemTrayIcon::setVisible: No Icon set .. and the applet is up.
(In reply to Rex Dieter from comment #4) > Mind doing a quick test? > > cp /usr/share/applications/kde4/bluedevil-monolithic.desktop > /etc/xdg/autostart/ > > and optionally: > > echo "OnlyShowIn=MATE;" >> /etc/xdg/autostart/bluedevil-monolithic.desktop > > and restart your session, would something like that suffice? Hello, Wolfgang emailed me to see if I could try this on my notebook with an internal adaptor. So I have run the commands above in MATE Terminal with sudo rights and it worked fine. The bluetooth monolithic is starting. The icon is displayed on the panel. Bluetooth radio is OFF by default which is fine by me. Clicking the icon and turning on works. As does everything else beyond that step normally. My notebook is running 32-bit MATE-Compiz Spin of Fedora. It is an hp compaq nx9105 business notebook. Bluedevil build:2.1-1 Kernel 3.17.8-300.fc21.i686 Device 002: ID 049f:0086 Compaq Computer Corp. Bluetooth Device" Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN Flags: bus master, fast devsel, latency 64, IRQ 17 Memory at e8104000 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge Kernel modules: ssb I would also like to support Wolfgang's request to add autostart capability for MATE upon install. While I don't mind running the commands you posted it would be simpler for less experienced users if it wasn't necessary. Thanks for your time and hard work on bluedevil for Fedora.
OK, I think I'll put that autostart in a subpkg, probably bluedevil-autostart, so only folks that want it can opt-in.
Thanks. Sounds good. Feel free to message me if you want me to test the additional package for you before it hits Bodhi. I'll stay email subscribed to this bug reference and also keep an eye on updates-testing anyhow.
(In reply to Rex Dieter from comment #12) > OK, I think I'll put that autostart in a subpkg, probably > bluedevil-autostart, so only folks that want it can opt-in. +1 :)
I forgot....thank you Rex. Maybe users from other non-product desktop are interested too. Maybe add "OnlyShowIn=MATE,XFCE,LXDE;" to desktop file, or "NotShowIn=KDE;GNOME;" Or without this tag, don't know what happens if a kde user installs the subpackage.
The autostart will contain NotShowIn=KDE; (since kde doesn't need it)
bluedevil-2.1-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/bluedevil-2.1-2.fc21
(In reply to Fedora Update System from comment #17) > bluedevil-2.1-2.fc21 has been submitted as an update for Fedora 21. > https://admin.fedoraproject.org/updates/bluedevil-2.1-2.fc21 Rex the RPMs work perfectly for me. I removed the autostart file created earlier prior to installing them. The autostart file was recreated and works. Bluedevil is loading and working as normal. Thanks again and kudos for doing it so quickly. Have a nice weekend
Package bluedevil-2.1-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bluedevil-2.1-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0734/bluedevil-2.1-2.fc21 then log in and leave karma (feedback).
bluedevil-2.1-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/bluedevil-2.1-2.fc20
bluedevil-2.1-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
bluedevil-2.1-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.