[SOLVED]Can't logn GNOME

archy777 · 2024-04-04 10:33:31

Hey guys!

My laptop (T480) fell suspend due to low battery.
After turning it on I can't login in gnome (wayland) but I can successfully login on tty2 or gnome x-org.
I tried to update system, disable/enable stop/start/restart gdm service, uninstall gdm, gnome, gnome-extra and reinstall it, but it doesn't help.

My journalctl here

Thanks in advance for any help

Last edited by archy777 (2024-04-07 13:00:14)

seth · 2024-04-04 13:13:50

You've nm, wpa_supplicant, dhcpcd and iwd running - at least.

Disable dhcpcd and if you want to use iwd as NM backend see https://wiki.archlinux.org/title/Networ … Fi_backend
Then please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

to make sure there're no other colliding network services.

апр 04 13:07:17 arch /usr/lib/gdm-wayland-session[1329]: /usr/bin/gnome-session: строка 6: grep: команда не найдена
апр 04 13:07:17 arch /usr/lib/gdm-wayland-session[1330]: /usr/bin/gnome-session: строка 16: gsettings: команда не найдена
апр 04 13:07:17 arch gnome-session-b[1302]: Неизвестный параметр -l
апр 04 13:07:17 arch gdm-password][1207]: pam_unix(gdm-password:session): session closed for user archy
апр 04 13:07:17 arch gdm[726]: Gdm: GdmDisplay: Session never registered, failing
апр 04 13:07:17 arch kernel: rfkill: input handler disabled
апр 04 13:07:17 arch systemd[1]: session-3.scope: Deactivated successfully.
апр 04 13:07:17 arch systemd-logind[587]: Session 3 logged out. Waiting for processes to exit.
апр 04 13:07:17 arch systemd-logind[587]: Removed session 3.

So google translate tells me "The team was not found", deepl.com tells me "command not found" - all hail our future AI overlords!
And apparently

апр 04 13:07:17 arch gnome-session-b[1302]: Неизвестный параметр -l

says "unknown parameter"

So you don't have grep or gsettings installed, what's almost not a thing - there's probably some filesystem corruption.
To see how bad it is:

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

