MEPIS Community Forum

The last updates removed network-manager and it's dependencies.
When trying to reinstall it refuses because it won't let you install network-manager without knm-runtime and if you try to install knm-runtime it won't because network-manager is not installed.

Am i the only one or one of very few that lost this with the last updates?

Whats an easy fix to get around this viscous circle besides wicd or similar?

I am using wicd for now but prefer the original network-manager.

That's weird--what exact updates were these?

Hi

Don't know if this is applicable to the problem the poster is having with his connection. The current version of pidgin in the Mepis community testing repos will remove the kde network manager and its dependencies. If the user has pidgin on his system and the testing repos enabled and did an update those packages would have been removed. I have not seen any other package(s) other than pidgin result in the removal of those packages.

HTH

Dale

yep it is the pidgin and testing being active that caused this..
Any suggestions for a fix?

Disable the CR, reload and repair by re-installing what you need. You may have to edit your synaptic preferences a little, like changing a setting under the Distribution tab. Once you have NM up and running again, which most likely will require removing pidgin, you can re-enable the CR, reload and try some dry-runs where you tick the checkbox to only download the packages to see what the effects of your chosen installation will be without actually changing anything. If necessary, try all 3 settings in the preferences, one of them may yield the results you desire.

Mike P

Sadly i have tried many combinations and it looks like i will be stuck with wicd for now if i want to keep pidgin. Something about NM and pidgin keeps breaking the system for now. Maybe a requirement for pidgin is the whole trouble.