Need guidance regarding setting up snapper with limine

[Optimus-Prime]

I was following this guide here

Is there a decent guide for converting from Grub to Limine?

ok let’s start the drama: procedure tested on two of my laptop with Mercury btrfs and grub installed. 1st increased boot partition from 1 gb to 3 gb 2nd followed procedure of Dalto (God bless and safe him ) for return back to systemd Next we need to remove grub: sudo pacman -Rc grub Next, we can cleanup /boot to prepare for the changes sudo rm -r /boot/efi /boot/grub /boot/initramfs* /boot/vmlinuz* Now we remount the EFI partition to /efi. sudo mkdir /efi efidevice=$(fin…

and everything seemed to be okay , until I booted from a snapshot
this is journalctl output from snapshot boot.

journalctl -b | grep -i “Failed”
Jul 05 22:31:07 EndeavousOS kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jul 05 22:31:09 EndeavousOS kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get target temp from SBIOS @ platform_request_handler_ctrl.c:2174
Jul 05 22:31:09 EndeavousOS kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get platform power mode from SBIOS @ platform_request_handler_ctrl.c:2117
Jul 05 22:31:09 EndeavousOS kernel: pci 10000:e0:06.0: bridge window [io size 0x1000]: failed to assign
Jul 05 22:31:09 EndeavousOS kernel: pci 10000:e0:1d.0: bridge window [io size 0x1000]: failed to assign
Jul 05 22:31:09 EndeavousOS kernel: pci 10000:e0:06.0: bridge window [io size 0x1000]: failed to assign
Jul 05 22:31:09 EndeavousOS kernel: pci 10000:e0:1d.0: bridge window [io size 0x1000]: failed to assign
Jul 05 22:31:11 EndeavousOS systemd[1]: systemd-remount-fs.service: Failed with result ‘exit-code’.
Jul 05 22:31:11 EndeavousOS systemd[1]: Failed to start Remount Root and Kernel File Systems.
Jul 05 22:31:11 EndeavousOS systemd-remount-fs[521]: mount: /: fsconfig() failed: overlay: No changes allowed in reconfigure.
Jul 05 22:31:11 EndeavousOS systemd-remount-fs[521]: dmesg(1) may have more information after failed mount system call.
Jul 05 22:31:12 EndeavousOS (udev-worker)[583]: cfg80211: Process ‘/usr/bin/set-wireless-regdom’ failed with exit code 1.
Jul 05 22:31:12 EndeavousOS systemd-remount-fs[681]: mount: /: fsconfig() failed: overlay: No changes allowed in reconfigure.
Jul 05 22:31:12 EndeavousOS systemd-remount-fs[681]: dmesg(1) may have more information after failed mount system call.
Jul 05 22:31:12 EndeavousOS systemd[1]: systemd-remount-fs.service: Failed with result ‘exit-code’.
Jul 05 22:31:12 EndeavousOS systemd[1]: Failed to start Remount Root and Kernel File Systems.
Jul 05 22:31:13 EndeavousOS avahi-daemon[734]: Failed to parse address ‘fe80::e21c:fcff:fe63:7973%wlan0’, ignoring.
Jul 05 22:31:14 EndeavousOS dbus-broker-launch[731]: Activation request for ‘org.freedesktop.home1’ failed: The systemd unit ‘dbus-org.freedesktop.home1.service’ could not be found.
Jul 05 22:31:15 EndeavousOS wireplumber[946]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Jul 05 22:31:17 EndeavousOS dbus-broker-launch[731]: Activation request for ‘org.freedesktop.resolve1’ failed: The systemd unit ‘dbus-org.freedesktop.resolve1.service’ could not be found.
Jul 05 22:31:17 EndeavousOS NetworkManager[737]: ((../NetworkManager/src/libnm-systemd-core/src/libsystemd/sd-event/sd-event.c:4458)): assertion ‘’ failed
Jul 05 22:31:17 EndeavousOS plasma-login-greeter[942]: failed to create compose table
Jul 05 22:31:18 EndeavousOS kwin_wayland[895]: atomic commit failed: Permission denied
Jul 05 22:31:18 EndeavousOS kwin_wayland[895]: Failed to open drm node: “/dev/dri/card0”
Jul 05 22:31:21 EndeavousOS dbus-broker-launch[731]: Activation request for ‘org.freedesktop.ModemManager1’ failed: The systemd unit ‘dbus-org.freedesktop.ModemManager1.service’ could not be found.
Jul 05 22:31:21 EndeavousOS kded6[1245]: Failed enumerating MM objects: “org.freedesktop.DBus.Error.NameHasNoOwner”
“Could not activate remote peer ‘org.freedesktop.ModemManager1’: activation request failed: unknown unit”
Jul 05 22:31:21 EndeavousOS dbus-broker-launch[731]: Activation request for ‘org.bluez’ failed: The systemd unit ‘dbus-org.bluez.service’ could not be found.
Jul 05 22:31:21 EndeavousOS kded6[1245]: PendingCall Error: “Could not activate remote peer ‘org.bluez’: activation request failed: unknown unit”
Jul 05 22:31:22 EndeavousOS org_kde_powerdevil[1291]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed “Charge thresholds are not supported by the kernel for this hardware”
Jul 05 22:31:22 EndeavousOS org_kde_powerdevil[1291]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed “Charge thresholds are not supported by the kernel for this hardware”
Jul 05 22:31:22 EndeavousOS ksmserver[1243]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.ksmserver’”)
Jul 05 22:31:22 EndeavousOS xembedsniproxy[1292]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.xembedsniproxy’”)
Jul 05 22:31:22 EndeavousOS gmenudbusmenuproxy[1288]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.gmenudbusmenuproxy’”)
Jul 05 22:31:22 EndeavousOS polkit-kde-authentication-agent-1[1290]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Unable to open /proc/1290/root”)
Jul 05 22:31:22 EndeavousOS kactivitymanagerd[1281]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.ActivityManager’”)
Jul 05 22:31:22 EndeavousOS kded6[1245]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.kded6’”)
Jul 05 22:31:22 EndeavousOS org_kde_powerdevil[1291]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.org_kde_powerdevil’”)
Jul 05 22:31:22 EndeavousOS org_kde_powerdevil[1291]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:22 EndeavousOS ksecretd[1067]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:22 EndeavousOS kaccess[1289]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:22 EndeavousOS python[1488]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘’”)
Jul 05 22:31:22 EndeavousOS gmenudbusmenuproxy[1288]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.gmenudbusmenuproxy’”)
Jul 05 22:31:22 EndeavousOS polkit-kde-authentication-agent-1[1290]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Unable to open /proc/1290/root”)
Jul 05 22:31:22 EndeavousOS kdeconnectd[1437]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:22 EndeavousOS kded6[1245]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.kded6’”)
Jul 05 22:31:22 EndeavousOS xembedsniproxy[1292]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.xembedsniproxy’”)
Jul 05 22:31:22 EndeavousOS kactivitymanagerd[1281]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.ActivityManager’”)
Jul 05 22:31:22 EndeavousOS xdg-desktop-portal-kde[1585]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:22 EndeavousOS ksmserver[1243]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.ksmserver’”)
Jul 05 22:31:22 EndeavousOS plasmashell[1256]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
Jul 05 22:31:25 EndeavousOS konsole[1645]: failed to create compose table

I don’t understand these completely ,but some seem concerning to me
Kindly guide me .
What should I do?

and before anyone asks , I installed most packages from pacman ,

limine-dracut-support

limine-snapper-sync,

Only these were installed from AUR and I inspected the pkgbuild as well ( to the best of ym knowledge ofcourse)

[mbod]

@Optimus-Prime

What should I do?

First thing I would do is to feed the log to perplexity, explain your setup and ask proper questions to it. In most cases you will receive an answer which is pointing in the right direction.

[Cphusion]

I would start here and see how far you get with it.

Snapper snapshot integration for Btrfs - Limine - ArchWiki

[BluishHumility]

The log you posted doesn’t seem out of the ordinary for booting to a snapshot. It is normal to get some errors in the log when booting with the overlayfs, for example that is almost certainly the cause of those systemd-remount-fs errors.

Keep in mind when you boot to a snapshot, you are not really supposed to use the system in that state. Once you get to the desktop you should restore a known good snapshot, or otherwise repair your system from that environment. Then reboot into the “normal” (i.e. not overlayfs) system.