Content
The only items left standing are dmenu-manjaro, which depends on manjaro-i3-settings which was also recently updated. I had to scale back my work since my heart attack. I build the 6 new latest pi kernels a week along with the boot related packages and eeprom and push them to unstable. So, I wonder if there’s a way I could support you. I still have a Pi4 in my drawer and could install the latest ARM testing update on it in the coming days. Then, I’d be happy to test how it works with my configuration, especially with pi-hole and ioBroker, and report back to you.
Manjaro default resolver
In my work I use extensions available only on play plinko Chrome. I personally recommend Firefox, but it might be worth your effort to try a major Chromium-based alternative such as Vivaldi, in case they have already dealt with the issue. An obvious workaround is to use another (non-Chromium-based) browser until whatever the issue may be is fixed upstream. A reminder that Chrome has frequent recent updates, which may or may not be reflected when sourcing it via the AUR.
Morc_menu on i3 stopped working (conflicting w/ dmenu-manjaro or manjaro-i3-settings?)
Such as, KDE Plasma 6.4 being released today (6/17). I usually install the most recent LTS kernel (currently linux612), and the latest kernel. Although I’m holding off installing linux616 (which is still a release candidate) until the next RC version arrives, as the current RC prevents my system from waking up. Systemctl enable sshd still works for me; it creates the sshd.service symlink as expected.
Manjaro Linux – Browse Files at SourceForge.net
However, since the ARM team changed and not all supported devices are at our end for testing, less updates were made to arm-stable branch. Device images are currently only auto-generated but not tested at all. There will be some updates to arm-unstable branch, but those might be just kernels or few packages.
The workaround would at least help minimise disruption of your workflow until the actual cause and solution is discovered. Those browsers that feature their own “addon store” usually have a setting to also allow addons from the Google counterpart. I’ve tried searching around for this issue a lot on the internet and got no luck.
I’ve moved this to it’s own topic as you will hopefully get better attention and support. Manjaro uses Network Manager and openresolv to set dns servers. Before I did anything I inspected the /etc/resolv.conf and that was a give-away – Ubuntu uses systemd-resolved where I know Manjaro uses resolvconf from the package openresolv. Anyway, I unchecked this as solved because now I think it’s possible there was never any problem. Maybe just the command wasn’t getting through right away on my system and so was sending an error. The link is coming after enabling the service because you cannot force a link to a non existing file – and the stub only exist after systemd-resolved has been started.
@philm is fixing to snap testing to stable in the next few days. That will put all of the branches with the same toolchain. So you would be able to install the latest kernel and other pi related packages if needed from unstable branch and still use the stable branch for the other packages. You could do that anyway regardless of toolchain version if you do not have any DKMS/3rdparty modules to build. So the whole process we somehow managed to do in 2 months.
On ARM side this happens not so often or for some months not at all. I use Manjaro ARM headless in production for Pi-hole and the SmartHome system ioBroker, so I prefer the stable branch. Even though the unstable branch is currently running well, there’s no guarantee it will always be like that.
