Manjaro KDE not able to boot - Stuck on loading screen

[panos91txc]

Done everything, so the fix-permissions command did find like 5 broken permissions the first time that I ran it. I fixed them and re ran the command (before rebooting), then it found only one, specifically, the /usr/share/polkit-1/rules.d (this had allready been found the first time), so I fixed it and then ran again the command, only to be found once again as broken. So I fixed it again and then decided to reboot, in hope of it being fixed through the reboot. After the reboot, I logged in using tty and startx, no sound available.

inxi -Aa

returned

Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
    class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Sound API: ALSA v: k6.1.1-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.63 running: no

I decided to run again the fix-permissions command, only to find out that again 5 or so were broken, see list below,

/etc/cups/classes.conf: 0o600 => 0o644
/etc/cups/printers.conf: 0o600 => 0o644
/etc/cups/subscriptions.conf: 0o640 => 0o644
/usr/share/polkit-1/rules.d: 0o755 => 0o750
/usr/lib/utempter/utempter: 0o2755 => 0o2711

not all the same, but polki-1/rules.d still persistent.

[brahma]

i dont think these permissions are related to your issue, so lets place the user services into your home folder, but first lets compare them to mine, so post output from:

cat /usr/lib/systemd/user/pipewire-pulse.service
cat /usr/lib/systemd/user/pipewire.service
cat /usr/lib/systemd/user/pipewire-pulse.socket
cat /usr/lib/systemd/user/pipewire.socket

[panos91txc]

I also ran this, as su (don’t know if it matters),

systemctl status
● ppapadopoulos
    State: degraded
    Units: 411 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 2 units
    Since: Sun 2023-01-08 18:40:46 EET; 26min ago
  systemd: 252.4-2-manjaro
   CGroup: /
           ├─init.scope
           │ └─1 /sbin/init
           ├─system.slice
           │ ├─ModemManager.service
           │ │ └─760 /usr/bin/ModemManager
           │ ├─NetworkManager.service
           │ │ └─737 /usr/bin/NetworkManager --no-daemon
           │ ├─avahi-daemon.service
           │ │ ├─712 "avahi-daemon: running [ppapadopoulos.local]"
           │ │ └─734 "avahi-daemon: chroot helper"
           │ ├─bluetooth.service
           │ │ └─846 /usr/lib/bluetooth/bluetoothd
           │ ├─colord.service
           │ │ └─833 /usr/lib/colord
           │ ├─cronie.service
           │ │ ├─ 713 /usr/bin/crond -n
           │ │ └─2989 /usr/sbin/anacron -s
           │ ├─cups.service
           │ │ └─785 /usr/bin/cupsd -l
           │ ├─dbus.service
           │ │ └─714 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
           │ ├─polkit.service
           │ │ └─716 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─rtkit-daemon.service
           │ │ └─1212 /usr/lib/rtkit-daemon
           │ ├─sddm.service
           │ │ ├─828 /usr/bin/sddm
           │ │ └─843 /usr/lib/Xorg -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{97bf46df-cbc9-4fdc-acd2-c1b695af5044} -noreset -displayfd 17
           │ ├─snapd.service
           │ │ └─717 /usr/lib/snapd/snapd
           │ ├─systemd-journald.service
           │ │ └─439 /usr/lib/systemd/systemd-journald
           │ ├─systemd-logind.service
           │ │ └─719 /usr/lib/systemd/systemd-logind
           │ ├─systemd-timesyncd.service
           │ │ └─703 /usr/lib/systemd/systemd-timesyncd
           │ ├─systemd-udevd.service
           │ │ └─udev
           │ │   └─440 /usr/lib/systemd/systemd-udevd
           │ ├─teamviewerd.service
           │ │ └─935 /opt/teamviewer/tv_bin/teamviewerd -d
           │ ├─udisks2.service
           │ │ └─894 /usr/lib/udisks2/udisksd
           │ ├─upower.service
           │ │ └─908 /usr/lib/upowerd
           │ └─wpa_supplicant.service
           │   └─864 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant
           └─user.slice
             └─user-1000.slice
               ├─session-1.scope
               │ ├─1069 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth71bf8672-6606-4d37-b335-5b792bd0e5d6 --id 1 --start /usr/bin/startplasma-x11 --user ppapadopoulos
               │ ├─1076 /usr/bin/kwalletd5 --pam-login 6 8
               │ └─1077 /usr/bin/startplasma-x11
               └─session-2.scope
                 ├─1108 "login -- ppapadopoulos"
                 ├─1110 -bash
                 ├─1123 /bin/sh /usr/bin/startx
                 ├─1138 xinit /home/ppapadopoulos/.xinitrc -- /etc/X11/xinit/xserverrc :1 vt2 -keeptty -auth /tmp/serverauth.yJIfyfer8u
                 ├─1139 /usr/lib/Xorg -nolisten tcp :1 vt2 -keeptty -auth /tmp/serverauth.yJIfyfer8u
                 ├─1143 startplasma-x11
                 ├─1149 dbus-launch --sh-syntax --exit-with-session startplasma-x11
                 ├─1150 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
                 ├─1174 /usr/bin/plasma_session
                 ├─1181 /usr/lib/kf5/start_kdeinit
                 ├─1182 "kdeinit5: Running..."
                 ├─1184 /usr/lib/kf5/klauncher --fd=9
                 ├─1187 /usr/lib/xdg-desktop-portal
                 ├─1193 /usr/lib/xdg-document-portal
                 ├─1197 /usr/lib/xdg-permission-store
                 ├─1203 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
                 ├─1218 /usr/lib/xdg-desktop-portal-kde
                 ├─1240 /usr/bin/kded5
                 ├─1245 /usr/bin/kwin_x11
                 ├─1263 /usr/bin/kglobalaccel5
                 ├─1273 /usr/bin/ksmserver
                 ├─1276 /usr/lib/dconf-service
                 ├─1301 /usr/bin/xembedsniproxy
                 ├─1303 /usr/lib/org_kde_powerdevil
                 ├─1304 /usr/bin/kaccess
                 ├─1305 /usr/lib/baloo_file
                 ├─1308 /usr/bin/plasmashell
                 ├─1310 /usr/lib/polkit-kde-authentication-agent-1
                 ├─1317 /usr/bin/gmenudbusmenuproxy
