Hello again, Nik! It's good to have friends online in situations like this. Yes I am already a member of the group netdev; I was not a member of the dialout group, so added myself to that group, too, just in case it might help. Those other commands are very nifty tools, especially nmtui. Myself, I want to go back to stone tools and live in a cave, and this makes me feel that I am already halfway there. Unfortunately, these did nothing whatsoever to change my network issues. I tried quitting and restarting tdenetworkmanager, tried running as my normal user, then had to go back to running as root, which I don't like, but I still need to do a few things today. Everything has been working just fine. I really don't want to reinstall my system just to correct this issue. Besides, when I booted up the machine with my handy flash drive (with the Devuan installation image), just to check my network connection, it seemed that only about every other time I rebooted that it showed available networks. Mind you, this is the Devuan installation image: sometimes it shows available networks, sometimes no networks at all. I live in an area that is surrounded by hundreds of local networks, and sometimes when I scan for networks, I find so many that they won't all fit on the screen. This makes no sense, for the Devuan installation image not to find networks. Is it possible that some hardware issue is causing my internal wifi antenna not to pick up networks? I also tried an old CCrane wifi antenna that I have kept, which has served me well for maybe twenty years, and still works with other machines; but alas, doesn't even register with this machine. Bill

On Monday 29 January 2024 16:09:48 deloptes via tde-users wrote: Well, until now I have managed to run my machine without using any non-free software; every once in a great while, I need some firmware update, but even there I have managed to steer clear of non-free and proprietary crap. It may be that I will eventually have to surrender. There is one other detail to add: which is, that I remember what you suggested in an earlier post about installing a Linux system to a flash drive. As it happens, I had a friend who kept pestering me about Linux, but my gut feeling is, this won't last, then she will have installed Linux, discovers she doesn't like it, doesn't have the patience to learn, and so regrets having wiped out a running Windoze system. So I thought, why not give this a try? I have installed to a flash drive before (complete with root, swap and home partitions), and it was able to run my desktop for at least 6 months or so. Then I decided that it was too slow for everyday use (and it was an older desktop machine), so I installed to the internal hard drive like usual. (The flash drive, after a few more months, became corrupted and unusable, which is no doubt because they aren't made to take that kind of stress.) But it was an instructive experiment. In this case, I thought I might get some practice at doing it again, as I must do some travelling in the future, and it would be nice to carry around a smaller version of my own machine in my pocket, so that in a pinch I can borrow somebody else's hardware, but still have my own machine to use, so to speak, and meanwhile keep my laptop safely tucked away in my bags, in a locker, wherever. This time, after installing to the flash drive, I did experience some peculiar issues. My hunch was that it was due to the fact of two UEFI partitions when I booted up -- one on the flash drive, one on my machine. (When I did this before, there the UEFI partitions were just starting to appear in newer machines, so this was not an issue back then.) It took another few reboots before I had problems, but then this network problem developed. I did try out the flash drive on my machine, of course, just to be sure that it worked as intended, but it was another couple days before I started having this network problem (of having to start tdenetworkmanager as root). I don't know whether my experimentation with installing to a flash drive has anything to do with it, but it's the only other thing that I can think of. Also, I forgot to mention, there was a full moon the other night, but that has never before affected my network. Bill

Hi Bill! Anno domini 2024 Mon, 29 Jan 15:50:21 -0800 William Morder via tde-users scripsit: what does 'dmesg|grep wlan' say, when it tries to connect? It looks like I have a simillar issue: [ 9.891861] wlan0: authenticate with e8:48:b8:e1:89:da [ 9.902526] wlan0: send auth to e8:48:b8:e1:89:da (try 1/3) [ 9.918070] wlan0: authenticated [ 9.919082] wlan0: associate with e8:48:b8:e1:89:da (try 1/3) [ 9.935475] wlan0: RX AssocResp from e8:48:b8:e1:89:da (capab=0x11 status=0 aid=1) [ 9.937940] wlan0: associated [ 55.012840] wlan0: deauthenticating from e8:48:b8:e1:89:da by local choice (Reason: 3=DEAUTH_LEAVING) [ 56.868760] wlan0: authenticate with e8:48:b8:e1:89:da [ 56.880559] wlan0: send auth to e8:48:b8:e1:89:da (try 1/3) [ 56.883686] wlan0: authenticated [ 56.887070] wlan0: associate with e8:48:b8:e1:89:da (try 1/3) [ 56.889993] wlan0: RX AssocResp from e8:48:b8:e1:89:da (capab=0x11 status=0 aid=1) [ 56.893218] wlan0: associated from sec. 9 to 55 he blue gear keeps turning. Usally it connects after 1-2 minutes, in this case I reconnected manually and it connected after 2 secs. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...

On Sat February 3 2024 08:37:00 William Morder via tde-users wrote: <snip> How about the content of your .trinity directory tree Bill? Running tdenetworkmanager as root may have changed ownership of some crucial file that your regular user account was unable to change back. --Mike

On Sat February 3 2024 09:11:37 William Morder via tde-users wrote: <snip> Hi Bill, If it happens again see what you can get from command line tools and log files but try to avoid running tdenetworkmanager as root. But the reality is we may never know what was causing the earlier network problem. Maybe your quantums got entangled, or unentangled. --Mike