I do not get it.
no boot after update because no kernel (but before 3)
Update was wtih pacman -Syu. Hang after “upgraded micro-manjoro” with
"created symlink ‘/etc/systemd/system/multi-user.target.wants/micro-keymap,service’ >> ‘/usr/lib/systemd/system/mirco-keymap.service’
After 10min interrupt and start again pacman -Syu runs thru.
Not edit pacsave because I understand where is not important to change or I I read here 5 different thoughts about it …
Now I am in chroot and don’t understand what to change in etc/default/grub. Meld doesnt work, vm is my enemy and what is really the changes in grub ?
I moved your reply to a dedicated topic for further discussion and troubleshooting.
Please see:
not really understand the changes but for none professionals I recommend do take all changes of the grub.pacnew. I rename grub to grub.old and the rename the grub.pacnew to grub.
And of course update-grub. Good Luck !
Don’t recommend things you do not understand then. The proper way is to merge changes as written in many tutorials already.
Managing .pacnews is mentioned many times in this forum here already, good examples are explained, there is also an Arch wiki entry, also all other Arch based distro forums such as from EndeavourOS or Garuda provide some examples. Personally, as a first start to get used to this subject I like this link:
Looks like you need to (re)install a Kernel, e.g. linux618. Not sure if mhwd works in chroot these days, so do it with pacman e.g.:
pacman -Syu linux618
and
update-grub
… should do it, you might have to prepend with sudo though (I had to before at some point); you may also need headers for the Kernel though. We need your system information for that. ![]()
I can confirm. I did not have this package installed on any of my instances, but installing it yields the same results.
In the logs it just adds this:
Oct 17 14:41:05 mbox systemd[1]: Starting Micro keybindings in console...
And it’s been going for 15 min before I Ctrl+C'd it.
Removing this one package would be a workaround until it’s fixed.
e.g.
sudo pacman -R micro-manjaro
sudo pacman -Syu
Fixing that bug (or removing the package or reverting the changes) will be at @Yochanan 's power.
Reinstalled Grub completely new, now working.
Don’t understand what happens. I don’t think it was a .pacnew problem.
In 2 VMs similar problems. (with edit config file and install+update grub)
My understanding from past was:
A new version of grub on a running system do nothing. You have for changes do a manuel install. Always a little bit risk: your system, your responsibility …
So if I do NOT update-grub and not install-grub nothing bad could happens.
That was I take with from the last big grub updates (=problems ?!?) …
But I am to silly for these things.
But this update in stable: big trouble will rise
My thoughs
PS:
Yes , the “micro-manjoro” freeze by creat symlink problem happens in 2 different VMs, too
I think what what happened was, due to the bug in micro-manjaro 3.0-6 the update hung, you force stopped it and there were unfinished things to do, like for example the update-grub hook which is a postupdate task. @Yochanan is the packager, he is pinged to check where is hangs. Until it gets fixed, do not use the package, it is not critical anyways.
Can we mark this solved or finished without proper solution now?