Check if the UUID of your encrypted drive matches in your config files.
Based on the manual, unlike filesystem UUIDs, UUIDs for encrypted devices must be specified without dash separators. So check /boot/grub/grub.cfg for entries like cryptomount -u 3722dfb2-3b32-414b-bd59-4329fa92b6a9 and try to remove the dash separators.
If you modified the above configuration, you then need to update the grub menu with sudo update-grub.
A message “no such cryptodisk found” may appear on the following reboot, but should not prevent you from continuing by typing any key.
You may still want to have a liveUSB ready, in the rare case your bootloader does break, in which case you will need to reinstall grub.
Switch to the base-devel meta package requires manual intervention
2023-02-12 - Robin Candau
On February 2nd, the base-devel package group has been replaced by a meta package of the same name.
If you installed the base-devel package group prior to this date, explicitly re-install it to get the new base-devel package installed on the system:
A solution, regarding to rob215x, is:
VLC would crash immediately when trying to play any video. I opened VLC directly, and changed Preferences > Video > Output from “Automatic” to “VDPAU” and it works now. I found that solution on another thread but I still don’t understand the problem and why VDPAU works.
PHP 8.2 update and introduction of legacy branch
2023-01-13 - Pierre Schmitz
The php packages have been updated to the latest version 8.2. In addition to this, a new set of php-legacy packages have been introduced. These will follow the oldest but still actively supported PHP branch. This enables users to install the latest version but also introduces the option to use third party applications that might rely on an older version. Both branches will be kept up to date following our rolling release model. php and php-legacy can be installed at the same time as the latter uses a -legacy suffix for its binaries and configuration files.
In addition to this, the php7 packages have been removed as they reached end of life. The imap extension will no longer be provided as it relies on the c-client library which has been abandoned for many years.
kernel zswap: compressor lz4 not available, using default zstd
kernel zswap: loaded using pool zstd/z3fold
But, when using kernel linux62:
kernel zswap: loaded using pool lz4/z3fold
I have set in /etc/grub to use “zswap.compressor=lz4” and “zswap.zpool=z3fold”. As is in the Arch zswap wiki. Manjaro uses zstd as default, I will change this to use zstd, by removing this parametres. But when I remove them:
kernel zswap: loaded using pool zstd/zsmalloc
Then, this is the defaults for Manjaro.
I read somewhere that lz4 and z3fold is better for zswap compression.
Feel like elaborating on the first part about yay, cause I just replaced pikaur cause I didn’t feel like building it by hand?
As for Octopi you don’t have pikaur in the Manjaro repos? I switched switched to it when I thought yay was end of life and refused and still refuse to use paru.
That said Seeing Octopi dropped won’t hurt my feelings. Never been a fan of it. Years back when I first tried out Manjaro it came with Octopi and because if it and something else which I don’t remember I dropped Manjaro like a hot potato. Since then I learned I could simply install any number of software managers. Any Arch distro I install gets pamac with aur, snap, and flatpak support even though I update through the terminal and us pacseek for finding software.
Nonsense! if you remove the applications with a bug, manjaro will be empty!
Why not also remove pamac at the first bug? yay’s engine was rewritten a few weeks ago, so it’s normal to have bugs right now and they are fixed very fast. If manjaro doesn’t trust the developers anymore, they better stop the distribution right away.
If manjaro doesn’t trust the developers anymore, they better stop the distribution right away.
Why we have branches? I thought it was for this case ???
Why block testing when plasma or gnome is a problem when it is easier to remove them.
yay -S "package_name" --answerclean All not work ? it’s your solution last year for python 3.9 to 3.10 and, i can’t found issue in forum eos and arch for this python update with yay …
This implies that if yay fixes the current issue, that it will be re-added to the repos. Is this the case? (If so, I agree that’s a weird reason to remove a long-time staple package from all Manjaro branches).
If that’s not the case, maybe be more straight-forward with the reasoning? i.e. Manjaro devs offer and support pamac, which is probably seen as having feature-parity with yay for most general use-cases, so maintaining yay in the repos is no longer easy to justify.
I don’t really have much skin in this - I mainly use pikaur, which can also be used for rebuilds as follows: