You are not logged in.
Hi there,
I've been experiencing the following issue: after password is entered to login into my user the screen would not change, cursor is there, but the password field is stuck and any other button is unresponsive and nothing is happening. I've did arch-chroot using USB stick and tried to look in the logs, but I don't see anything particular.
Could you please help me understand where to look and how to fix this? thanks!
Last edited by shuruper (2022-09-20 16:23:17)
Offline
did you set a user passwd ?
Offline
Yes
Offline
a) can you log into a console session (ctrl+alt+f1,2,3,…)?
b) if so, please elaborate on your "login page" and the desired session (what display manager and desktop environment do you intend to use)
c) if you can log into a console session, ***after*** a failing login from your "login page", post a complete system journal
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
seth, thanks for your reply.
a) I cannot
b) it is plasma (X11)
I tried to get output from “journalctl …” command you suggested while arch-chroot from my USB stick, but got:
curl: (6) Could not resolve host: 0x0.st
Offline
curl: (6) Could not resolve host: 0x0.st
means you've no internet connection and it would also be the wrong journal this way:
https://wiki.archlinux.org/title/System … al_to_view
What happens when you try to log in on the console?
Can you login (on the console) as root?
Offline
I can log in on the console as a root, but with the following messages:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
Also, “ip link” command doesn’t show my wlan0 interface, only loopback.
Offline
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
There's most likely some garbage in some /etc/profile* or a global bashrc or one you copied around - does that ring any bell? (What did you do before this started?)
Also, “ip link” command doesn’t show my wlan0 interface, only loopback.
Check
lspci -k
whether the wifi device shows up (unless it's some USB dongle) and which kernel driver is *in use*.
Also compare "uname -a" and "pacman -Qs linux" on whether you're booting an old kernel.
Offline
My bad, I should have described what I was doing before diving into debugging. Although, I think (hope) I rolled back what I did, it did some “damage” and I should have mentioned it.
So, I was trying to run ParaView (some program to visualise stuff) while “ssh -X …” into workstation where the stuff is. It was crushing saying that something wrong with my X server so I added xorg.conf file (removed, service restarted or at least I’ve tried to) and installed a couple of video drivers via pacman -S and from repo (removed). Somewhere in the middle this login page freeze happened and some of the things I was removing via arch-chroot.
Regarding bashrc or /etc/profile - I wasn’t meddling with those.
lspci -k yields correct name for the wifi card, but doesn’t list “Kernel driver in use” for it.
uname -a and pacman are friends about the kernel version.
Thanks for your help!
Offline
installed a couple of video drivers via pacman -S
did you maybe conduct a partial update?
What *does* lspci say (about the wifi chip)?
Also check the system journal and rfkill.
An early iwd startup might cause unfortunate interference, https://wiki.archlinux.org/title/iwd#Re … after_boot - but I don't think it would typically cause the kernel module to fail.
I can log in on the console as a root, but with the following messages:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
Since your wifi doesn't work, we can assume that this is on a physical terminal and NOT via ssh?
Offline
I typically do “sudo pacman -Syu” update types so partial update is a no.
lspci -k does say the following:
3a:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265
Kernel modules: iwlwifi
I don’t think that iwd can interfere since it haven’t started yet. rfkill probably is not there either, since systemctl command gives :
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down.
Yeah, every single problem now is physically present on my laptop, no ssh connection is involved.
Offline
System has not been booted with systemd as init system (PID 1). Can’t operate.
WTF?
You might want to elaborate on that situation?
Do you start a root shell w/ "init=/bin/bash" or so?
Offline
Yeah, hit “e” and then add “init=/bin/bash” and f10 to go.
Offline
Is that what's causing
I can log in on the console as a root, but with the following messages:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
?
The question was more whether you could log into the root account from a regular boot.
Offline
No, this is (init=…) the only way I know. Trying to activate terminal with ctrl+alt+f# isn’t working and I don’t know another way.
Offline
Please chroot in from live media and post the journal for a boot with the issue.
Offline
Trying to activate terminal with ctrl+alt+f# isn’t working and I don’t know another way.
2nd link below, I suspect the only thing here broken is your GUI DM or DE and you can probably log in on a console.
Offline
I’d be happy to agree, but:
1. I can’t change graphical.target into multi-user.target unless systemctl is working. I can do it from arch-chroot but what is the point if systemd isn’t started?
2. This is now my secondary issue since the only thing I can see is GRUB command line. Trying to boot regularly my disk drive results in rebooting and .. GRUB.
Ok, arch-chroot, mkinitcpio, reinstall grub (probably useless though). I can manually boot into GUI where I should enter my password just to see the same result - laptop getting stuck. I don’t know how to boot into a root shell from grub
Offline
You can edit the Kernel parameters from within GRUB. to append systemd.unit=multi-user.target
Offline
ok, I did some stupid stuff, but I stopped doing it lol.
So, as seth suggested, I've changed the target and now I'm on root with networking and also did"
journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/oVMW.txt
seth, is this what you need and what can I do next?
Offline
The journal is for the current boot. Can you post a journal for a boot where the display manager is started and the screen freezes?
journalctl -b -1
Would be the previous boot, -2 the boot before that .e.t.c..
Please also elaborate on what display manager the system uses and what configuration you have done for it.
Offline
I'm using plasma(X11) and I wasn't trying to reconfigure it before this thing happened.
Here is my journal: http://0x0.st/oVu1.txt
Offline
Sep 19 13:02:17 ganjArch systemd-logind[338]: New session c1 of user sddm.
…
Sep 19 13:02:26 ganjArch systemd-logind[338]: New session 2 of user ganja.
…
Sep 19 13:02:27 ganjArch sddm-helper[715]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Sep 19 13:02:27 ganjArch audit[697]: USER_START pid=697 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring,pam_kwallet5 acct="ganja" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 19 13:02:27 ganjArch sddm-helper[697]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Sep 19 13:02:27 ganjArch sddm-helper[717]: Adding cookie to "/home/ganja/.Xauthority"
…
Sep 19 13:02:47 ganjArch sddm[411]: Session started
Sep 19 13:02:47 ganjArch sddm-helper[697]: [PAM] Closing session
Sep 19 13:02:47 ganjArch sddm-helper[697]: pam_unix(sddm:session): session closed for user ganja
Sep 19 13:02:47 ganjArch audit[697]: USER_END pid=697 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring,pam_kwallet5 acct="ganja" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 19 13:02:47 ganjArch audit[697]: CRED_DISP pid=697 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="ganja" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 19 13:02:47 ganjArch sddm-helper[697]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Sep 19 13:02:47 ganjArch sddm-helper[697]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 19 13:02:47 ganjArch sddm-helper[697]: [PAM] Ended.
Sep 19 13:02:47 ganjArch kernel: audit: type=1106 audit(1663606967.501:106): pid=697 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring,pam_kwallet5 acct="ganja" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 19 13:02:47 ganjArch kernel: audit: type=1104 audit(1663606967.501:107): pid=697 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="ganja" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 19 13:02:47 ganjArch sddm[411]: Auth: sddm-helper exited with 1
Sep 19 13:02:47 ganjArch systemd-logind[338]: Session 2 logged out. Waiting for processes to exit.
It would seem that you're loggin in, starting the session and that somehow fails (there's no indication at all that even an attempt is made to start the plasma desktop processes) and you return to SDDM.
If you don't boot the rescue.target, but multi-user.target, I'm fairly convinced that you'll be able to log in there (on a console session)
I also assume that you can start a different session, eg. openbox?
Also
pacman -Qikk plasma-workspace
Offline
I can log in with multi-user.target, seems fine. Openbox - idk, I don't have it.
pacman -Qikk plasma-workspace outputs:
Name : plasma-workspace
Version : 5.25.5-3
Description : KDE Plasma Workspace
Architecture : x86_64
URL : https://kde.org/plasma-desktop/
Licenses : LGPL
Groups : plasma
Provides : None
Depends On : knotifyconfig ksystemstats ktexteditor libqalculate kde-cli-tools appstream-qt xorg-xrdb xorg-xsetroot kactivitymanagerd kholidays xorg-xmessage milou prison kwin plasma-integration kpeople kactivities-stats libkscreen kquickcharts kuserfeedback accountsservice kio-extras kio-fuse qt5-tools oxygen-sounds
Optional Deps : plasma-workspace-wallpapers: additional wallpapers [installed]
gpsd: GPS based geolocation
networkmanager-qt: IP based geolocation [installed]
kdepim-addons: displaying PIM events in the calendar
appmenu-gtk-module: global menu support for GTK2 and some GTK3 applications
baloo: Baloo search runner [installed]
discover: manage applications installation from the launcher [installed]
Required By : kdeplasma-addons khotkeys plasma-browser-integration plasma-nm plasma-pa plasma-vault powerdevil systemsettings
Optional For : kde-cli-tools ktorrent
Conflicts With : None
Replaces : None
Installed Size : 48.52 MiB
Packager : Antonio Rojas <arojas@archlinux.org>
Build Date : Wed Sep 14 06:55:58 2022
Install Date : Mon Sep 19 12:21:17 2022
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
plasma-workspace: 7105 total files, 0 altered files
While booted in multi-user.target I tried to "kstart plasma-desktop" to get the following:
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
...
Not sure what is it, but I'm going to reinstall it.
Offline
While booted in multi-user.target I tried to "kstart plasma-desktop"
That can expectably not work in this context.
Openbox - idk, I don't have it.
Well, … https://archlinux.org/packages/communit … 4/openbox/
Offline