● ppapadopoulos
    State: degraded
    Units: 411 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 2 units
    Since: Sun 2023-01-08 18:40:46 EET; 26min ago
  systemd: 252.4-2-manjaro
   CGroup: /
           ├─init.scope
           │ └─1 /sbin/init
           ├─system.slice
           │ ├─ModemManager.service
           │ │ └─760 /usr/bin/ModemManager
           │ ├─NetworkManager.service
           │ │ └─737 /usr/bin/NetworkManager --no-daemon
           │ ├─avahi-daemon.service
           │ │ ├─712 "avahi-daemon: running [ppapadopoulos.local]"
           │ │ └─734 "avahi-daemon: chroot helper"
           │ ├─bluetooth.service
           │ │ └─846 /usr/lib/bluetooth/bluetoothd
           │ ├─colord.service
           │ │ └─833 /usr/lib/colord
           │ ├─cronie.service
           │ │ ├─ 713 /usr/bin/crond -n
           │ │ └─2989 /usr/sbin/anacron -s
           │ ├─cups.service
           │ │ └─785 /usr/bin/cupsd -l
           │ ├─dbus.service
           │ │ └─714 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
           │ ├─polkit.service
           │ │ └─716 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─rtkit-daemon.service
           │ │ └─1212 /usr/lib/rtkit-daemon
           │ ├─sddm.service
           │ │ ├─828 /usr/bin/sddm
           │ │ └─843 /usr/lib/Xorg -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{97bf46df-cbc9-4fdc-acd2-c1b695af5044} -noreset -displayfd 17
           │ ├─snapd.service
           │ │ └─717 /usr/lib/snapd/snapd
           │ ├─systemd-journald.service
           │ │ └─439 /usr/lib/systemd/systemd-journald
           │ ├─systemd-logind.service
           │ │ └─719 /usr/lib/systemd/systemd-logind
           │ ├─systemd-timesyncd.service
           │ │ └─703 /usr/lib/systemd/systemd-timesyncd
           │ ├─systemd-udevd.service
           │ │ └─udev
           │ │   └─440 /usr/lib/systemd/systemd-udevd
           │ ├─teamviewerd.service
           │ │ └─935 /opt/teamviewer/tv_bin/teamviewerd -d
           │ ├─udisks2.service
           │ │ └─894 /usr/lib/udisks2/udisksd
           │ ├─upower.service
           │ │ └─908 /usr/lib/upowerd

