¡Hola Cristian! El 2016-08-17 a las 14:03 +0200, Cristian Ionescu-Idbohrn escribió:
On Wed, 17 Aug 2016, Maximiliano Curia wrote:I should probably add that this happened as a result of the upgrade from wheezy to jessie.
plasma-nm depends on network-manager, but does not conflict with wicd-kde, or the other way around. So, one ends up with the two packages competing/raceing with eachother. Very shaky wireless authentication process.I think this needs to be addressed at the network-manager/wicd level, this issue is not specific to the plasma desktop, and the dependencies allow the removal of plasma-nm.
So, which package should this bug be transfered to?
Both, I guess. You can reassign a bug to multiple packages (version tracking is lost doing this), or simply send a one new bug each. I'm not sure if the log is still relevant to the network-manager and wicd maintainers, so it might be better to send two new bugs.
Nonetheless, plasma-nm has a hard dependency to network-manager, which in "worst" case scenario (no other package depends on network-manager) will force network-manager installation without caring if wicd-kde is installed, thus causing non-trivial problems for debian stable users. And that's what needs to be resolved in the jessie release, IMO.
plasma-nm uses network-manager, without it it is useless. So the hard dependency is needed here. plasma-nm is recommended by kde-standard and task-kde-desktop, so it can be easily uninstalled. That's as far as we can go from the kde packages to allow the user to manage it's system using something different than network-manager.
We could consider having another "plasma network widget" as an alternative to plasma-nm, but that would need to be well maintained first.
Happy hacking, -- "By definition, when you are investigating the unknown, you do not know what you will find" -- The Ultimate Principle Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: Digital signature