Last Tumbleweed update (December 13 2020) blocks user with UID 1000 from loggin in. Other users can log in. Fortunately, I had another ID that I use with ssh -X vidar@127.0.0.1 to access my main ID. I kind of remember this problem occurring earlier, but can not locate any information on it. I have this situations on two machines. Just plain tumbleweed with no propritary graphic driver.
I am not noticing any problem. I am normally UID=1001, but the user with UID=1000 is working fine.
Is there anything different about that user (different shell, for example)?
Are you talking about a graphic login or a command line login (both work here).
Is there any error message when you try?
Only the graphical login is not possible, the process starts and then exits, leaving the sddm. Same for all posibilities of sessions, but I use “KDE plasma”, and bash-shell. Both old users and new that I create can login, but not my usual ID with UID 1000. I do not see an obvious error message. I have a part of the systemd journal, but I do not see an option for an attachement here. Sorry, I do not often appear here.
Check permissions. What you describe is similar to the behavior if the home directory is owned by a different user or the home directory doesn’t actually exist.
That would make a CLI login also impossible and he says “Only the graphical login is not possible”.
In my experience, a CLI login works in those cases. It’s just that you cannot write to the home directory. And if there is no home directory, I think you login with the root directory as $HOME on a CLI login, though it has been a while since I tried that.
Well, let him post (as root)
ls -l /home
ls -ln /home
linux-gkwu:/home/vidar # ls -l /home
total 0
drwxr-xr-x 1 svartur users 222 Dec 13 23:04 svartur
drwxr-xr-x 1 vg users 556 Dec 14 14:29 vg
drwxr-xr-x 1 vidar users 1906 Dec 14 21:09 vidar
linux-gkwu:/home/vidar # ls -ln /home
total 0
drwxr-xr-x 1 1002 100 222 Dec 13 23:04 svartur
drwxr-xr-x 1 1001 100 556 Dec 14 14:29 vg
drwxr-xr-x 1 1000 100 1906 Dec 14 21:09 vidar
I can not access “vidar” directly with a gui-login (yes I can do it in konsole) so I am using “vg” or “svartur” created at very different times to access vidar via ssh -X vidar@127.0.01 without a problem, to have all my configurations. I see nothing I notice as suspicious in /var/log/Xorg.1.log. Inside the home directory of vidar all seems to have right permissions. About a 2 years ago a similar situation happended in tumbleweed, but then I found on the web directions how to empty one system file, but now I can neither remember the file nore find this posting on the web.
Error FOUND: I was installing Intel oneAPI last weekend, and to activate it in the bash-shell I added in .bashrc:
#----------------------------------------------
OneAPI ifort + MKL
. /opt/intel/oneapi/setvars.sh > /dev/null
#----------------------------------------------
ifort + mkl
#. /opt/intel/bin/compilervars.sh intel64
#----------------------------------------------
gfortran + mkl
#. /opt/MKL/mkl/bin/mklvars.sh intel64
#----------------------------------------------
the added “> /dev/null” was to get rid of a greeting that interferred with rsync. When I block this sentence all works fine. What is the best method to block this greeting message from oneAPI?
Hi
According to the api notes, your sourcing for sudo or root user? It should be in you home directory and sourced.
What is in that script that is hanging if you run manually?
OK, I think we are now talking about the problems Intel oneAPI is making.
I have no idea what that is, thus I leave it to others to help you.
Maybe doublecheck your UID?
Could you actually want to be using UID 100?
TSU