it states 2 failed services but I couldn’t find them.

So here are the results,

cat /usr/lib/systemd/user/pipewire-pulse.service                                                                                                                                                              INT ✘  5m 58s  
[Unit]
Description=PipeWire PulseAudio

# We require pipewire-pulse.socket to be active before starting the daemon, because
# while it is possible to use the service without the socket, it is not clear
# why it would be desirable.
#
# A user installing pipewire and doing `systemctl --user start pipewire-pulse`
# will not get the socket started, which might be confusing and problematic if
# the server is to be restarted later on, as the client autospawn feature
# might kick in. Also, a start of the socket unit will fail, adding to the
# confusion.
#
# After=pipewire-pulse.socket is not needed, as it is already implicit in the
# socket-service relationship, see systemd.socket(5).
Requires=pipewire-pulse.socket
ConditionUser=!root
Wants=pipewire.service pipewire-session-manager.service
After=pipewire.service pipewire-session-manager.service
Conflicts=pulseaudio.service

[Service]
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
Type=simple
ExecStart=/usr/bin/pipewire-pulse
Restart=on-failure
Slice=session.slice

[Install]
Also=pipewire-pulse.socket
WantedBy=default.target

cat /usr/lib/systemd/user/pipewire.service                                                                                                                                                                                   ✔ 
[Unit]
Description=PipeWire Multimedia Service

# We require pipewire.socket to be active before starting the daemon, because
# while it is possible to use the service without the socket, it is not clear
# why it would be desirable.
#
# A user installing pipewire and doing `systemctl --user start pipewire`
# will not get the socket started, which might be confusing and problematic if
# the server is to be restarted later on, as the client autospawn feature
# might kick in. Also, a start of the socket unit will fail, adding to the
# confusion.
#
# After=pipewire.socket is not needed, as it is already implicit in the
# socket-service relationship, see systemd.socket(5).
Requires=pipewire.socket

[Service]
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
Type=simple
ExecStart=/usr/bin/pipewire
Restart=on-failure
Slice=session.slice

[Install]
Also=pipewire.socket
WantedBy=default.target

cat /usr/lib/systemd/user/pipewire-pulse.socket 
[Unit]
Description=PipeWire PulseAudio
ConditionUser=!root
Conflicts=pulseaudio.socket

[Socket]
Priority=6
ListenStream=%t/pulse/native

[Install]
WantedBy=sockets.target

cat /usr/lib/systemd/user/pipewire.socket                                                                                                                                                                                    ✔ 
[Unit]
Description=PipeWire Multimedia System Socket

[Socket]
Priority=6
ListenStream=%t/pipewire-0

[Install]
WantedBy=sockets.target

[brahma]

we know which 2 services are they:

@panos91txc

sddm:x:963:963:Simple Desktop Display Manager:/var/lib/sddm:/usr/bin/nologin

and

@panos91txc

ppapadopoulos:x:1000:1000:Panagiotis Papadopoulos:/home/ppapadopoulos:/bin/bash

---

post also output from:

cat /usr/lib/systemd/system/sddm.service
cat /usr/lib/systemd/system/user@.service
cat /usr/lib/systemd/system/user@.service.d/10-login-barrier.conf

[panos91txc]

cat /usr/lib/systemd/system/sddm.service                                                                                                                                                                                     ✔ 
cat /usr/lib/systemd/system/user@.service
cat /usr/lib/systemd/system/user@.service.d/10-login-barrier.conf
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
Conflicts=getty@tty1.service
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service systemd-logind.service
StartLimitIntervalSec=30
StartLimitBurst=2

[Service]
ExecStart=/usr/bin/sddm
Restart=always

[Install]
Alias=display-manager.service

#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=User Manager for UID %i
Documentation=man:user@.service(5)
After=user-runtime-dir@%i.service dbus.service
Requires=user-runtime-dir@%i.service
IgnoreOnIsolate=yes

