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

macOS No Sensors Found #371

Closed
Walther opened this issue Dec 21, 2020 · 7 comments
Closed

macOS No Sensors Found #371

Walther opened this issue Dec 21, 2020 · 7 comments
Labels
bug Something isn't working the way that is expected.

Comments

@Walther
Copy link

Walther commented Dec 21, 2020

Describe the bug

on macOS, btm reports No Sensors Found in the temperature block.

To reproduce

  1. Run btm on macOS
  2. Observe the No Sensors Found message

bottom version

bottom 0.5.5

bottom config file (if used)

no config file

Installation method

homebrew

brew info bottom
clementtsang/bottom/bottom: stable 0.5.5
A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.
https://github.com/ClementTsang/bottom
/usr/local/Cellar/bottom/0.5.5 (5 files, 3.4MB) *
  Built from source on 2020-12-16 at 23:09:06
From: https://github.com/clementtsang/homebrew-bottom/blob/HEAD/bottom.rb
==> Caveats
zsh completions have been installed to:
  /usr/local/share/zsh/site-functions

Platform and environment information

Operating system, OS version, and architecture

macOS Big Sur 11.1 (20C69)

Terminal (i.e. urxvt, kitty, etc.)

alacritty

Shell (i.e. zsh, bash, etc.)

zsh

Miscellaneous system info

macbook pro 15" 2018, 6-core i7, radeon 560X, 16GB ddr4, 512GB ssd

Rust version

Additional context

@Walther Walther added the bug Something isn't working the way that is expected. label Dec 21, 2020
@ClementTsang
Copy link
Owner

ClementTsang commented Dec 21, 2020

@Walther Could you please try to update to 0.5.6 and let me know if that resolves it? This should have a fix for the issue.

@ClementTsang
Copy link
Owner

Closing for now, this should already be resolved. Feel free to reopen if not.

@not-ivy
Copy link

not-ivy commented Jan 2, 2021

issue still appears on version 0.5.6.
running both natively(arm64) and under Rosetta 2 can reproduce this issue

brew version

clementtsang/bottom/bottom: stable 0.5.6
A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.
https://github.com/ClementTsang/bottom
/usr/local/Cellar/bottom/0.5.6 (5 files, 3.4MB) *
  Built from source on 2021-01-02 at 10:44:01
From: https://github.com/clementtsang/homebrew-bottom/blob/HEAD/bottom.rb
==> Caveats
zsh completions have been installed to:
  /usr/local/share/zsh/site-functions

System info

[email protected] 
-------------------------- 
OS: macOS Big Sur 11.0.1 20B29 x86_64 
Host: MacBookPro17,1 
Kernel: 20.1.0 
Shell: zsh 5.8 
Terminal: kitty 
CPU: VirtualApple (8) @ 2.50GHz processor 
GPU: Apple M1 

@ClementTsang
Copy link
Owner

ClementTsang commented Jan 2, 2021

@sourTaste000 Not sure if that's an issue with the M1 processor in tandem with the libraries I work with... it works fine for me on a Catalina Hackintosh, and correctly shows the CPU temps.

I also don't own an M1 Mac or anything running Big Sur, unfortunately, so I can't really test it here...

If possible, could you:

  1. Go to https://github.com/GuillaumeGomez/sysinfo and clone the repo.
  2. cd into the repo go to examples, then run cargo run (if you don't have cargo installed, you can do so here).
  3. Type "temperature" in the program that runs and tell me the output?

That might help me determine if it's an issue with the library or my program. If you can't, that's also fine, but it'll certainly help me troubleshoot this problem.

Thanks!

@ClementTsang ClementTsang reopened this Jan 2, 2021
@not-ivy
Copy link

not-ivy commented Jan 2, 2021

it did not return anything.

@ClementTsang
Copy link
Owner

Yeah... if that's the case then it's an upstream issue with sysinfo, and I can't really do much.

I'm guessing the library just doesn't support M1 and/or Big Sur yet? Unfortunately if that's the case then I'll also have to mark the current support for bottom on it to be incomplete as well.

@ClementTsang
Copy link
Owner

ClementTsang commented Jan 2, 2021

This really does seem to be more of an M1-specific issue, and macOS ARM is something I currently don't officially support. As such, I'm going to close this issue for now and open a new one specifically in regards to M1 support, but I don't expect to be able to do much on it for a while.

New issue: #382

If anyone else also has this problem on an x86 system, then feel free to re-open (or just file a new bug report).

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

No branches or pull requests

3 participants