(And since you apparently don't have grep, try to re-install that package first

archy777 · 2024-04-04 14:04:25

seth wrote:

You've nm, wpa_supplicant, dhcpcd and iwd running - at least.
Disable dhcpcd and if you want to use iwd as NM backend see https://wiki.archlinux.org/title/Networ … Fi_backend

Yeah, when I just installed plain arch I used iwd for wlan. But after I installed gnome it says smth like "can't display networks, network manager is not available" in network menu. Than I enabled it with systemd.

seth wrote:

Then please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

I've stoped and disabled dhcpcd and iwd

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | timers.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

seth wrote:

(And since you apparently don't have grep, try to re-install that package first wink

That's weird cause I have one and able to do

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/gshadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/hosts (Modification time mismatch)
backup file: filesystem: /etc/hosts (Size mismatch)
backup file: filesystem: /etc/hosts (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
backup file: filesystem: /etc/subgid (Modification time mismatch)
backup file: filesystem: /etc/subgid (Size mismatch)
backup file: filesystem: /etc/subgid (SHA256 checksum mismatch)
backup file: filesystem: /etc/subuid (Modification time mismatch)
backup file: filesystem: /etc/subuid (Size mismatch)
backup file: filesystem: /etc/subuid (SHA256 checksum mismatch)
backup file: glibc: /etc/locale.gen (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Size mismatch)
backup file: glibc: /etc/locale.gen (SHA256 checksum mismatch)
warning: libutempter: /usr/lib/utempter/utempter (GID mismatch)
warning: libutempter: /usr/lib/utempter/utempter (Permissions mismatch)
libutempter: 20 total files, 1 altered file
backup file: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Size mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (SHA256 checksum mismatch)
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (SHA256 checksum mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Modification time mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Size mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (SHA256 checksum mismatch)
warning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
warning: systemd: /var/log/journal (GID mismatch)
shadow: 588 total files, 1 altered file
backup file: sudo: /etc/sudoers (Modification time mismatch)
backup file: sudo: /etc/sudoers (Size mismatch)
backup file: sudo: /etc/sudoers (SHA256 checksum mismatch)
systemd: 1449 total files, 1 altered file
warning: vlc: /usr/lib/vlc/plugins/plugins.dat (Modification time mismatch)
warning: vlc: /usr/lib/vlc/plugins/plugins.dat (Size mismatch)
warning: vlc: /usr/lib/vlc/plugins/plugins.dat (SHA256 checksum mismatch)
vlc: 1085 total files, 1 altered file

seth wrote:

all hail our future AI overlords!

Yeah, "team" and "command" sounds and writes similar in russian

Last edited by archy777 (2024-04-04 14:07:39)

seth · 2024-04-04 14:20:25

That's weird cause I have one and able to do

The output there is innocuous…

cat /usr/bin/gnome-session

What's your login shell, bash? zsh? fish?
Do you use oh-my-zsh?

archy777 · 2024-04-04 14:31:17

seth wrote:

cat /usr/bin/gnome-session
What's your login shell, bash? zsh? fish?
Do you use oh-my-zsh?

Bash. A couple days ago I installed starship, if it matters

seth · 2024-04-04 14:35:28

Perhaps. Comment all overly fancy stuff in your bashrc, iirc. at least KDE invokes the shell differently depending on whether wayland or X11 are started and there's the "gnome-session-b[1302]: Неизвестный параметр -l" what looks like a failed attempt at a login shell…

archy777 · 2024-04-04 15:58:26

Get it!
It's not starship and it's not even .bashrc. The problem was in .bash_profile. I guess if you export any path that doesn't exists wayland fails with login while x-org just ignores these lines.
Thank you so much for help!

Last edited by archy777 (2024-04-04 16:33:16)

seth · 2024-04-04 16:51:29

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

The X11 session will most likely not have invoked bash in a way that sourced .bash_profile

V1del · 2024-04-04 17:16:26

That last analysis sounds unlikely, maybe post the file/the line you changed.

Otherwise, if you consider it solved mark it as such by editing the title in your first post and prepending [SOLVED]

Edit: How did I not F5 in the last 20 mins ...

Last edited by V1del (2024-04-04 17:17:05)

archy777 · 2024-04-04 18:55:25

V1del wrote:

maybe post the file/the line you changed

#export PATH='$PATH:$HOME/.scripts'

Don't have '.scripts' folder yet. Copied .bash_profile from another machine
Also commented

#export PATH='$PATH:/usr/local/bin/obsidian'

Obsidian isn't installed here either.

seth wrote:

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

V1del wrote:

Otherwise, if you consider it solved mark it as such by editing the title in your first post and prepending [SOLVED]

Sorry, didn't find out how to do this. Thanks for help again!

seth · 2024-04-04 20:25:50

Don't have '.scripts' folder yet. Copied .bash_profile from another machine

The problem there are the single quotes, they prevent variable expansion - so '$PATH' is just literally '$PATH' whereas "$PATH" is "/home/user/bin:/usr/local/bin:/usr/bin"

archy777 · 2024-04-04 22:05:34

seth wrote:

The problem there are the single quotes, they prevent variable expansion - so '$PATH' is just literally '$PATH' whereas "$PATH" is "/home/user/bin:/usr/local/bin:/usr/bin"

Now I have in my bash_profile

export EDITOR="vim"
export TERMINAL='alacritty'

If I type

❯ echo $EDITOR
❯ echo $TERMINAL

I get vim and alacritty respectively.

How does it work? Bash misread it only while first loading?

seth · 2024-04-04 22:08:32

You're setting the variables to static literals that also require no escaping whatsoever - single or double quote doesn't make any dfference in this case.

foo=bar
echo $foo
bar='$foo'
echo $bar
bar="$foo"
echo $bar

archy777 · 2024-04-04 22:12:55

seth wrote:

You're setting the variables to static literals that also require no escaping whatsoever - single or double quote doesn't make any dfference in this case.
foo=bar
echo $foo
bar='$foo'
echo $bar
bar="$foo"
echo $bar

Get it. Thank you)

Arch Linux

#1 2024-04-04 10:33:31

[SOLVED]Can't logn GNOME

#2 2024-04-04 13:13:50

Re: [SOLVED]Can't logn GNOME

#3 2024-04-04 14:04:25

Re: [SOLVED]Can't logn GNOME

#4 2024-04-04 14:20:25

Re: [SOLVED]Can't logn GNOME

#5 2024-04-04 14:31:17

Re: [SOLVED]Can't logn GNOME

#6 2024-04-04 14:35:28

Re: [SOLVED]Can't logn GNOME

#7 2024-04-04 15:58:26

Re: [SOLVED]Can't logn GNOME

#8 2024-04-04 16:51:29

Re: [SOLVED]Can't logn GNOME

#9 2024-04-04 17:16:26

Re: [SOLVED]Can't logn GNOME

#10 2024-04-04 18:55:25

Re: [SOLVED]Can't logn GNOME

#11 2024-04-04 20:25:50

Re: [SOLVED]Can't logn GNOME

#12 2024-04-04 22:05:34

Re: [SOLVED]Can't logn GNOME

#13 2024-04-04 22:08:32

Re: [SOLVED]Can't logn GNOME

#14 2024-04-04 22:12:55

Re: [SOLVED]Can't logn GNOME

Board footer