Well, not Plasma's but mine for sure.  I have been chasing my tail trying to 
reverse engineer processes/services/applications I do not want auto-running on 
a fresh Plasma installation and I'm fast losing the will to live.

I've installed plasma-meta plus some kde-apps meta packages as follows:

kde-apps/kdeadmin-meta
kde-apps/kdecore-meta
kde-apps/kdegraphics-meta
kde-apps/kdemultimedia-meta
kde-apps/kdenetwork-meta
kde-apps/kdepim-meta
kde-apps/kdeutils-meta
kde-apps/kwalletmanager
kde-frameworks/oxygen-icons
kde-plasma/plasma-meta

One of the above[1] brought in NetworkManager, which I don't use because for 
my use case there's nothing wrong with openrc netifrc scripts.  When I plug in 
a USB wireless adaptor nothing happens since it stays dormant, although its 
LED illuminates.  Then I enable it by starting 'net.wlp0s18f2u1' and at that 
point NM starts fighting over the wireless adaptor, resulting in the unpleasant 
phenomenon of dropping the connection every few minutes and changing its MAC 
address, consequently rendering it unusable with APs which implement ACL.

[1] kde-plasma/plasma-meta requires kde-plasma/powerdevil, which requires kde-
frameworks/networkmanager-qt, which requires net-misc/networkmanager, which 
requires net-misc/modemmanager

So I naively thought, let's try stopping NM (note:  the NetworkManager rc 
service is not set to run at any level, so something else is starting it).  
The moment I stop NM I find my logs being flooded with a storm of 'dbus failing 
to start obex', which bluez wants.  Note: I have not started a bluetooth 
service, or tried running bluetootctl, and BTW rfkill shows the bluetooth 
adaptor is soft blocked anyway.

So I now try to stop dbus and restart it, which results in losing access to 
any Plasma menu applications, so I can't launch any application.  It may be 
worth mentioning when I leave alone NM and just disable the USB adaptor from 
openrc, I also lose access to launching KDE applications (the error message 
when trying to launch an app from a terminal mentions a Qt error).

Could someone more knowledgeable in  Plasma/KDE shenanigans please explain how 
I can end up with a workable USB wireless dongle, which I can enable/disable 
at will?

-- 
Regards,

Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to