[Service]
User=%i
PAMName=systemd-user
Type=notify
ExecStart=/usr/lib/systemd/systemd --user
Slice=user-%i.slice
KillMode=mixed
Delegate=pids memory cpu
TasksMax=infinity
TimeoutStopSec=120s
KeyringMode=inherit
OOMScoreAdjust=100
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
# Make sure user instances are started after logins are allowed. However this
# is not desirable for user@0.service since root should be able to log in
# earlier during the boot process especially if something goes wrong.
After=systemd-user-sessions.service

[brahma]

all of those services look like mine… and before we proceed, post also output from:

systemctl --user status pipewire.service

[panos91txc]

@brahma

systemctl --user status pipewire.service

tried this one before, all I get is,

systemctl --user status pipewire.service                                                                                                                                                                                     ✔ 
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1

[brahma]

ok, so lets put the services in your home… create 2 folders if they are not there in this location: /home/.config/systemd/user
default.target.wants
sockets.target.wants
and in the default.target.wants folder create 2 services: right click/create new/link to file or directory, and under name:
pipewire-pulse.service
and under file or directory to link to:
/usr/lib/systemd/user/pipewire-pulse.service
and put inside it:

[Unit]
Description=PipeWire PulseAudio

# We require pipewire-pulse.socket to be active before starting the daemon, because
# while it is possible to use the service without the socket, it is not clear
# why it would be desirable.
#
# A user installing pipewire and doing `systemctl --user start pipewire-pulse`
# will not get the socket started, which might be confusing and problematic if
# the server is to be restarted later on, as the client autospawn feature
# might kick in. Also, a start of the socket unit will fail, adding to the
# confusion.
#
# After=pipewire-pulse.socket is not needed, as it is already implicit in the
# socket-service relationship, see systemd.socket(5).
Requires=pipewire-pulse.socket
ConditionUser=!root
Wants=pipewire.service pipewire-session-manager.service
After=pipewire.service pipewire-session-manager.service
Conflicts=pulseaudio.service

[Service]
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
Type=simple
ExecStart=/usr/bin/pipewire-pulse
Restart=on-failure
Slice=session.slice

[Install]
Also=pipewire-pulse.socket
WantedBy=default.target

create second link with name:
pipewire.service
and link to:
/usr/lib/systemd/user/pipewire.service
and put there:

[Unit]
Description=PipeWire Multimedia Service

# We require pipewire.socket to be active before starting the daemon, because
# while it is possible to use the service without the socket, it is not clear
# why it would be desirable.
#
# A user installing pipewire and doing `systemctl --user start pipewire`
# will not get the socket started, which might be confusing and problematic if
# the server is to be restarted later on, as the client autospawn feature
# might kick in. Also, a start of the socket unit will fail, adding to the
# confusion.
#
# After=pipewire.socket is not needed, as it is already implicit in the
# socket-service relationship, see systemd.socket(5).
Requires=pipewire.socket

[Service]
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
Type=simple
ExecStart=/usr/bin/pipewire
Restart=on-failure
Slice=session.slice

[Install]
Also=pipewire.socket
WantedBy=default.target

---

in the sockets.target.wants folder create 2 links:
pipewire-pulse.socket
link to:
/usr/lib/systemd/user/pipewire-pulse.socket
inside:

[Unit]
Description=PipeWire PulseAudio
ConditionUser=!root
Conflicts=pulseaudio.socket

[Socket]
Priority=6
ListenStream=%t/pulse/native

[Install]
WantedBy=sockets.target

second link name:
pipewire.socket
link to:
/usr/lib/systemd/user/pipewire.socket
inside:

[Unit]
Description=PipeWire Multimedia System Socket

[Socket]
Priority=6
ListenStream=%t/pipewire-0

[Install]
WantedBy=sockets.target

reboot

[panos91txc]

Done everything. Still no sound…

[brahma]

damn!

post again logs to see if the failed services are still there:
journalctl -b0 -p4 --no-pager

[panos91txc]

great cat hahaha.

here arethe results… pretty red…

