Unable to log-in after an update

Support GNOME
1

Recently I’ve ran an update on my laptop and now am unable to log in to the DE. After putting in the password it just greys-out the input field and does nothing (tried on both xorg and wayland).

Here’s the journal logs from the moment I tried to log in:

Jul 05 11:45:40 manjaro systemd-journald[366]: System Journal (/var/log/journal/094f27daba6249019fcb289da5bb296a) is 24M, max 4G, 3.9G free.
Jul 05 11:45:41 manjaro systemd-journald[366]: Received client request to rotate journal, rotating.
Jul 05 11:45:41 manjaro systemd-journald[366]: Vacuuming done, freed 0B of archived journals from /var/log/journal/094f27daba6249019fcb289da5bb296a.
Jul 05 11:45:41 manjaro sudo[2934]: pam_unix(sudo:session): session closed for user root
Jul 05 11:45:44 manjaro sudo[2947]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-2947) opened.
Jul 05 11:45:44 manjaro sudo[2947]:    owner : TTY=tty2 ; PWD=/home/owner ; USER=root ; COMMAND=/usr/bin/journalctl --vacuum-time=1s
Jul 05 11:45:44 manjaro sudo[2947]: pam_unix(sudo:session): session opened for user root(uid=0) by owner(uid=1000)
Jul 05 11:45:44 manjaro sudo[2947]: pam_unix(sudo:session): session closed for user root
Jul 05 11:45:46 manjaro sudo[2954]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-2954) opened.
Jul 05 11:45:46 manjaro sudo[2954]:    owner : TTY=tty2 ; PWD=/home/owner ; USER=root ; COMMAND=/usr/bin/journalctl --vacuum-time=6h
Jul 05 11:45:46 manjaro sudo[2954]: pam_unix(sudo:session): session opened for user root(uid=0) by owner(uid=1000)
Jul 05 11:45:46 manjaro sudo[2954]: pam_unix(sudo:session): session closed for user root
Jul 05 11:45:51 manjaro kernel: rfkill: input handler disabled
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Successfully made thread 2314 of process 2296 owned by '120' high priority at nice level 0.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 7 threads of 4 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 6 threads of 3 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 6 threads of 3 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Successfully made thread 2314 of process 2296 owned by '120' RT at priority 20.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 7 threads of 4 processes of 1 users.
Jul 05 11:45:51 manjaro systemd[1]: session-11.scope: Deactivated successfully.
Jul 05 11:45:51 manjaro systemd-logind[805]: Removed session 11.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Successfully made thread 2314 of process 2296 owned by '120' high priority at nice level 0.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 7 threads of 4 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 6 threads of 3 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 6 threads of 3 processes of 1 users.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Successfully made thread 2314 of process 2296 owned by '120' RT at priority 20.
Jul 05 11:45:51 manjaro rtkit-daemon[1226]: Supervising 7 threads of 4 processes of 1 users.
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: > Warning:          Unsupported maximum keycode 708, clipping.
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: >                   X11 cannot support keycodes above 255.
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: > Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: > Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Jul 05 11:45:51 manjaro org.gnome.Shell.desktop[3029]: Errors from xkbcomp are not fatal to the X server
Jul 05 11:45:52 manjaro gnome-shell[2296]: Object .MetaInputDeviceNative (0x7ff69c0936e0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                           == Stack trace for context 0x561a40c5dad0 ==
                                           #0   561a40d23f00 i   resource:///org/gnome/shell/ui/keyboard.js:1099 (33e17846c3d0 @ 56)
                                           #1   561a40d23e58 i   resource:///org/gnome/shell/ui/keyboard.js:1105 (33e17846c420 @ 99)
                                           #2   561a40d23dc8 i   resource:///org/gnome/shell/ui/init.js:21 (2559d7c70bf0 @ 48)
Jul 05 11:45:52 manjaro gdm-password][3030]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-3030) opened.
Jul 05 11:45:55 manjaro gdm-password][3030]: gkr-pam: unable to locate daemon control file
Jul 05 11:45:55 manjaro gdm-password][3030]: gkr-pam: stashed password to try later in open session
Jul 05 11:45:55 manjaro gdm-password][3030]: pam_unix(gdm-password:session): session opened for user owner(uid=1000) by owner(uid=0)
Jul 05 11:45:55 manjaro gdm-password][3030]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-3030) opened.
Jul 05 11:45:55 manjaro systemd-logind[805]: New session 12 of user owner.
Jul 05 11:45:55 manjaro systemd[1]: Started Session 12 of User owner.
Jul 05 11:45:55 manjaro gdm-password][3030]: gkr-pam: unlocked login keyring
Jul 05 11:45:55 manjaro gnome-shell[2296]: Dropping signal SessionOpened of type (s) since the type from the expected interface is (ss)
Jul 05 11:45:59 manjaro kernel: rfkill: input handler enabled
Jul 05 11:45:59 manjaro gsd-power[2473]: Release of light sensors failed: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Not Authorized: Sensor claim not allowed

kernel: 6.0.19-4-MANJARO
DE: Gnome Shell 46.2

2

Hi @ncpa, and welcome!

That kernel is EOL and has been for quite some time.

It is very possible that that is the reason for your woes. I’d recommend you boot into a live environment, and enter a chroot environment from there.

How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

From there you can install a still-supported kernel, say 6.1, an LTS one that should be maintained for a long time to come:

mhwd-kernel --install linux61

If successful, reboot into the installed kernel:

Followed by removing the EOL one:

sudo mhwd-kernel --remove linux60

Also, if you haven’t updated in a while, you no doubt have .pacnew files to handle. You should do this ASAP. See:

And:

https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#.pacnew

3

I’ve updated to the 6.6 (since that seems to be the latest LTS kernel), but the problem persist. I’ve now also tried to create a completely new account and log in there, to see if maybe some old config files were causing this but that didn’t work either. It is still freezing on the login screen.

4

Then boot the live environment and enter the chroot environment again. But this time, get us logs to check out and let['s see what there is to see.

Finding errors

journalctl --priority=warning..crit --no-pager --boot=0

Where:

  • The --priority=warning..err argument limits the output to warnings and errors only;
  • --no-pager formats the output nicely for use here, on the forum;
  • the --boot=0 argument limits the messages to be from the current boot.

The above is to be run in the chroot environment and the output provided here:

Providing terminal output

:bangbang: Tip :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Also provide the output of:

inxi --full --admin --filter --width

…from the chroot environment, please.

5

@Mirdarthos thank you for your help, but in the meantime I’ve done what you suggested and went through the .pacnew files, however something must have gone wrong there, since after doing it and rebooting a GUI for creating a new account was presented to me. After making one I’ve seemingly been logged in to it, except was not able to do anything, there was no dock, no applications, settings button in the top left menu was missing, event the time and calendar on top was not there. I went to another TTY and tried to log in to my original account but was unable to do so, my credentials were not working. The newly created account didn’t had sudo privileges, so I was not even able to check what happened or reset my password. At this point I think trying to fix this would be too much hassle. I am nuking the os right now, and will get a fresh install. It will actually take me less time doing it this way. But again, thank you for taking your time trying to help me with this.

1 Like
6

Now you get a new, fresh beginning and you can keep your system up-to-date and handle any and all .pacnew files with every update instead of letting it all accumulate.

1 Like