SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Any file with a "." at the front of it's name is usually a hidden file that part of your user profile configuration on a Linux system. You probably don't want to delete these unless you have uninstalled the package relevant to it.
Easy solution: Don't use the GUI from within the root account.
Er Wrong.
This is created by the system when a normal user does something that requires root level access.
In the days of old you would have to run su in an xterm to get root level access for a X windows app, those days are long gone and now when you need that level of access it comes up with a nice dialog asking for the root password.
Unfortunately anything based on Qt will cause this directory to be created, and KDE is based on Qt so there is no avoiding it if you run KDE.
@chrisretusn
But this does not solve! Only provides a solution to live with it ( /.config ) ... The directory "/.config" should not be there, or should?
but also not solved ....
thanks
I was pointing out that there was an existing thread that discusses the same problem. That is all.
I am not running -current so have not seen this myself.
If you can't prevent it for the time being, how about making it a symlink to another location so that it would at least not write directly to the root directory?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.