Content
I also didn’t know if Manjaro does an online install, so even if the ISO says 612, it could update it during the install to a newer version. Or if it does an offline install, if it would update the kernel upon first boot. But, if it’s using LTS kernels, then updates don’t happen that often.
After a big update yesterday ssh no longer works although installed
The latest packages are first made available on the unstable branch, then they get propogated to “testing” and finally “stable” as manjaro team decides the stability of those packages for general use. Well, it is still a manual process via our tool boxit. You might see daily updates on unstable branch for x86_64 simply cos our developers and package maintainers call boxit sync when ever they see a need to do so.
That’s why about a year ago, when I had to replace my Debian stable system on the Pi4 for ioBroker again, I decided to try Manjaro ARM—and I was impressed by how smoothly it worked. Personally, an ARM stable update every 3-6 months would be totally fine for me, though I know that might not be true for everyone. I really hope the situation around ALARM changes before the transition. Kernel-LTS and Node.js-LTS updates are especially important to me. Look the last unstable update, the feedback are looking good.
Onlyoffice Desktop-Editors segfault following 2025-02-16 update
Then we might need more people who might want to join the ARM team on our end and pick up what old members left of. When new tools like bxt get introduced at some point our workflow needs to be adopted or changed. When we talk ARM then the upstream distribution is currently Archlinux ARM or short ALARM. They do push packages to their repos and update their stuff. However, there might be a misunderstanding on how we get the packages from Arch or ALARM. When we look back to i686 architecture, Manjaro also had to maintain that architecture too.
Even when you use ARM parts of Manjaro, most likely you will also have some x86_64 machines you might run at your home with Manjaro too. Introduce “Arch Linux Ports” as testbed for unofficial architectures until they are integrated in the main Arch Linux repositories. This integration is meant to provide infrastructure…
If you would share a quick list of those extensions, it would be easy enough to verify which browsers will support them. Alternatively, the more-or-less equivalent chromium is in the extra repo and you could try installing and running that. The only other major change is that I’ve added an extra HDD and mounted it to /home/user/Data. But I’m storing there only backups and it is not within the baloo search database.
It helps to have always 2 kernels (one of them LTS)
So, posting here, even if vague, was a last line of defense move. You’ll notice from a quick Internet search that these reports are all current, and quite widespread. As of writing, there is no official fix for this issue, but you can use the following workaround.
Status of ARM Stable Updates: No Major Update Since March 2024?
I can also delete (or move) the ~/.config/google-chrome. This also is also suggestive of the issue remaining in current versions of Google Chrome, and potentially all Chromium-based browsers. If you have OpenGL selected as ANGLE, it can cause invalid output errors in the latest Chrome version and lead to a gray screen. You forgot to mention it was new install – not an update play plinko – as updates never installs new packages – they update existing ones.
I can understand well that you need more time and manpower for the ARM architecture, which is currently less utilized. Now the project has grown and has even more architectures than it had before. So we might also need to grow our team to give better support to those who use this distribution.