Didn't see that, didn't scroll enough to see it I think, would that stop Xfce from logging in?skidoo wrote: ↑Sun Jan 27, 2019 4:05 amdoesn't look "ok" to methis can result from su or sudo (vs gksu) being used to launch a graphical program.
Code: Select all
drwx------ 2 root root 4096 gen 11 12:41 .gvfs
Would the unreadable (by anyone other than root) status of .gvfs interfere with desktop session login?
(asking b/c I wonder, but haven't tested this)
The kernel problem with recent updates has been solved. Find the solution here
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities
-- Introducing our new Website
-- MX Linux on social media: here
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules
I just now tested. No, mismatched ownership of that particular file doesn't prevent desktop login.would that stop Xfce from logging in?
find /home/demo -iname .gvfs
^--------- doesn't exist in a fresh install, so
sudo touch /home/demo/.gvfs
^------v session logout, able to login again without a hiccup
Knowing that at least one file is affected & since others might be also, I would:
cd ~ && find . \! -user $USER -print
cd ~ && find \! -readable
sudo chown -R myusername:myusername /home/myusername
You're right. I tryed and it didn't solve the problem.
Sorry for my inexperience but should I give this commands from my root folder or from my home folder? I don't want to mess up my configuration since I have done this many times in the past