Description of problem: blueberry runs under both python2 and python3 and spawns two instances of rfkill event. Version-Release number of selected component (if applicable): blueberry-1.1.20-1.fc27.noarch rfkill-0.5-10.fc27.x86_64 How reproducible: Always. Steps to Reproduce: 1. open Bluetooth Device Manager 2. toggle "Show a tray icon" switch off and on 3. ps axf Actual results: 7165 ? S 0:00 /usr/bin/python3 /usr/bin/blueberry 7166 ? Sl 0:00 \_ /usr/bin/python2 /usr/lib/blueberry/blueberry.py 7174 ? S 0:00 \_ python2 /usr/lib/blueberry/safechild /usr/sbin/rfkill event 7175 ? S 0:00 | \_ /usr/sbin/rfkill event 7224 ? S 0:00 \_ /usr/bin/python3 /usr/bin/blueberry-tray 7226 ? Sl 0:00 \_ /usr/bin/python2 /usr/lib/blueberry/blueberry-tray.py 7236 ? S 0:00 \_ python2 /usr/lib/blueberry/safechild /usr/sbin/rfkill event 7237 ? S 0:00 \_ /usr/sbin/rfkill event Expected results: Only one instance of rfkill event should be running. Only python3 or only python2 should be running blueberry. Additional info: Possible duplicate: bug #1530218.
It only spawns one here :-) 1472 ? Sl 0:06 \_ nm-applet 1474 ? Sl 1:29 \_ python3 /usr/bin/dnfdragora-updater 1481 ? Sl 0:00 \_ blueberry-obex-agent 1483 ? Sl 0:02 \_ nemo-desktop 1485 ? Sl 0:00 \_ /usr/libexec/polkit-gnome-authentication-agent-1 1488 ? Sl 0:00 \_ /usr/bin/python3 /usr/bin/cinnamon-killer-daemon 1678 ? S 0:00 \_ /usr/bin/python3 /usr/bin/blueberry-tray 1680 ? Sl 0:00 | \_ /usr/bin/python2 /usr/lib/blueberry/blueberry-tray.py 1686 ? S 0:00 | \_ python2 /usr/lib/blueberry/safechild /usr/sbin/rfkill event 1689 ? S 0:00 | \_ /usr/sbin/rfkill event 1679 ? Sl 1:28 \_ cinnamon-screensaver 740 ? Ssl 0:00 /usr/libexec/colord Can you file it upstream as well please? https://github.com/linuxmint/blueberry/issues
Well, for me it's 100% reproducible, just flip the systray switch off and on. Filed https://github.com/linuxmint/blueberry/issues/50 . I'm using MATE desktop.
Apparently it's all fine. The second rfkill instance comes from the settings dialog and goes away when it's closed. Sorry for the false alarm.