On Tuesday 30 January 2024 08:14:10 Dr. Nikolaus Klepp via tde-users wrote: > > 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 Never got to try these out, as the problems got too annoying for me to ignore. After wrestling with this issue for days, trying different strategies to trace the source(s) of these problems, I decided to do a fresh installation. At the moment, I have no time whatsoever to waste, but I also need a working computer, under my own control, in order to keep my life together. So I spent the better part of two days reinstalling my system in the manner typical of most mortals; what is usually recommended, that is: that overly cautious, piecemeal way; one-thing-at-a-time, to make sure I didn't make any careless mistakes. Then I copied over my personal stuff gradually. I created a new user folder, copied everything over there, then copied back to my actual user folder, once I had completed the installation. This has generally worked before to filter out similar problems, and it worked again. My network is back to normal; my system appears to be running in its customary way, obeying my wishes. I believe that I might find what causes these issues somewhere in those dot files at the bottom of my home folder. Everything else can be copied from backups except those files. I will assume that it's not such innocuous files such as my user icon, and dot folders don't seem to affect the system at all; I only need to get into the individual dot folders when there's an issue with a specific program -- for example, audacity, which periodically needs to be sanitized, as whatever's inside may get corrupted, and things stop working right. But that is just for that particular program, and doesn't affect other parts of the system, such as networking. Whatever affects my network (the issues described at length in previous posts) must be in these hidden files at the bottom of the home folder. .bash_history .bash_logout .bashrc .DCOPserver_<my_top_secret_host_name>_:0 .DCOPserver_<my_top_secret_host_name>__0 .dmrc .ICEauthority .mcoprc .profile .sudo_as_admin_successful .tderc .Xauthority .xsession-errors Among these suspects, I would suppose bash, the dcop server lines wiith my hostname, and after that I am just shooting in the dark. Any suggestions? Bill ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
