After updating, I first noticed that the login under wayland took much longer. But after it all came up, it worked fine.
Then when my computer hibernated for the first time, I found that I was unable to get the screen to wake up without closing the laptop lid and reopening it. At which point I could type in my password and it would again take a long time to bring up the desktop.
The reason I suspect that it might be a compositor issue is because when I went into the system settings looking to change my resolution to default 100% from it’s current 125% thinking that THAT might be an issue, the Display and Monitor section specifically lagged and froze for the same amount of time as the login screen would.
Doesn’t happen under X11, but I’d rather not go back to X11 on this laptop because it’s a touchscreen, which wayland handles far better.
Any advice on what I look at reports wise to troubleshoot what’s happening?
You could start by providing system information as described (below), which will allow others to quickly rule out a range of possible contributors.
I’m sure someone will help as soon as they are able.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
Update Announcements
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;
Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
I decided to do a fresh install since most of my important stuff was on removable storage anyway.
After the reinstall with a fresh copy of the 2503 ISO, everything worked great again. But upon doing the first update after install, it immediately went back to the same issues, forcing a Timeshift restore.
Slow from login to desktop. Slow to wake from hibernate. Occasional reboot getting stopped by a “fail to mount root…dropped into root shell” or something like that message. Random crashes.
I’m going to have to stay unupdated for a little while to see if I can deduce what the issue is, or (hopefully not) try a different distro entirely.
The name 2503 is not an official Manjaro Linux release - I am speculating, where did you obtain that ISO?
Of course you may just have confused the Manjaro ISO with - what ever you used provided by MrChromebox-2503.0
If hibernation is a must - I am thinking that using a dedicated swap partition would perform better than a swapfile - fragmentation wise.
What exactly got updated? You can find the information in /var/log/pacman.log
This points to an issue involving the storage device holding your operating system files.
This could be driver related - which again would involve the kernel - which involves the answer to where you obtained the ISO - and which kernel was supplied with the ISO.
One may speculate if the kernel from the ISO has been specifically built for the Chromebook?
I can only echo the above comments regarding swap.
With only 4GB of physical RAM, it’s not uncommon for a system to require a great deal more swap space, and with your / partition usage already high there may come a time when a swapfile is impractical.
If additional storage is a consideration, moving your /home to a secondary SSD and expanding / to a greater capacity might help to prevent that eventuality.
Increasing RAM might also be worthwhile.
The ISO.
Did you check the ISO for consistency? Assuming an official Manjaro ISO, a newly downloaded ISO can be verified against the (also downloadable) .sha256 checksum file.
If the ISO is damaged in any way (doesn’t match the checksum), and if you used the same ISO for both installs, then it stands to reason you might experience similar issues.
On the other hand, if the ISO is sound, then the problem is elsewhere; perhaps your disk itself, as suggested by @linux-aarhus .
Sorry for the confusion. Manjaro 2503 is just the short name that DD assigned to the USB stick when it burned the ISO.
the iso file was downloaded from the official website. manjaro-kde-25.0.3-250526-linux612.iso
I re-downloaded it brand new when re-installing. But that new ISO hadn’t presumably been updated to be the new stable (still on the May 26th stable). So the immediate update needed when installed would be the update taking me to the June stable, which is why it caused the same issue.
I’m wondering if I should wait for the June stable ISO to be the one included on the download page and see if that makes a difference.
When I have a second I’ll go track down the pamac logs.
The easy method is to use get-iso from manjaro-get-iso-package to download and verify the ISO.
$ get-iso -p plasma
==> Storage dir: /home/fh
==> Working dir: /tmp/tmp5oeyzxg5
-> Processing plasma ISO
--> Download: manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso.sha256
--> Required space on tmpfs: 6399 MiB
--> Required space on storage: 3151 MiB
--> Download: manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso.z01
--> Download: manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso.zip
-> Testing archive integrity...iB
-> Unpacking ISO to /tmp/tmp5oeyzxg5...
--> Moved 'manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso.sha256' to '/home/fh'
--> Moved 'manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso' to '/home/fh'
-> Wait for checksum to complete...
--> Checksum verified. manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso: OK
-> Cleaning up...
==> ISO file: manjaro-kde-dev-25.06-development-unstable-minimal-250628-linux615.iso
==> Storage : /home/fh
Used the latest ISO available on the forum, booted from the live image. But when I went to install it fresh, it said “there are no partitions to install on”.
So I guess the update from the may stable to the June stable, or a fresh install of the June stable directly, just doesn’t like the mmcblk. But it also doesn’t give me an option to re-partition manually.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 116.5G 0 disk
├─mmcblk0p1 179:1 0 300M 0 part /boot/efi
├─mmcblk0p2 179:2 0 108G 0 part /var/log
│ /home
│ /var/cache
│ /
└─mmcblk0p3 179:3 0 8.2G 0 part [SWAP]
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
The above is my lsblk from the current install of the May stable. This is now heading way past my knowledge level…
Did you opt for BTRFS (the new default) or choose EXT4 filesystem?
The manual partitioning method would be the most practical with BTRFS.
This indicates that you hadn’t prepared your system. To install Manjaro there must be unallocated space available; this means removing your previous partition(s).
At that point, it didn’t let me choose any options. It never even got to that screen. Simply said “There is no partition” and grayed out the “continue” box which would have taken me to the partition manager portion of Calamares on the next screen.
Regardless. I re-updated my firmware and tried again and this time I was able to install the June Stable ISO. It seems to be working fine…
To be safe, I formatted it as swap with no hibernate just in case so I’ll see if it continues to act up the next time I’m away from the computer for long enough for it to go idle.
Okay. So here’s what I’ve discovered. I wanted to put it all in here so that it’ll show up in searches for other people with the same issues.
It wasn’t one issue causing problems. It was two. One from the Chrultrabook firmware and one from the grub config and modprobe. They just all got triggered from the upgrade to the June Stable. So I’m going to take them one by one.
LOGIN AND WAKE LAG TIME
CAUSE: install of iio-sensor-proxy that was used to get my rotating touch screen to work in Wayland. Stumbled upon it completely by accident while setting up my laptop to do everything it used to do. As soon as I installed iio-sensor-proxy I immediately started having e. Uninstalled it…went away.
UNABLE TO MOUNT UUID ON “REAL ROOT” during a restart
This one held on forever. Took years off my life googling and trying the multiple different solutions that appeared. If I powered off and then powered on using the hardware button, all was good. But doing a restart the software would fail every time.
In the end, the solution that worked was to create a .conf file in modprobe.d and blacklist cros-ec-uart.
It also was a specific issue with NVME storage devices, so in my grub config I added nvme_load=YES to the command line defaults.
It seems to be the combination of those two that fixed the issue for me. Other possibilities like rebuilding the fstab, etc… took me nowhere.
Hope this helps anyone else googling for answers to this frustratingly specific set of issues…
