blueman-applet logs errors to console during start and usage of this applet when networkmanager is not installed. Reproducible: Always Steps to Reproduce: 1. install net-wireless/bluez-5.50-r1 2. make sure that there is no net-misc/networkmanager installed 3. run blueman-applet Actual Results: Error message appears: blueman-applet version 2.1.alpha3 starting Stale PID, overwriting blueman-applet 09.55.27 ERROR PluginManager:90 load_plugin: Unable to load plugin module NMDUNSupport Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/blueman/main/NetworkManager.py", line 6, in <module> gi.require_version('NM', '1.0') File "/usr/lib64/python3.6/site-packages/gi/__init__.py", line 130, in require_version raise ValueError('Namespace %s not available' % namespace) ValueError: Namespace NM not available Expected Results: No errors will be produced during blueman-applet startup I can fix the prbolem when I install net-misc/networkmanager-1.14.6 So I think it should be a dependency of the bluez package.
That'd be a circular dependency.
I fixed this last year already in master and in alpha3 [1]. You do not say which version of blueman you are running as the problem lies with it. [1] https://github.com/blueman-project/blueman/commit/ad5af0996a06f9e2f3610f0cd812a6cd9c76ca11
I think the dep, if needed, would need to be in blueman, not bluez... or am I missing something? :/
@Sander Sweers Blueman version is mentioned in the error output: > blueman-applet version 2.1.alpha3 @Pacho Ramos It seems you are right.
@enca, The alpha3 tarball as released on github includes my fix so *if* it would crash it should have crashed with ImportError. This is not a Gentoo problem and if you can reproduce it with blueman-2.1_alpha3-r1.ebuild open an issue https://github.com/blueman-project/blueman/issues and we'll have a look at it. The ebuild already pulls in NM when the `network` useflag is set. The alpha3 release and master do now require NM introspection but the use flag is not required on networkmanager atm. Would be nice if someone can fix that :-)
I have had the same problem: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/blueman/main/PluginManager.py", line 88, in load_plugin importlib.import_module(self.module_path.__name__ + ".%s" % plugin) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib64/python3.6/site-packages/blueman/plugins/applet/NMDUNSupport.py", line 3, in <module> from blueman.main.NetworkManager import NMDUNConnection File "/usr/lib64/python3.6/site-packages/blueman/main/NetworkManager.py", line 8, in <module> raise ImportError('NM python bindings not found.') ImportError: NM python bindings not found. Only after having installed net-misc/networkmanager-1.18.4-r3 the error is gone away. I got the same error both installing blueman via emerge and via source code. Regards
FWICS it's not a fatal error, so I don't think we need to do anything here. I suppose blueman could be a little more friendly about NM being missing.
