I’m experiencing a consistent crash with btop on my EndeavourOS installation. The program fails to start with an error before any configuration files can be created.
Error Message
text
ERROR: Exception during Config::unlock() : unordered_map::at
System Information
CPU: AMD Ryzen 5 7530U (6-core, Zen 3+)
GPU: AMD Barcelo integrated graphics (Radeon)
Shell: Nushell (nu)
Terminal: Konsole
bash
$ lspci | grep -i vga
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c5)
Locale Configuration (Verified Working)
Initially had UTF-8 locale errors, but those are now resolved:
bash
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_ALL=en_US.UTF-8
# ... all other LC_* variables set to en_US.UTF-8
What I’ve Tried (None Worked)
Fixed UTF-8 locale issues - Generated locales, set LANG/LC_ALL in shell config
Attempted btop --utf-force - No effect on the crash
Updated btop to latest version from repos
(btop4win works perfectly on Windows 11 on the same hardware with full GPU monitoring)
Packages Installed
bash
$ pacman -Qs btop
local/btop (version here)
bash
$ pacman -Qs rocm
local/btop 1.4.5-1
A monitor of system resources, bpytop ported to C++
Any help would be greatly appreciated!
It seems to be a known bug .
Well, btop worked fine on ubuntu based linux and windows btop4win . I just switched to EndavourOS from Windows, so I thought this is an Endavour specific problem.
Well I don’t know it works without problems on my EOS plasma, but I haven’t got Nushell installed, and I don’t know if the bug can be related to that . Don’t think you could compare Ubuntu with a rolling distro like EOS, which has upstream updates all of the time, and I can see the last update for Btop is about a month ago.
Just tested btop on my system: works without problem here.
MESA-INTEL: warning: Haswell Vulkan support is incomplete
Operating System: EndeavourOS
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.12.55-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4570R CPU @ 2.70GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: Intel® Iris® Pro Graphics 5200
Just launched Btop on my EOS install. Zero issues.
Operating System: EndeavourOS
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060 Ti
EDIT:
There appears to be a bug similar to the OP’s issue that was filed in January and is still being discussed…
opened 01:12PM - 09 Jan 25 UTC
bug
**Read the README.md and search for similar issues before posting a bug report!*… *
Any bug that can be solved by just reading the [prerequisites](https://github.com/aristocratos/btop#prerequisites) section of the README will likely be ignored.
**Describe the bug**
When quickly, repeatedly pressing or holding the `p` key `btop` crashes with the following message:
```
ERROR: Exception during Config::unlock() : unordered_map::at
```
**To Reproduce**
1. open btop
2. hold `p`
3. `btop` crashes after some time
**Expected behavior**
btop should not exit
**Info (please complete the following information):**
- btop++ version: `btop --version`
```
btop version: 1.4.0
Compiled with: g++ (13.3.0)
Configured with: cmake -DBTOP_STATIC=OFF -DBTOP_USE_MOLD=OFF -DBTOP_FORTIFY=ON -DBTOP_GPU=ON
```
- Binary: from release
- Architecture: [x86_64, aarch64, etc.] x86_64
- Platform: Linux
- (Linux) Kernel: 6.12.7
- (OSX/FreeBSD) Os release version: NixOS 24.11
- Terminal used: alacritty
- Font used: JetBrains Mono
**Additional context**
Contents of `~/.config/btop/btop.log`
```bash
2025/01/09 (21:07:45) | ===> btop++ v.1.4.0
2025/01/09 (21:07:45) | WARNING: Intel GPU: Failed to initialize PMU
2025/01/09 (21:08:03) | ERROR: Exception during Config::unlock() : unordered_map::at
```
You mean this topic I guess ?
I didn’t even notice that. I sometimes miss text as a link. I tend to just link the page itself, much easier to see.
Chalk it up to old age and deteriorating vision.
Guess I am a lazy person and don’t want to scroll through a topic with all the links that take up a lot of space in a topic. But I agree it is just a bit of getting used to , because in the beginning I also missed a lot of that hyperlinks. Now I think it is a nice option to use.
1 Like