On Fri 23 Apr 2021 at 10:49:00 (+0100), Richmond wrote: > Cindy Sue Causey <butterflyby...@gmail.com> writes: > > > Questions where answers might help come to mind. Primarily, has this > > always occurred, or did it just start up in the last couple days? > > It has occured since installing debian (10). Prior to that I was using > opensuse. > > > I'm on a new old secondhand laptop today. Just started using it > > yesterday. It's doing similar, but I can trigger it back on via > > "wicd-curses". A quick CTRL+R (refresh) for no particular reason and > > then CTRL+C (connect), and I'm back up and running. > > I don't think I am using Wicked, if that is the equivalent of the > opensuse Wicked. I think I am using network manager.
JFTR there's no connection (pun, sorry) between Wicd¹ and Wicked.² Confusion is compounded by their identical pronunciation. Wicked would claim to be a superset of NetworkManager. Wicd is a simple connection manager, handling just one connection at a time. In any case, wicd's days are numbered unless and until it moves forward from Python2. There's a Python3 version in experimental, but the hiatus might not be good for sustaining its popularity. ¹ acronym, Wireless Interface Connection Daemon ² "No REST for the wicked", motivational joke after SUSE rejected using REST, a REpresentational State Transfer interface. Cheers, David.
