[FIXED] login loop after /sda disconnected during update

BoGy · 2024-09-20 14:52:02

I have arch running on my hp probook laptop (3rd gen Core I5)

This laptop has broken sata connections, so i boot it from an ssd that is connected via usb.
This has been running fine for many years, but a few days ago i accidentally hit the usb connector while yay -Suy was running, this caused an IO error and made the pc lock up
I then rebooted, fsck fixed some stuff, but my system (gui) doesn't autologin me anymore. So now i have to enter my pwd, and if i do that, it'll start loading, then returns to the login screen, so something is wrong.

Via Recovery mode/console I've already tried to reinstall all packages and dependencies and was hoping that this would fix it.. But it didn't.

How can I fix this?

Thanks

Last edited by BoGy (2024-10-03 10:07:26)

V1del · 2024-09-20 18:11:32

Produce the broken situation, log into a terminal, post

sudo journalctl -b | curl -F 'file=@-' 0x0.st
pacman -Qkk > /dev/null |  curl -F 'file=@-' 0x0.st

BoGy · 2024-09-24 13:43:15

sorry for the long wait, i had a very busy weekend...

So, i let my arch boot into gui, and after the autologin returned me to the login screen I opened a second session (CTRL-ALT-F3), logged in as root and performed your commands.

the first line delivered a result:
http://0x0.st/XYL6.txt
to me it looks like QT has problems loading its wayland plugin, or am I wrong here? And above all, how can I fix this?

the second line resulted in:
http://0x0.st/XYpG.txt

EDIT: updated this post so both URL's are ez to find

Last edited by BoGy (2024-09-24 16:32:59)

V1del · 2024-09-24 13:52:22

You normally get that plugin error if you erreoneously set the QT_QPA_PLATFORM environment variable to some incorrect value, but seeing you get a bunch of mismatches chances are quite a few packages are corrupted and need to be reinstalled.

So for a proper assessment we'd need the output of the second command -- but I think i fucked that up it should be

pacman -Qkk 2>&1 >/dev/null |  curl -F 'file=@-' 0x0.st

to properly pipe stderr

Last edited by V1del (2024-09-24 13:59:10)

BoGy · 2024-09-24 16:07:00

<UPDATE>
I was able to generate the second file with your modified command; this is the URL:
http://0x0.st/XYpp.txt

<Original reply>
I ran the second command twice;

without SUDO:
No URL generated (started with error 451 - Unavailable for legal reasons)
followed by tons of errors

