Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Btop v1.4.0 changed how the CPU cores render from 1 column to 2 column #1006

Open
NuwenPham5420 opened this issue Jan 5, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@NuwenPham5420
Copy link

Bug Report: Change in CPU Core Display in Btop v1.4.0
(This is a BUG in 1.4.0 but after looking at the logs may have been introduced as far back as 1.3.2 - as I recall, I was excited to get 1.4 in the hopes that the bug had been fixed.)

Summary: In Btop v1.4.0, the display of individual CPU cores has changed from a single column to two columns. Previously, when the vertical screen height was large enough, the individual cores (e.g., C0, C31) were displayed in a single column, making it easier to read the details of each core. This also allowed more space for the aggregate CPU graph, which was placed next to the core display, providing a longer view of CPU usage history. However, this behavior seems to have been altered in v1.4.0.

Expected Behavior: Please restore the previous behavior where individual CPU cores are shown in a single column when the vertical screen height allows for it. This would improve readability and ensure better utilization of available screen space, particularly for the aggregate CPU graph next to the core display.

Steps to Reproduce:

Upgrade to Btop v1.4.0.
Run the application and observe the CPU core display.
Notice that the cores are now shown in two columns instead of one in high core count processors.
Additional Information: This change makes it harder to read the individual cores, and reduces the space available for the aggregate CPU usage graph, which was previously shown more clearly.

Thank you for considering this issue for a future release.

OS: Fedora Linux 41 (KDE Plasma) x86_64
Kernel: Linux 6.12.7-200.fc41.x86_64
DE: KDE Plasma 6.2.5
WM: KWin (Wayland)
CPU: Intel(R) Core(TM) i9-14900K (32) @ 6.00 GHz
GPU 1: NVIDIA GeForce RTX 4090 [Discrete]
GPU 2: Intel UHD Graphics 770 @ 1.65 GHz [Integrated]
Display (LG HDR 4K): 3840x2160 @ 60 Hz in 43" [External] *
Display (Sceptre C35): 3440x1440 @ 60 Hz in 35" [External]
Display (DELL ST2420L): 1920x1080 @ 60 Hz in 24" [External]
Memory: 6.19 GiB / 62.52 GiB (10%)
Swap: 0 B / 8.00 GiB (0%)
Disk (/): 141.21 GiB / 1.82 TiB (8%) - btrfs
Shell: bash 5.2.32
Terminal: konsole 24.12.0
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK3/4]
Locale: en_US.UTF-8
Bios (UEFI): 9036 (90.36)
Version: fastfetch 2.33.0 (x86_64)

btop --version (installed from Fedora RPM's with dnf install)
btop version: 1.4.0
Compiled with: g++ (14.2.1)
Configured with: /usr/bin/make STATIC= FORTIFY_SOURCE=true GPU_SUPPORT=true RSMI_STATIC=

btop.log file unique entries

8953 │ 2024/11/03 (16:19:51) | ERROR: Couldn't determine terminal size of "STDOUT_FILENO"!
8954 │ 2024/11/03 (16:19:52) | ERROR: Couldn't determine terminal size of "STDOUT_FILENO"!
8955 │

8959 │ 2024/11/03 (16:31:32) | ===> btop++ v.1.3.2
8960 │ 2024/11/03 (16:31:32) | WARNING: Invalid box name in config value presets!
8961 │ 2024/11/03 (16:34:13) | WARNING: Invalid box name in config value presets!

8963 │ 2024/11/03 (16:39:37) | ===> btop++ v.1.3.2
8964 │ 2024/11/03 (16:39:37) | WARNING: Invalid box name in config value presets!
8965 │ 2024/11/03 (16:39:50) | ERROR: Exception during Config::unlock() : unordered_map::at

8967 │ 2024/11/03 (16:46:19) | ===> btop++ v.1.3.2
8968 │ 2024/11/03 (16:46:19) | WARNING: Invalid box name in config value presets!

9021 │ 2024/12/10 (06:34:01) | ===> btop++ v.1.3.2
9022 │ 2024/12/10 (06:34:01) | ERROR: Stall in Runner thread, restarting!
9023 │
9024 │ 2024/12/17 (06:00:02) | ===> btop++ v.1.4.0
9025 │ 2024/12/17 (06:00:02) | WARNING: Intel GPU: Failed to initialize PMU

image

btop_Screenshot_20250105-114714

@NuwenPham5420 NuwenPham5420 added the bug Something isn't working label Jan 5, 2025
@Jamim
Copy link

Jamim commented Jan 15, 2025

This issue looks like a duplicate of #999.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants