I ignored and now I can’t boot ( some kind of BLue screen
Something I can do or I reinstall ?
BlueScreen
BlueScreen
Can’t boot anymore after installing the last update using :
sudo pacman -Syu --ignore icu --ignore flac
I know it was not a good move but from here, I reinstall or what ?
I used that command after getting this error when updating :
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron28
:: installing flac (1.5.0-1) breaks dependency 'libFLAC.so=12-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron30
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron30
:: installing flac (1.5.0-1) breaks dependency 'libFLAC.so=12-64' required by electron30
Mod edit:- Please enclose any code or command output appropriately for preformatted text. This has been done for you this time. In future you are expected to do it yourself.
No, not necessary.
You just need to boot from a Manjaro ISO, like the one you used when you installed the system.
The use the tool manjaro-chroot that is present on this ISO to chroot and fix your system.
Start by removing blocking AUR packages like electron28 and electron30 - AUR packages in general - you can reinstall what you need of them after the base system is updated.
Use pacman rather than pamac - but this is “just” my preference.
1 Like
tks !!!
So I : simply remove electron28 and electron30 and try to boot ?
What about electron after that, if something on my system needs it ?
My installation is encrypted but I found some info how how to chroot in an encrypted system
Note: So i’m not crazy, it’s possible that this electron thing is guilty of my blue screen ? THANKS FOR YOUR TIME !! I was about to reinstall
Holding back package updates is responsible for your blue screen. After removing the outdated electron packages that block the update, perform the update in the chroot environment without ignoring any updates.
2 Likes
in short:
lsblk -f to find the needed partitions
sudo cryptsetup open /dev/name_of_partition encrypted to open the encrypted container
sudo mount /dev/mapper/encrypted /mnt to mount the / file system to /mnt
don’t forget to mount the EFI partition if you have an EFI system
sudo mount /dev/sdxY /mnt/boot/efi as an example in that case
manjaro-chroot /mnt /bin/bash to chroot
no sudo needed anymore once inside chroot - you are root - be careful
exit to exit chroot when finished
3 Likes
Much appreciated…
WIll let you know how it went
Do you mind telling what info you found and where?
I’m just curious - and could perhaps use the reference in the future when others need assistance.
Boot up from the live USB, chroot into your installed system, remove the IgnorePkg on icu from /etc/pacman.conf, and run the update process again.
Make sure you do as recommended, i.e. remove the blocking packages first, and then rinse and repeat. 
1 Like
Please create only one thread on the same topic. Both have now been merged into one.
2 Likes
This has come up for me once or twice - you can simply purge the AUR package and if you’re worried, make a note of it… then later on reinstall (but ONLY if you find out why you needed it - otherwise just let the bloat fall away and rejoice!!!).
I’ve dumped 2 versions of electron in the last few months - often it’s included as an ‘optional extra’.
I still have electron34, electron27, electron 31, 32, 33… it’s not like I’m going to run out soon!!!
List orphans in a pager with colour:
pacman -Qdt --color=always | bat
Good pagers include bat, moar. You can type / and type to search ‘electron’.
1 Like
Something to keep in mind. On the rare occasion that an application still requires an older verion of Electron, a binary (usually denoted by “-bin” at the end of a filename) of that version can usually be found on the AUR.
For example, electron29-bin which can be installed later, if needed, until the application author/maintainer plays catch up.
pamac build electron29-bin
Regards.
Use a live Manjaro ISO to boot the system. If you don’t have one - either download an official ISO or a dedicated Manjaro Rescue ISO from manjaro.dk
Open a terminal and change root to the system on disk.
manjaro-chroot -a
Select the system you want to mount by it’s location
inside chroot
Create a list of alien packages
pacman -Qqem > /alien-package-list.txt
Remove all
pacman -Rns < (pacman -Qqem)
If the remove all fails - using the sledge hammer
pacman -Rdd < (pacman -Qqem)
Then run a full system sync
pacman -Syu
Exit chroot and reboot the system
system restored
Evaluate the content of the alien-package-list.txt and rebuild only those required for your day-to-day operation.
Thanks to everyone !!! WOW very much appreciated
Taking care of my grandkid for 3 days but will soon have time to try everything and get my laptop back on it’s feet !
Work from home or on the road so that laptop I messed up is important to me…
I could have reinstalled but want to avoid it.
Hi @Nachlese
I 99% of the time use https://grok.com/ now (almost Not googling anymore)
Here is the info I found for chroot encrypted partition.
https://x.com/i/grok/share/iHRdICIoXD4icIw7nFigtbzsd
Thanks.
It may be accurate - although they start with mentioning Manjaro, but then go on to give generic advice (not using manjaro-chroot)
and the mount procedure, although generic, is different than I have seen anywhere else.
All --bind mounts.
it might work, but is not using Manjaro’s tool manjaro-chroot - which would make it easier.
This is generated content, then - rather than what some actual person wrote up as a guide and from actual experience.
Like the Arch Wiki - or the howto’s here in the forum are.
Thanks for the feedback - but this, once again, turns me away from asking “AI” anything.