I am new to the Manjaro/Arch world. However, I’ve been using other linux versions for more than 30 years. In recent years, I’ve been regularly using Debian, Ubuntu, and LinuxMint.
I want to try Manjaro, and I have installed it on an x86_64 laptop.
I use zsh, and I have a few decades worth of zsh configuration that I always install and use.
After installing Manjaro (manjaro-xfce-26.0.4-260327-linux618) – which, of course, comes with zsh by default – I installed my standard zsh startup configuration files, but now I keep getting “_p9k”-related shared library errors in zsh.
I don’t want to use any powerlevel10k theme (nor powerlevel9k nor any powerlevel software at all) in zsh. How can I totally and permanently disable the use of this powerlevel*-related software in Manjaro zsh? This way, I can use the zsh configuration that I’ve been accustomed to for decades.
Thank you very much in advance.
UPDATE: And to be clear: I don’t want to try to figure out how to somehow configure zsh or powerlevel10k to be compatible with my accustomed zsh setup. All I’m willing to accept is a total, complete, and permanent disabling and removal of all powerlevel software.
I did, but I’m not sure which of the standard Manjaro zsh settings will be safe to remove. Should I remove each and every one of the zsh-related packages except the zsh base package, itself?
I might be helpful if you post the errors, so we can narrow things down.
Check your config for anything related to powerlevel 9k, or powerlevel 10k.
I have my own zsh config and neither Manjaro’s config nor powerlevel10k cause any issues despite being installed.
Did you merge your config with Manjaro’s? If so then just use your config, if not then I don’t see how it could be anything but your own config causing this. Unless you need to restart your terminal to remove the old config completely.
That’s way if you want remove completely powerlevel10k and manjaro’s zsh config but if you want only not using powerlevel10k features (it’s responsible only for prompt) you can simply comment or remove these lines in your ~/.zhsrc:
# Use manjaro zsh prompt
if [[ -e /usr/share/zsh/manjaro-zsh-prompt ]]; then
source /usr/share/zsh/manjaro-zsh-prompt
fi
Of course my own config is responsible … but ONLY (!!!) when it’s running along with Manjaro’s default zsh configuration. My configuration has worked flawlessly for years with Debian, Ubuntu, and LinuxMint, and I made no changes whatsoever to my own config when installing it on Manjaro. I have no intention of messing with my own working zsh configuration simply to get it to work with Manjaro’s unique, customized zsh configuration.
To be clear: my goal is to modify Manjaro’s zsh config (and ONLY Manjaro’s zsh config!) such that this powerlevel stuff is totally and permanently absent, and so that my own well-working-for-years zsh configuration will start to work properly under Manjaro.
I guess what I’ll do now is to start removing zsh-related packages from my Manjaro OS, and hope that this doesn’t somehow mess up my ability to log in and use the standard shell.
I’ll do that a little later today when I’m back at home, and then I’ll report my findings.
So you’ve kept the default .zshrc and added your config in?
If you replaced it with your own .zshrc, then it’s not using any Manjaro zsh config. AFAIK, it still wouldn’t explain why you’re getting errors about shared libraries (unless you removed them). If you’d posted the errors then we might be able to tell you why you’re getting them.
All I can think of is that your config relies upon powerlevel, and the libraries are missing or named differently. If we had more information to go on then perhaps I could think of something else.
If you didn’t merge your config into Manjaro’s or vice versa then Manjaro’s config isn’t involved at all, it exists but is not being used, therefore modifying it is pointless.
You can try removing manjaro-zsh-config and zsh-theme-powerlevel10k and for completeness ttf-meslo-nerd-font-powerlevel10k.
As I said, I have my own config too, and Manjaro’s config has no part to play because it’s not used in my config. Even if it was used - all the libraries, etc are there as expected so why would it give errors about them?
My .zshrc ONLY runs code from my own set of zsh configuration files. No config merging was done.
And there is ABSOLUTELY NOTHING (!!!) in my own configuration that makes any reference whatsoever to any powerlevel software.
I just now ran the “pacman -R …” command that you recommended above, and now, /usr/bin/zsh got removed from my system.
I guess I’ll have to re-do my ISO-based manjaro installation from the beginning. I don’t have any more time today for all this, so I’ll get back to this within the next few days and see if I can figure out more about what’s going on. And then I’ll report my findings here.
Manjaro itself does not use zsh for any scripts, and it is generally accepted by most UNIX people that while zsh is an interesting interactive shell, at the same time it is not a good choice for use as a scripting language. Among many other reasons, zsh isn’t even POSIX-compatible.
Thank you very much. However, what I’d rather do instead is the following:
(1) Re-install manjaro from scratch. After my current messing with some manjaro confguration, I believe it’s better to start again with a totally clean slate.
(2) After installation, convert all my users’ shells from /usr/bin/zsh to /bin/bash
(3) Totally uninstall zsh and everything else that’s related to zsh.
(4) Get the official source code for zsh, and then build it from scratch and install it. This will ensure that no powerlevel stuff is part of zsh, and that no manjaro-specific zsh changes are present.
(5) Then and only then install all my own zsh configuration files.
That should be /usr/bin/bash, then. /bin is only a symbolic link to /usr/bin anymore, for reasons of backward compatibility, and it may disappear from the filesystem package in the future.
There is no *powerlevel* stuff in the zsh Manjaro ships with, because that’s just the same package as what Arch uses. The *powerlevel* stuff comes from the manjaro-zsh-config package, which pulls it in as a dependency.
I suppose it depends on what you’ve done, but even that seems overkill.
The rest is definitely overkill. Instead of doing all that I’d just review my config. However it’s your time, spend it however you wish.
Again if you post the errors we might be able to help. If you post both the errors and the config, we should definitely be able to figure out what’s going on.
Well, OK, before I go all out and try to reinstall manjaro from scratch, I’ll just simply install zsh again and see where that gets me. If I can then get my zsh configuration stuff to work, then I’ll be done.
And if not, then I’ll perform the full-blown 6-step scenario that I described above.
And yes, if I hit more errors, I’ll post all the error messages and config stuff.
Just keep in mind that if any significant changes in my zsh configuration files would need to be made in order for this to run under manjaro, then I won’t make those changes, and I’ll give up on manjaro.
The reason I would choose to do this is because I use several machines on different linux versions now, and I run all of them with a standard set of configurations in order to easily keep them in sync. Any significant zsh config changes that I might have to make just for manjaro would sabotage my keeping-them-all-in-sync setup.
Anyway, I hope I can get this to work and not need to abandon manjaro.
I’ll be back in a few days, when I have more time to work on this.
By the way, since when is zsh the default shell on manjaro xfce? It wasn’t like that in 2023 as i installed. It was bash and i still use bash. I tried others but i guess i am too used to bash and stayed there.
