Content
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.
It’s fantastic to hear that @philm will soon be syncing the testing snapshot to stable, allowing all branches to use the same toolchain. This will definitely make it easier to install the latest kernel and Pi packages from unstable while keeping the rest of the system on the stable branch. This flexibility will surely benefit many users, especially those who don’t rely on DKMS or third-party modules.
But, if you like, we can just close the topic without the solution. If I’d just waited for ten minutes maybe they’d all have worked, I don’t know. Anyway I restarted and now ssh does seem to be running as a service on startup. I just need to reboot and see if ssh is now running as a persistent service. Same issue on my other computer with manjaro after upgrade. Since the dawn of Manjaro, the network has been configured using NetworkManager and resolved provided by openresolv package.
After a big update yesterday ssh no longer works although installed
@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.
Getting a “QXcbConnection: XCB error” everytime I try to open Aegisub
The error occurs because of the default settings of morc_menu in its configuration file ~/.config/morc_menu/morc_menu_v1.conf. Hi @jolic, thx for asking what the situation with stable updates on ARM are. You can check the packages mailing list to see how many syncs, pushes or commits were done to the binary packages repositories and by whom.
Troubleshooting NordVPN on Manjaro
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.
It helps to have always 2 kernels (one of them LTS)
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.
Yes – various helpers exist – but they are only required if one uses openresolv and the whole intent of the topic is to mogrifiy the end-user’s system to use systemd as resolver. Oh, and I also am reminded that openvpn-update-systemd-resolved AUR package is handy for anyone using an openvpn connection. This topic was automatically closed 3 days after the last reply. Well, first we have to reduce all supported images and only focus on the few we might have devices on our end.
Status of ARM Stable Updates: No Major Update Since March 2024?
In my work I use extensions available only on 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.
For some reason after the upgrade it seems the command has changed or something. The arch wiki contains the necessary information to correctly deal with DNS issues when using OpenVPN configuration files. Perhaps plinko casino game some of these – as they are labelled as Alternative frontend – are not working well together? This is pure speculation – I didn’t install those when I tried this quite elegantly looking program.It simply worked for me and I was guessing that your config file could be at fault. As a new user the frozen screen resembles the “gray” screen described in recent bugs. Someone suggested me to delete de ~/.cache/google-chrome, but it didn’t fix it.