with SUDO:
no URL generated (same error 451 like without sudo)
followed by 8 packages giving errors
- cups (3x Rights don't match)
- java-runtime (Symlinkpath & Modification Time doesn't match)
- libutempter (GID & Rights doesn't match)
- nodejs-nopt (rights don't match)
- passim (UID & GID doesn't match; also passim/data has these two errors)
- shadow (GID & Rights doesn't match)
- systemd (GID doesn't match)
- vlc (plugins.dat errors), vlc is not used by me

-->> X & Y doens't match -->> this means there are two error lines on this package.

Last edited by BoGy (2024-09-24 16:09:37)

V1del · 2024-09-24 16:20:37

You must've copied or written the command incorrectly or using some weird shell, my command works properly on bash.

If these 8 packages are the only ones listed after letting it run through, those are more or less normal

seth · 2024-09-24 16:23:03

fout:pakket '/dev/null' niet gevonden
waarschuwing:'/dev/null' is een bestand, u wilt waarschijnlijk -p/--file gebruiken.

sudo LC_ALL=C pacman -Qkk 2>&1 > /dev/null  > /tmp/error_packages.txt
cat /tmp/error_packages.txt | curl -F 'file=@-' 0x0.st # if this command fails w/ 451, upload the file somewhere

Edit, @V1del, https://en.wikipedia.org/wiki/HTTP_451
But a general problem is that Qkk can take so long that the connection times out (though that would not generate 451)

Last edited by seth (2024-09-24 16:24:57)

BoGy · 2024-09-24 16:34:03

seth wrote:

fout:pakket '/dev/null' niet gevonden
waarschuwing:'/dev/null' is een bestand, u wilt waarschijnlijk -p/--file gebruiken.
sudo LC_ALL=C pacman -Qkk 2>&1 > /dev/null  > /tmp/error_packages.txt
cat /tmp/error_packages.txt | curl -F 'file=@-' 0x0.st # if this command fails w/ 451, upload the file somewhere
Edit, @V1del, https://en.wikipedia.org/wiki/HTTP_451
But a general problem is that Qkk can take so long that the connection times out (though that would not generate 451)

i have a valid second output now... i forgot the second > in that updated pacman command

BoGy · 2024-09-24 16:35:21

V1del wrote:

You must've copied or written the command incorrectly or using some weird shell, my command works properly on bash.
If these 8 packages are the only ones listed after letting it run through, those are more or less normal

yes I forgon a ">" symbol...

this is the correct output link

https://0x0.st/XYpG.txt

seth · 2024-09-26 14:07:45

That doesn't look hugely corrupted, do you still get the "login loop" and do you have an updated journal for that?

Edit:

sep 24 15:22:00 probook sddm[477]: Loading theme configuration from "/usr/share/sddm/themes/Vivid-SDDM-6/theme.conf"

Your problem doesn't look like it's w/ the session but w/ SDDM.
https://wiki.archlinux.org/title/SDDM#Editing_themes => try "breeze"
For the other themes you'll likely require some Qt5 packages, see https://aur.archlinux.org/packages/sddm-sugar-candy-git

Last edited by seth (2024-09-26 14:14:54)

BoGy · 2024-09-28 13:00:57

I still get the login loop.

If it's gotta do something with the theme, then creating a new account should work right? (as thet'll default back to the breeze theme)

this also failed when tried.
when logging in it shortly switches to a console loginscreen (text) and then switches back to the gui loginscreen

seth · 2024-09-28 13:24:43

It's (most likely) not your account, it's the login manager.
You need to change the SDDM configuration.

BoGy · 2024-09-28 15:35:55

OK, i tried in recovery mode, couldn't login with wayland...
When I selected Plasma-X11 it did show the login splashscreen (cat animation), although it does seem to lock up after a while, so I never get to see my desktop. But it's one step forward to a working solution maybe?

So my thinking is now that there is a problem with my wayland config and/or my plasma config.

I'll create another journal output for that, as a newbie i only knew it's journalctl to use, but not exactly what command. (I do know i'll have to pipe the output like this: | curl -F 'file=@-' 0x0.st)

thanks in advance for your help!

BoGy · 2024-09-28 18:46:25

seth wrote:

It's (most likely) not your account, it's the login manager.
You need to change the SDDM configuration.

here is the requested journal:
http://0x0.st/Xgb8.txt

this part makes me think there is something wrong with freedesktop (which gets updated through flatpak, but i don't know how to reinstall all flatpak packages)

sep 28 17:31:31 probook dbus-daemon[412]: [system] Successfully activated service 'org.freedesktop.UDisks2'
sep 28 17:31:31 probook udisksd[617]: Acquired the name org.freedesktop.UDisks2 on the system message bus
sep 28 17:31:31 probook systemd[1]: Started Disk Manager.
sep 28 17:31:31 probook dbus-daemon[412]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.32' (uid=1000 pid=560 comm="/usr/lib/kf6/baloo_file")
sep 28 17:31:31 probook systemd[1]: Starting Daemon for power management...
sep 28 17:31:31 probook ksplashqml[563]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
sep 28 17:31:31 probook kcminit_startup[564]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
sep 28 17:31:31 probook kcminit_startup[564]: qt.qpa.xcb: could not connect to display :1
sep 28 17:31:31 probook kcminit_startup[564]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
sep 28 17:31:31 probook kcminit_startup[564]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
sep 28 17:31:31 probook kcminit_startup[564]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                              
                                              Available platform plugins are: minimal, eglfs, xcb, wayland-egl, vnc, linuxfb, minimalegl, offscreen, vkkhrdisplay, wayland.
sep 28 17:31:31 probook ksplashqml[563]: qt.qpa.xcb: could not connect to display :1
sep 28 17:31:31 probook sddm-helper[663]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=967) by (uid=0)
sep 28 17:31:31 probook ksplashqml[563]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
sep 28 17:31:31 probook sddm-helper[663]: pam_systemd(sddm-greeter:session): New sd-bus connection (system-bus-pam-systemd-663) opened.
sep 28 17:31:31 probook ksplashqml[563]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
sep 28 17:31:31 probook dbus-daemon[412]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.40' (uid=0 pid=665 comm="(systemd)")
sep 28 17:31:31 probook ksplashqml[563]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                         
                                         Available platform plugins are: minimal, eglfs, xcb, wayland-egl, vnc, linuxfb, minimalegl, offscreen, vkkhrdisplay, wayland.
sep 28 17:31:31 probook dbus-daemon[412]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
sep 28 17:31:31 probook systemd-coredump[655]: Process 563 (ksplashqml) of user 1000 terminated abnormally with signal 6/ABRT, processing...
sep 28 17:31:31 probook (systemd)[665]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
sep 28 17:31:31 probook systemd-coredump[652]: Process 564 (kcminit_startup) of user 1000 terminated abnormally with signal 6/ABRT, processing...
sep 28 17:31:31 probook (systemd)[665]: pam_unix(systemd-user:session): session opened for user sddm(uid=967) by sddm(uid=0)
sep 28 17:31:31 probook systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.

I found out how to get flatpak checked (flatpak repair)
didn't result in a fixed system either. btw; it's not sddm not loading imho, as i do get an sddm loginscreen after the autologin looped

Last edited by BoGy (2024-09-29 12:23:18)

seth · 2024-09-28 19:46:02

sep 28 17:31:28 probook kwin_wayland_wrapper[606]: /usr/bin/kwin_wayland: symbol lookup error: /usr/lib/libKF6XmlGui.so.6: undefined symbol: _ZN16KStandardActions4nameENS_14StandardActionE

pacman -Qikk kxmlgui kwin

BoGy · 2024-09-29 12:29:07

seth wrote:

pacman -Qikk kxmlgui kwin

result was: 385 (kxmlgui) + 2224 (kwin) total files, 0 + 0 modified files

seth · 2024-09-29 19:20:52

That's not the output of that command - the rest (notably the entier "-i" part) matters, too.
Also add

ldd  /usr/lib/libKF6XmlGui.so.6
pacman -Qikk kconfig

BoGy · 2024-10-01 12:41:55

output of pacman -Qikk kxmlgui kwin: http://0x0.st/Xgvu.txt (i gave a summary of these results, but here's the full output)

output of pacman -Qikk kconfig: http://0x0.st/Xgv1.txt

output of ldd /usr/lib/libKF6XmlGui.so.6: http://0x0.st/Xgv_.txt

seth · 2024-10-01 12:48:43

Naam : kconfig-git

Stale AUR package, you need to update or replace it w/ the repo version.

On a formal note, in future please add LC_ALL=C to generate english output (I can still read that, but many people would have to put it through a translation service)

BoGy · 2024-10-02 13:08:40

seth wrote:

Naam : kconfig-git
Stale AUR package, you need to update or replace it w/ the repo version.
On a formal note, in future please add LC_ALL=C to generate english output (I can still read that, but many people would have to put it through a translation service)

ok, I tried rebuilding kconfig.git, but that failed..
reading through the stated errors i found out ECM had a config file but wasn't accepted.
So i started looking for ECM (yay -Ss ecm) and found out that i had an AUR version installed of extra-cmake-modules-git which is older than the Repo version. So i switched to the REPO/extra version, and after that the compiling/building of kconfig-git finally came through.

I often get questions during updates if i want to replace one version of a package with another, and sometimes it switches by itself (usually the same packagename but with the number 5 added), and then it later switches back automatically during a next update.

Anyways, i now switched back to the good version of ECM, after compilation i'll try another reboot

(needed to do it twice, as the first time it timed-out due to a Y/N question i didn't answer in time between compile and build... So did it a second time and kept an eye on the screen.. kconfig-git is now properly compiled/rebuilt

reboot now

-->> YEAH it's working again!!!

Thanks for directing me towards the solution, for me you are the most valuable person of the week!

So a big thanks, and some applause for seth!

seth · 2024-10-02 13:37:36

\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.

BoGy · 2024-10-03 19:37:04

it was already changed to "[FIXED] login....."

is that wrong or what should i change it to?

seth · 2024-10-03 19:43:40

It's typically "solved" but "fixed" is fine, too.

Arch Linux

#1 2024-09-20 14:52:02

[FIXED] login loop after /sda disconnected during update

#2 2024-09-20 18:11:32

Re: [FIXED] login loop after /sda disconnected during update

#3 2024-09-24 13:43:15

Re: [FIXED] login loop after /sda disconnected during update

#4 2024-09-24 13:52:22

Re: [FIXED] login loop after /sda disconnected during update

#5 2024-09-24 16:07:00

Re: [FIXED] login loop after /sda disconnected during update

#6 2024-09-24 16:20:37

Re: [FIXED] login loop after /sda disconnected during update

#7 2024-09-24 16:23:03

Re: [FIXED] login loop after /sda disconnected during update

#8 2024-09-24 16:34:03

Re: [FIXED] login loop after /sda disconnected during update

#9 2024-09-24 16:35:21

Re: [FIXED] login loop after /sda disconnected during update

#10 2024-09-26 14:07:45

Re: [FIXED] login loop after /sda disconnected during update

#11 2024-09-28 13:00:57

Re: [FIXED] login loop after /sda disconnected during update

#12 2024-09-28 13:24:43

Re: [FIXED] login loop after /sda disconnected during update

#13 2024-09-28 15:35:55

Re: [FIXED] login loop after /sda disconnected during update

#14 2024-09-28 18:46:25

Re: [FIXED] login loop after /sda disconnected during update

#15 2024-09-28 19:46:02

Re: [FIXED] login loop after /sda disconnected during update

#16 2024-09-29 12:29:07

Re: [FIXED] login loop after /sda disconnected during update

#17 2024-09-29 19:20:52

Re: [FIXED] login loop after /sda disconnected during update

#18 2024-10-01 12:41:55

Re: [FIXED] login loop after /sda disconnected during update

#19 2024-10-01 12:48:43

Re: [FIXED] login loop after /sda disconnected during update

#20 2024-10-02 13:08:40

Re: [FIXED] login loop after /sda disconnected during update

#21 2024-10-02 13:37:36

Re: [FIXED] login loop after /sda disconnected during update

#22 2024-10-03 19:37:04

Re: [FIXED] login loop after /sda disconnected during update

#23 2024-10-03 19:43:40

Re: [FIXED] login loop after /sda disconnected during update

Board footer