1 Like
Hi @srikk, and welcome!
The last makes it sound like some kind of permissions problem.
Please see [HowTo] Provide System Information, [HowTo] post screenshots and links, and [HowTo] Increase your chances of solving your issue to know how to provide better information, so you can get more help with the problem.
The username may be the same but what about the UID?
This is most likely because the UID of the new user does not match the UID on the resused home folder.
It will be obvious if there’s no username which matches to filesystem UID when you list the content of /home.
$ ls -l /home
total 4
drwx------ 41 1001 1001 4096 Feb 6 16:22 username
If /home/username owner:group is numbers you know this is the issue
To fix it you login as root. Then run (replace username with the username in question)
# chown username:username /home/username -R
2 Likes
This a partial output of inxi:
System:
Kernel: 5.15.19-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=eba91160-e9de-4847-9943-73d97f3de82a rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: Cinnamon 5.2.7 tk: GTK 3.24.31 dm: LightDM 1.30.0
Distro: Manjaro Linux base: Arch Linux
CPU:
Info: model: Intel Core2 6420 bits: 64 type: MCP arch: Core Merom family: 6
model-id: 0xF (15) stepping: 6 microcode: 0xD0
Graphics:
Device-1: Intel 82946GZ/GL Integrated Graphics driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:2972 class-ID: 0380
Device-2: NVIDIA G73 [GeForce 7300 GT] driver: nouveau v: kernel
bus-ID: 01:00.0 chip-ID: 10de:0393 class-ID: 0300
Display: server: X.Org 1.21.1.3 driver: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa display-ID: :1 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.0x9.4")
s-diag: 449mm (17.7")
Monitor-1: DVI-I-1 res: 1440x900 hz: 60 dpi: 89
size: 410x260mm (16.1x10.2") diag: 485mm (19.1")
Message: Unable to show advanced data. Required tool glxinfo missing.
I did check this and the UID is the same, both in passwd file and in the output of ls -lhn (1000).
No, ls -l does not show number, it shows the user name.
So I believe that the problem is elsewhere!!
Regards,
Srikanth
what does the journal say?
journalctl -xe -u dbus-org.freedesktop.home1.serviceno entries
But this is the last few lines of journalctl -xe
░░
░░ The job identifier is 2851.
Feb 06 21:19:14 srikanth-pc dbus-daemon[478]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=479 comm="/usr/bin/NetworkManager --no-daemon ")
Feb 06 21:19:14 srikanth-pc dbus-daemon[478]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 06 21:19:14 srikanth-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 21:19:14 srikanth-pc kernel: kauditd_printk_skb: 5 callbacks suppressed
Feb 06 21:19:14 srikanth-pc kernel: audit: type=1130 audit(1644162554.624:174): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 21:19:14 srikanth-pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░
░░ The job identifier is 2851.
Feb 06 21:19:24 srikanth-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 21:19:24 srikanth-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Feb 06 21:19:24 srikanth-pc kernel: audit: type=1131 audit(1644162564.637:175): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
journalctl -u dbus-org.freedesktop.home1.service
-- No entries --
I just recalled something about lightdm display manager.
There is an old topic - something which - for some - is a workaround
/etc/lightdm/lightdm.conf
[LightDM]
logind-check-graphical=true
If you get stuck in loop in which you type your correct user and password but the screen goes black and the you are back in the login after every attempt, running
rm ~/.Xauthority(or the stuck user’s problematic.Xauthority) may fix the issue.
So you may have a look at:
/var/log/lightdm/.log
/var/log/x.log
I tried this, but it still fails.
I had a look at /var/log/lightdm/lightdm.log. This is a partial listing of it:
35 │ [+0.09s] DEBUG: User /org/freedesktop/Accounts/User1000 added
36 │ [+1.35s] DEBUG: Got signal 10 from process 586
37 │ [+1.35s] DEBUG: XServer 0: Got signal from X server :0
38 │ [+1.35s] DEBUG: XServer 0: Connecting to XServer :0
39 │ [+1.35s] DEBUG: Seat seat0: Display server ready, starting session authentication
40 │ [+1.35s] DEBUG: Session pid=729: Started with service 'lightdm-greeter', username 'lightdm'
41 │ [+1.41s] DEBUG: Session pid=729: Authentication complete with return value 0: Success
42 │ [+1.41s] DEBUG: Seat seat0: Session authenticated, running command
43 │ [+1.41s] DEBUG: Session pid=729: Running command /usr/bin/slick-greeter
44 │ [+1.41s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
45 │ [+1.41s] DEBUG: Session pid=729: Logging to /var/log/lightdm/seat0-greeter.log
46 │ [+2.02s] DEBUG: Activating VT 7
47 │ [+2.02s] DEBUG: Activating login1 session c1
48 │ [+2.02s] DEBUG: Seat seat0 changes active session to c1
49 │ [+2.02s] DEBUG: Session c1 is already active
50 │ [+3.30s] DEBUG: Greeter connected version=1.30.0 api=1 resettable=false
51 │ [+3.83s] DEBUG: Greeter start authentication for srikk
52 │ [+3.83s] DEBUG: Session pid=976: Started with service 'lightdm', username 'srikk'
53 │ [+3.86s] DEBUG: Session pid=976: Got 1 message(s) from PAM
54 │ [+3.86s] DEBUG: Prompt greeter with 1 message(s)
55 │ [+14.57s] DEBUG: Continue authentication
56 │ [+14.61s] DEBUG: Session pid=976: Authentication complete with return value 0: Success
57 │ [+14.61s] DEBUG: Authenticate result for user srikk: Success
58 │ [+14.61s] DEBUG: User srikk authorized
59 │ [+14.67s] DEBUG: Greeter requests session cinnamon2d
60 │ [+14.67s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
61 │ [+14.67s] DEBUG: Terminating login1 session c1
62 │ [+14.68s] DEBUG: Session pid=729: Sending SIGTERM
63 │ [+14.71s] DEBUG: Greeter closed communication channel
64 │ [+14.71s] DEBUG: Session pid=729: Exited with return value 0
65 │ [+14.71s] DEBUG: Seat seat0: Session stopped
66 │ [+14.71s] DEBUG: Seat seat0: Greeter stopped, running session
67 │ [+14.71s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
Does this give any hints?
I tried this, but it failed .
This is a partial journalctl:
Feb 07 12:29:17 srikanth-pc systemd-logind[457]: New session c4 of user lightdm.
Feb 07 12:29:17 srikanth-pc systemd[1]: Started Session c4 of User lightdm.
Feb 07 12:29:17 srikanth-pc systemd[1]: session-7.scope: Deactivated successfully.
Feb 07 12:29:17 srikanth-pc audit[28243]: USER_START pid=28243 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:session_o>
Feb 07 12:29:17 srikanth-pc systemd-logind[457]: Removed session 7.
Feb 07 12:29:17 srikanth-pc slick-greeter-check-hidpi[28249]: Window scale: 1
Feb 07 12:29:17 srikanth-pc slick-greeter-set-keyboard-layout[28252]: Current keyboard configuration: rules: evdev
model: pc105
layout: us
Feb 07 12:29:17 srikanth-pc slick-greeter-set-keyboard-layout[28252]: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '->
Feb 07 12:29:17 srikanth-pc slick-greeter-set-keyboard-layout[28252]: Result: Warning! Multiple definitions of keyboard model
Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
Using command line, ignoring X server
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
Feb 07 12:29:17 srikanth-pc slick-greeter-set-keyboard-layout[28252]: New keyboard configuration: rules: evdev
model: pc105
layout: us
Feb 07 12:29:17 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.login1.suspend-multiple-sessions']
Feb 07 12:29:17 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=28246 user='lightdm' groups=lightdm seat='seat0' session='>
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=28246 user='lightdm' groups=lightdm seat='seat0' session='>
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=28246 user='lightdm' groups=lightdm seat='seat0' session='>
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=28246 user='lightdm' groups=lightdm seat='seat0' session='>
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 12:29:18 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=28246 user='lightdm' groups=lightdm seat='seat0' session='>
lines 21319-21351/21351 (END)
Since you are authorized - I believe this is a permission issue due to the reused home folder.
Have you tried to create a new user an login as that user?
At the display manager - switch to TTY and login as root - then create a new user (the example adds the new user using the same groups as the installer thus creating a superuser)
useradd -mUG network,lp,wheel newuserI tried this. I can login into newuser.
Then it is confirmed that you have a permission problem with your recycled home folder.
When logged in as root you should fix the owner ship of the entire home folder (replace user with the actual user in question)
sudo chown user:user -R /home/userTried this too, with the proper user id, same result 
.
here is the partial listing of journalctl:
7 20:24:01 srikanth-pc lightdm[35684]: gkr-pam: unable to locate daemon control file
Feb 07 20:24:01 srikanth-pc audit[35684]: USER_AUTH pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication grantors=pam_shells,pam_faillock,p>
Feb 07 20:24:01 srikanth-pc audit[35684]: USER_ACCT pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permi>
Feb 07 20:24:01 srikanth-pc lightdm[35684]: gkr-pam: stashed password to try later in open session
Feb 07 20:24:01 srikanth-pc kernel: kauditd_printk_skb: 7 callbacks suppressed
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1100 audit(1644245641.877:329): pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication granto>
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1101 audit(1644245641.877:330): pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=p>
Feb 07 20:24:01 srikanth-pc systemd[1]: Stopping Session c5 of User lightdm...
Feb 07 20:24:01 srikanth-pc lightdm[35608]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1106 audit(1644245641.947:331): pid=35608 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:session_close grantor>
Feb 07 20:24:01 srikanth-pc audit[35608]: USER_END pid=35608 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct=">
Feb 07 20:24:01 srikanth-pc audit[35608]: CRED_DISP pid=35608 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm>
Feb 07 20:24:01 srikanth-pc systemd[1]: session-c5.scope: Deactivated successfully.
Feb 07 20:24:01 srikanth-pc systemd[1]: Stopped Session c5 of User lightdm.
Feb 07 20:24:01 srikanth-pc systemd[1]: session-c5.scope: Consumed 1.495s CPU time.
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1104 audit(1644245641.950:332): pid=35608 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_>
Feb 07 20:24:01 srikanth-pc audit[35684]: CRED_ACQ pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permi>
Feb 07 20:24:01 srikanth-pc audit[35684]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=8 a1=7ffe813605e0 a2=4 a3=3e8 items=0 ppid=574 pid=35684 auid=1000 uid=0 gid=0 eu>
Feb 07 20:24:01 srikanth-pc audit: PROCTITLE proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003132003231
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1103 audit(1644245641.957:333): pid=35684 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_>
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1006 audit(1644245641.957:334): pid=35684 uid=0 subj==unconfined old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=>
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1300 audit(1644245641.957:334): arch=c000003e syscall=1 success=yes exit=4 a0=8 a1=7ffe813605e0 a2=4 a3=3e8 items=0 ppid=574 pid=>
Feb 07 20:24:01 srikanth-pc kernel: audit: type=1327 audit(1644245641.957:334): proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003132003231
Feb 07 20:24:01 srikanth-pc systemd-logind[457]: Removed session c5.
Feb 07 20:24:01 srikanth-pc lightdm[35684]: pam_unix(lightdm:session): session opened for user srikk(uid=1000) by (uid=0)
Feb 07 20:24:01 srikanth-pc systemd-logind[457]: New session 11 of user srikk.
Feb 07 20:24:01 srikanth-pc systemd[1]: Started Session 11 of User srikk.
Feb 07 20:24:01 srikanth-pc lightdm[35684]: pam_env(lightdm:session): deprecated reading of user environment enabled
Feb 07 20:24:02 srikanth-pc audit[35684]: USER_START pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_>
Feb 07 20:24:02 srikanth-pc lightdm[35684]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Feb 07 20:24:02 srikanth-pc kernel: audit: type=1105 audit(1644245642.013:335): pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=PAM:session_open grantors=pam_loginuid,>
Feb 07 20:24:02 srikanth-pc audit[35684]: USER_LOGIN pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=login id=1000 exe="/usr/bin/lightdm" hostname=srikanth-pc addr=? t>
Feb 07 20:24:02 srikanth-pc kernel: audit: type=1112 audit(1644245642.063:336): pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=login id=1000 exe="/usr/bin/lightdm" ho>
Feb 07 20:24:02 srikanth-pc audit[35684]: USER_LOGOUT pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=logout id=1000 exe="/usr/bin/lightdm" hostname=srikanth-pc addr=?>
Feb 07 20:24:02 srikanth-pc lightdm[35684]: pam_unix(lightdm:session): session closed for user srikk
Feb 07 20:24:02 srikanth-pc audit[35684]: USER_END pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_u>
Feb 07 20:24:02 srikanth-pc audit[35684]: CRED_DISP pid=35684 uid=0 auid=1000 ses=11 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_failloc>
Feb 07 20:24:02 srikanth-pc systemd-logind[457]: Session 11 logged out. Waiting for processes to exit.
Feb 07 20:24:02 srikanth-pc kernel: nouveau 0000:01:00.0: DRM: 0xC298: Parsing digital output script table
Feb 07 20:24:03 srikanth-pc audit[35705]: CRED_ACQ pid=35705 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm">
Feb 07 20:24:03 srikanth-pc lightdm[35705]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=967) by (uid=0)
Feb 07 20:24:03 srikanth-pc systemd-logind[457]: New session c6 of user lightdm.
Feb 07 20:24:03 srikanth-pc systemd[1]: Started Session c6 of User lightdm.
Feb 07 20:24:03 srikanth-pc audit[35705]: USER_START pid=35705 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct=>
Feb 07 20:24:03 srikanth-pc systemd[1]: session-11.scope: Deactivated successfully.
Feb 07 20:24:03 srikanth-pc systemd-logind[457]: Removed session 11.
Feb 07 20:24:03 srikanth-pc slick-greeter-check-hidpi[35712]: Window scale: 1
Feb 07 20:24:03 srikanth-pc slick-greeter-set-keyboard-layout[35715]: Current keyboard configuration: rules: evdev
model: pc105
layout: us
Feb 07 20:24:03 srikanth-pc slick-greeter-set-keyboard-layout[35715]: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '-layout', 'us', '-variant', '', '-option>
Feb 07 20:24:03 srikanth-pc slick-greeter-set-keyboard-layout[35715]: Result: Warning! Multiple definitions of keyboard model
Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
Using command line, ignoring X server
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
Feb 07 20:24:03 srikanth-pc slick-greeter-set-keyboard-layout[35715]: New keyboard configuration: rules: evdev
model: pc105
layout: us
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.login1.suspend-multiple-sessions']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Feb 07 20:24:03 srikanth-pc polkitd[455]: <no filename>:4: subject=[Subject pid=35708 user='lightdm' groups=lightdm seat='seat0' session='c6' local=true active=true]
Has it got something to do with policy settings?
Or some X server setting in my home directory?
No one can’t possible know or deduct what setting in your reused home folder in causing this - suffice to say that we have narrowed it down to your home folder.
I really don’t know - instead of using more time on it - just transfer the file from the non working user to the working user and be done with it.
I cannot be of further help and have no further to add.
You best bet would be to copy things 1-by-1 and narrow it down that way. But there’s no real other, or easier way to do it.