-
-
Notifications
You must be signed in to change notification settings - Fork 604
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] time shown differs from system #626
Comments
@tan-wei-xin-alez This should be dependent on which timezone your terminal thinks you're in, btop can change your locale if your native locale doesn't have a UTF-8 version generated, but that wouldn't change your current time zone. |
@aristocratos That was actually one of the first things I checked Do my locale settings matter?
|
Oh I just realized
|
@tan-wei-xin-alez But you could try running |
cool, so I got it to use my timezone by running Might even be worthwhile to add it as something that can be set in menu → general as well as configurable in btop.conf like below
|
I'm fairly certain this is an issue related to configuration on your system. Considering this is the first report I've ever gotten of this particular problem. My timezone (also CEST) gets picked up without problem, the |
ok, I figured out exactly why, it's because I used
and I'm guessing, the Sorry for bothering and thanks for the help @aristocratos ! |
Good find!
No problem :) |
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 section of the README will likely be ignored.
Describe the bug
As mentioned here, for some reason, the time
btop
is showing differs from my system timeTo Reproduce
Simply run
btop
after installing it and make sure menu → general → Clock format is set to%X
Expected behavior
Time shown by
btop
and system time should be the sameScreenshots
Info (please complete the following information):
Additional context
contents of
~/.config/btop/btop.log
(try running btop with
--debug
flag if btop.log is empty)GDB Backtrace
If btop++ is crashing at start the following steps could be helpful:
(Extra helpful if compiled with
make OPTFLAGS="-O0 -g"
)run (linux):
gdb btop
(macos):lldb btop
r
to run, wait for crash and press enter if prompted, CTRL+L to clear screen if needed.(gdb):
thread apply all bt
(lldb):bt all
to get backtrace for all threadsCopy and paste the backtrace here: N/A
The text was updated successfully, but these errors were encountered: