Manjaro KDE not able to boot - Stuck on loading screen

[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)

[brahma]

this is the only output?:

@panos91txc

fsck from util-linux 2.37.2

try forcing it:
sudo fsck -f /dev/sda2

---

and also you can just copy the home directory, with the hidden files and then just copy the configs folders back, for example from your browsers… etc …

---

more info:

Would my every setting recover if i just copy the home directory?

like panels’ positions, my cursor etc. or should i just copy the File System for all of my settings. [image]

How to reinstall manjaro with existing `home` partition?

My home directory is located at a separate partition. I want to install a fresh Manjaro deleting all the hidden files from home directory and keeping other files that are not related to configuration. How can I do so?

Install Manjaro KDE and keep Home partition from Kubuntu 20.04?

I have Home on a separate partition. I want to install Manjaro and keep my Home. Is this a good idea or a bad idea? System: Host: shmuel-Kubuntu Kernel: 5.4.0-42-generic x86_64 bits: 64 Desktop: KDE Plasma 5.18.5 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser/root required> UEFI: American Megatrends v: 1203 date: 10/10/2019 CPU: Topology: 8-Core model:…

[panos91txc]

@brahma

sudo fsck -f /dev/sda2

still only getting

fsck from util-linux 2.37.2

[brahma]

so there is something wrong with your system…
try:
sudo e2fsck -f /dev/sda2

you can use also kde partition manager from the live usb to check the partition…
but as mentioned just backup the home directory, install manjaro, and copy the folders from the backup into the new home directory… escpecially the browser folder and other program that you regularly use and have it set up… dont copy anything else…

[panos91txc]

@brahma

sudo e2fsck -f /dev/sda2

e2fsck 1.46.4 (18-Aug-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sda2 contains a crypto_LUKS file system

as I understand it, it fails because the drive is encrypted?

[brahma]

oh you have encryption, that could be a problem… can you access your files via dolphin?

[panos91txc]

yes!\ I am able to mount via dolphin

[brahma]

ok, i was worried, that the fsck on the encrypted partition messed it all up…
again, forget about the fsck, just do this:

@brahma

but as mentioned just backup the home directory, install manjaro, and copy the folders from the backup into the new home directory… escpecially the browser folder and other program that you regularly use and have it set up… dont copy anything else…

its better that way, to copy only the important programs and nothing else … also check the other links for more info if you are intersted