Workaround for version 1.13 new install & upgrade not working after boot

[OmarSkalli]

Thanks to harpreetchima, nik-securemeasure, ryanrhughes, and others for the workaround to #688.

Below are the summarized steps to restoring Omarchy:

STEP 1)

1. a) If you are on systemd and you see the screen below:

During the bootloader:

1. press e
2. Scroll all the way right to the end of the existing command
3. Add the following at the end: systemd.unit=single-user.target
4. Press enter

1.b) If you are on grub and see the screen below:

1. Add single where indicated in the screenshot, followed by ctrl + x to continue in rescue mode.

STEP 2) When you see the Omarchy login screen, log-in as usual

STEP 3) When you're prompted Enter root password for system maintenance. Enter your sudo password.

Step 4) In the terminal, enter the following to downgrad your version of uwsm:

systemctl start systemd-networkd
systemctl start systemd-resolved
sudo pacman -U --noconfirm https://archive.archlinux.org/packages/u/uwsm/uwsm-0.23.0-1-any.pkg.tar.zst

Note: if you are using wifi, you will also need to: systemctl start iwd

STEP 5) Reboot your machine:

reboot

STEP 6) Cross fingers, and hopefully things are resolved for now. Until there is a better fix, refrain from updating uwsm

[GuzmanPintos]

Thanks for this guide. If you're running on WiFi, you'll likely need to run systemctl start iwd to get a working network before executing sudo pacman -U --noconfirm https://archive.archlinux.org/packages/u/uwsm/uwsm-0.23.0-1-any.pkg.tar.zst.

[rondilley]

Using 'e' on the "Arch Linux" in systemd did not boot out of the problem, but selecting linux-fallback, 'e' and adding single did get me to a maintenance shell and from there, I was able to backout the uwsm update.

[hritikjm]

Using 'e' and adding systemd.unit=single-user.target gets me to put in the password to access btrfs in either of the options(linux/linux-fallback), but then it says "Cannot open access to console, the root account is locked." Press enter to continue, which then goes back to the problem. Edit: I had not setup a root password during archinstall.

[hritikjm]

To fix it i chrooted into my installation with a live usb and then followed the guide. For anyone who can't chroot I did the following:
1.Start the arch live usb
2.lsblk/fdisk -l to find your root partition
3.cryptsetup luksOpen /dev/your-root cryptroot
4.mount /dev/mapper/cryptroot /mnt

This put me in the chroot where I connected to my wifi and put sudo pacman -U --noconfirm https://archive.archlinux.org/packages/u/uwsm/uwsm-0.23.0-1-any.pkg.tar.zst

[jelcke]

I could logon and execute comand by pressing alt-F3 and then I had half a second input a character so I could finish downgrade. Oufff...

[nikkos]

This solution didn't work for me because the root account was locked. I solve with arch ISO boot. https://docs.google.com/document/d/1MXZ3i70mjcOJLX3vqL5ndbY8hIeB1GIuOG8xVj7-BYg/edit?usp=sharing

[hritikjm]

After cryptsetup try doing "mount /dev/mapper/cryptoroot /mnt" and then directly "arch-chroot /mnt"

[markjfisher]

My systemd-boot arch entry wasn't unlocked, so I couldn't edit it.
Fortunately, I have sshd running, so let it boot, and on my laptop connected via ssh, and used the pacman command.
The screen immediately was fixed without having to reboot the machine.

Thought I'd post this in case others had the issue, and didn't want to revert to a usb stick, but did have sshd running like myself.

[timmo001]

HOLY **** this literally would have saved me 5 hours of my life...

I did this in a roundabout way, learned a lot about uwsm, display managers, read and tried to edit a little bit of C, edited systemd services, installed sddm, ran hyprland from tty, only to read the commit message I had open before I hit reboot.

Anyway that last command solved my issue. This package 100% needs to be pinned and tested before anyone can accidentally run the omarchy-update script.

I'm actually a little confused why omarchy-update-git is used/done this way, surely it would be best if it would look for tags/releases, not pull from master?

[timmo001]

One other thing, the systemd service restarting every 2 seconds stopped the ability to drop to tty2 etc.

I'm not sure how possible this is, but catching the uwsm errors and stopping the restart loop would super useful here

[afgallo]

Thanks @OmarSkalli this has fixed it for me!

Thanks to harpreetchima, nik-securemeasure, ryanrhughes, and others for the workaround to #688.

Below are the summarized steps to restoring Omarchy:

[Lofiwaffle]

Thank you so much. You saved me. May be a stupid question, but how do I prevent upgrading uwsm and will this be patched in the near future?

[1hemmem]

Edit the pacman.conf

Find the the following line:

#IgnorePkg =

And change it to:

IgnorePkg = uwsm

this way any updates by pacman will ignore uwsm, it will work keep it this way until they release a fixed version

[adsovetzky]

This solution didn't work for me because the root account was locked, it also didnt work with arch iso boot, i also try to reinstall uswm and it didnt work too. What should i do?

Note: i dual boot

[pupa4u]

This fix worked for me. Thank you.
Running systemd
i9-13900kf / RTX 4080
Intel m.2 wifi.

[curtisspendlove]

The new update is replicating through the repos; but it's a good idea to test for it in your repos before unpinning and updating:

YOU, of course, should spell uwsm correctly (though pacman is pretty good at fuzzies) and probably won't have corrupted fingerprint sensor data.

[madanbazgai]

It worked for me, thank you!

[thegreyfellow]

I did not know about these fixes, so I did the following:

• I had my wife on a second keyboard typing ALT+FN+3, after every flash of the screen.
• Every time I get a few seconds I type my login, then password, until I logged in
• Run "yay -Syu" to update my packages.
• Had to retype my password AGAIN (Screen was still flashing with unit error mind you!!)
• Then hyperland popped up working just fine.

It took one try, and now my wife used linux for the first time ever ! Thank you for this bug uwsm !

[timmo001]

• I had my wife on a second keyboard typing ALT+FN+3, after every flash of the screen.

Thats one way around it 🤣

[RowdyRagamuffin]

This was my solution minus the wife helping. Fun was had!