root tip How To Make Manjaro compatible with major VPN providers Tutorials Manjaro Linux Forum
Content
So I’ll just use –disable-gpu for a while until the next update. The description of this ANGLE bug does not fit perfectly my bug. In my case, when chrome opens, I can see the window, but it is kind of translucent and not gray. Since they share the same code-base I would expect any chrome extension to work in chromium, so trying that is still an option.
Getting a “QXcbConnection: XCB error” everytime I try to open Aegisub
Of course, I do regular backups, but ioBroker should run without interruptions, and having to restore because of an update issue would be quite annoying. I can simply use –disable-gpu as temporary workaround. But I understand and appreciate plinko slot you all positioning towards open-source browsers. Chrome is the only app that takes my soul, everything else I use is open-source. I’ve tried to abandon Chrome in the past and use many others (chromium, firefox, vivaldi, opera, brave, …) but in the end I want something smooth on desktop + mobile, and I always go back to chrome. Ok, I know I can manually install whatever kernel I want, but I was wondering what Manjaro installs by default.
It helps to have always 2 kernels (one of them LTS)
I assume this happened because of the dmenu-manjaro package that got updated lately. If you have installed it via the AUR, perhaps the version is older, and no longer compatible. Removing it and installing the repo version might help. Hello @philm, thank you very much for your time and detailed response.
root tip How To NordVPN on Manjaro
It was working before, and it suddenly got this weird behavior. If I call without the tag above, the window opens, but not responsive. An update does not install new kernels – only update existing ones – so the update didn’t install 6.1 – you did. So if the future you should spot a KB article on NordVPN on this issue – you know where it came from.
LTS kernels are updated at the same pace as anything else in the system. But it is important here to make the distinction between an update and a version bump. That is the version the ISO uses – and what will be installed initially.You can very easily change it if you so desire.At any time.You can have two or more installed to choose from as well. This topic was automatically closed 15 days after the last reply. Check if sshd.socket is enabled with “systemctl status sshd.socket”. If it is, disable it and enable “sshd.service” (if you haven’t yet).
I hope this small approach could be helpful to you. I’m not a power user but I switched to unstable branch with success, so far the OS is stable. By default, Manjaro will not version-bump kernels during an update. However, if you’re not using an LTS kernel, then you need to pay attention, because if you happen to be running an EOL kernel, then it may get removed as part of the bundled-update process. That’s exactly the 3 commands I did yesterday before the upgrade. Today I have repeated exactly those 3 commands and for the last 2 I get “Unit ssh.service not found” despite ssh being installed.
Whether you are using an app offered by your provider or you are using configuration files it is of utmost importance you ensure correct configuration of DNS. Or not.I didn’t install that one – it is an optional dependency. As indicated, the versions did seem different, thus the suggestion. I’ve been using Manjaro x86_64 (KDE) for several years, and I particularly like the stable, rolling OS.
