On Sat February 3 2024 08:37:00 William Morder via tde-users wrote: <snip> > 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? 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 ____________________________________________________ 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