journalctl -b0 -p4 --no-pager                                                                                                                                                                                              1 ✘ 
Jan 08 19:59:34 ppapadopoulos kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Jan 08 19:59:34 ppapadopoulos kernel:  #5 #6 #7
Jan 08 19:59:34 ppapadopoulos kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Jan 08 19:59:34 ppapadopoulos kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jan 08 19:59:34 ppapadopoulos kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000000E) is beyond end of object (length 0xE) (20220331/exoparg2-393)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.HS15._PLD due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
Jan 08 19:59:34 ppapadopoulos kernel: nvidia: loading out-of-tree module taints kernel.
Jan 08 19:59:34 ppapadopoulos kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 08 19:59:34 ppapadopoulos kernel: Disabling lock debugging due to kernel taint
Jan 08 19:59:34 ppapadopoulos kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 23:04:03 UTC 2022
Jan 08 19:59:34 ppapadopoulos kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000184F (\GPIS) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C5F (\_SB.PCI0.PEG0.PEGP.GPR) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C7F (\GPIO) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C63 (\GP01) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C5F (\_SB.PCI0.PEG0.PEGP.GPR) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C7F (\GPIO) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C63 (\GP01) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C5F (\_SB.PCI0.PEG0.PEGP.GPR) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C7F (\GPIO) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C63 (\GP01) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20220331/utaddress-204)
Jan 08 19:59:34 ppapadopoulos kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Jan 08 19:59:34 ppapadopoulos kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Jan 08 19:59:34 ppapadopoulos kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
Jan 08 19:59:35 ppapadopoulos kernel: at24 7-0052: supply vcc not found, using dummy regulator
Jan 08 19:59:35 ppapadopoulos kernel: spi-nor: probe of spi0.0 failed with error -22
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Jan 08 19:59:36 ppapadopoulos bluetoothd[840]: src/plugin.c:plugin_init() Failed to init bap plugin
Jan 08 19:59:36 ppapadopoulos kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
Jan 08 19:59:37 ppapadopoulos systemd[879]: PAM failed: Authentication failure
Jan 08 19:59:37 ppapadopoulos systemd[879]: user@963.service: Failed to set up PAM session: Operation not permitted
Jan 08 19:59:37 ppapadopoulos systemd[879]: user@963.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jan 08 19:59:37 ppapadopoulos systemd[1]: user@963.service: Failed with result 'exit-code'.
Jan 08 19:59:37 ppapadopoulos systemd[1]: Failed to start User Manager for UID 963.
Jan 08 19:59:37 ppapadopoulos sddm-greeter[880]: QFont::fromString: Invalid description '(empty)'
Jan 08 19:59:37 ppapadopoulos sddm-greeter[880]: QObject: Cannot create children for a parent that is in a different thread.
                                                 (Parent is QGuiApplication(0x7ffedf10bb00), parent's thread is QThread(0x55ef2452e4e0), current thread is QThread(0x55ef24650aa0)
Jan 08 19:59:37 ppapadopoulos sddm-greeter[880]: QObject: Cannot create children for a parent that is in a different thread.
                                                 (Parent is QGuiApplication(0x7ffedf10bb00), parent's thread is QThread(0x55ef2452e4e0), current thread is QThread(0x55ef24650aa0)
Jan 08 19:59:37 ppapadopoulos sddm-greeter[880]: QObject: Cannot create children for a parent that is in a different thread.
                                                 (Parent is QGuiApplication(0x7ffedf10bb00), parent's thread is QThread(0x55ef2452e4e0), current thread is QThread(0x55ef24650aa0)
Jan 08 19:59:37 ppapadopoulos sddm-greeter[880]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Jan 08 19:59:38 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/components/VirtualKeyboard.qml:11:1: Type InputPanel unavailable
Jan 08 19:59:38 ppapadopoulos sddm-greeter[880]: qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard unavailable
Jan 08 19:59:38 ppapadopoulos sddm-greeter[880]: qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module "QtQuick.VirtualKeyboard.Plugins" is not installed
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.28'
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos sddm-greeter[880]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 08 19:59:39 ppapadopoulos wpa_supplicant[853]: bgscan simple: Failed to enable signal strength monitoring
Jan 08 19:59:39 ppapadopoulos kernel: kauditd_printk_skb: 112 callbacks suppressed
Jan 08 19:59:43 ppapadopoulos systemd[1065]: PAM failed: Authentication failure
Jan 08 19:59:43 ppapadopoulos systemd[1065]: user@1000.service: Failed to set up PAM session: Operation not permitted
Jan 08 19:59:43 ppapadopoulos systemd[1065]: user@1000.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jan 08 19:59:43 ppapadopoulos systemd[1]: user@1000.service: Failed with result 'exit-code'.
Jan 08 19:59:43 ppapadopoulos systemd[1]: Failed to start User Manager for UID 1000.
Jan 08 19:59:44 ppapadopoulos ksplashqml[1085]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath-dark.desktop/contents/splash/Splash.qml:49: ReferenceError: maxWidth is not defined
Jan 08 19:59:44 ppapadopoulos ksplashqml[1085]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath-dark.desktop/contents/splash/Splash.qml:82:29: Unable to assign int to QEasingCurve
Jan 08 19:59:45 ppapadopoulos kernel: kauditd_printk_skb: 7 callbacks suppressed
Jan 08 20:00:27 ppapadopoulos systemd[1103]: PAM failed: Authentication failure
Jan 08 20:00:27 ppapadopoulos systemd[1103]: user@1000.service: Failed to set up PAM session: Operation not permitted
Jan 08 20:00:27 ppapadopoulos systemd[1103]: user@1000.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jan 08 20:00:27 ppapadopoulos systemd[1]: user@1000.service: Failed with result 'exit-code'.
Jan 08 20:00:27 ppapadopoulos systemd[1]: Failed to start User Manager for UID 1000.
Jan 08 20:00:32 ppapadopoulos xdg-desktop-por[1181]: Failed connect to PipeWire: Couldn't connect to PipeWire
Jan 08 20:00:34 ppapadopoulos org.a11y.Bus[1496]: dbus-daemon[1496]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=1000 pid=1178 comm="/usr/lib/kf5/klauncher --fd=9")
Jan 08 20:00:34 ppapadopoulos org.a11y.Bus[1496]: dbus-daemon[1496]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 08 20:00:49 ppapadopoulos kstart5[1756]: Omitting both --window and --windowclass arguments is not recommended
Jan 08 20:00:49 ppapadopoulos konsole[1761]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Jan 08 20:00:49 ppapadopoulos konsole[1761]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Jan 08 20:00:56 ppapadopoulos kwalletd5[1870]: Application ' "Brave" ' using kwallet without parent window!
Jan 08 20:02:33 ppapadopoulos kernel: kauditd_printk_skb: 1 callbacks suppressed

I should also mention that pretty much anything I try with,

systemctl --user

returns

Failed to get properties: Process org.freedesktop.systemd1 exited with status 1

[brahma]

yes they are there… try also this:

systemctl daemon-reexec

and then:

sudo kill 1

reboot

[panos91txc]

still no luck…

[brahma]

in system settings/ login screen sddm/ behavior and select automatically login, with x11, click apply, reboot

[panos91txc]

It didn’t work. Still gets stuck…

[brahma]

well, im out of ideas, i would at this point just reinstall, and keep your home directory if you dont want to set up your system again…

[panos91txc]

I was just about to ask you the same thing. How do I proceed exactly and how do I keep the home directory in order to not lose files?

[brahma]

check this:

Reinstall Manjaro preserving the $USER files and settings

A topic from last month How to reinstall packages to default - #3 by linux-aarhus BE WARNED Even Gparted is a proven tool to do the job - the risk of losing data is always present when you work with the filesystem. The author of this guide is not to be blamed if you mess up and loose data. USING THIS GUIDE IS ENTIRELY YOUR RESPONSIBILITY. Target audience This guide has been written for a default Manjaro EFI based system using GPT partition scheme. Two partitions $esp partition as fi…

[panos91txc]

i’ll give it a go… fingers crossed. Thank you yet again for your patience and help!

[panos91txc]

I’m at the fsck step,
but when I run,

fsck /dev/sda2

where sda2=manjaro partition

it only results to,

fsck from util-linux 2.37.2

it doesn’t actually run fsck, only fsck’s version

what am I doing wrong? I run it as superuser and I have sda unmounted (running from live usb)