chinf / psensor Goto Github PK

Currently, psensor creates $HOME/.psensor/ to store configuration data and logs. This creates some clutter in $HOME that could be organized nicely.

• Configuration should be under ~/.config/psensor/.
• Cache should be under ~/.cache/psensor/ (e.g. logs).

See:

• http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
• http://ploum.net/207-modify-your-application-to-use-xdg-folders

Could you allow us to set different alarms depending on the range of CPU temperature.

On ubuntu 24.04 red thing appear.

Currently, the scale on the graph view is auto-computed based on the min and max of the sensor temps shown, and the dotted gridlines are unlabeled, but correspond to I think 10C (and 18? F) and 1 minute. I think it would be nice if we could manually specify the range of the y-axis of the graph (possibly with allowing it to expand if a new sensor goes out of the range, if that's easier) similar to how we can specify the range of the x-axis through Monitoring duration. I also think it would be nice to have the dotted gridlines labeled with their corresponding temps/times, because I think it would make it easier to read at a glance.

When changing "Position of sensors table" the graph is frequently lost. User must work out that there is an invisible splitter that must be dragged to display both graph and table.

Suggestion:
Prevent the splitter from being fully left/right/top/bottom so it can always be 'seen',
Or, allow a both or single panel display, selectable through a radio button in preferences, [and reflect this after splitter drags]
Or, probably best, implement a legend inside the regular graph, which would now take up the entire window.

As per
https://gitlab.com/jeanfi/psensor/-/issues/10 "On my laptop (Ubuntu 18.04, 8750H, Geforce 1070), pSensor 1.1.5 reports free memory percentage and used GPU memory percentage. This inconsistency is confusing."

The better measure of memory is, I think, mem.available rather than mem.free.

This can be tested by just changing
https://github.com/chinf/psensor/blob/master/src/lib/pgtop2.c#L98
from
v = ((double)mem.free) * 100.0 / mem.total;
to
v = ((double)mem.available) * 100.0 / mem.total;

And then if it works as expected, perhaps a second memory sensor can be added.

First, THANK YOU for making this! It's been my experience that overtemp and CPU cycle hogging are the biggest cause of failures in computing. Monitoring these has saved me many many hours of lost work.

There seems to be an issue when I set an alarm threshold. For example:

after clicking ok, then re-opening the dialog, on the Alarm tab I now see:

and I didn't change those values.

This only happens if I change the setting of Temperature unit to Fahrenheit. If I go back to Celsius (as god intended) then everything works perfectly.

On the one hand, we can consider this a tax on people who use freedom units. I personally only measure things in Capiberras. ,o) However, it seems wrong to have the /option/ to use 'F and then have that screw up other operations?

I have just installed psensor (apt install psensor) on a fresh Ubuntu installation. Once started, I cannot do anything with the box, unless I ssh to it and kill psensor, as it is in the loop of asking for password for every SSD / HD in the box.

Neither providing password nor clicking Cancel does any good. The time between those requests is just too short to go through the menu and do any changes (if there are such) to disable those devices. After few such cycles, the box locks up with the screen asking for the password.

If there is any solution for it, it should be front and center in the Readme.

Im on fedora 35 attempting to compile psensor. When I run sudo make install I get this:

Making install in doc
make[1]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/doc'
make[2]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/doc/psensor'
 /usr/bin/install -c -m 644 faq.html faq.txt TODO.txt TODO.html '/usr/local/share/doc/psensor'
make[2]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/doc'
make[1]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/doc'
Making install in po
make[1]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/po'
/usr/bin/mkdir -p /usr/local/share
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/psensor.mo
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/psensor.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/psensor.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/psensor.mo
installing hu.gmo as /usr/local/share/locale/hu/LC_MESSAGES/psensor.mo
installing hr.gmo as /usr/local/share/locale/hr/LC_MESSAGES/psensor.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/psensor.mo
installing lv.gmo as /usr/local/share/locale/lv/LC_MESSAGES/psensor.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/psensor.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/psensor.mo
installing pt_BR.gmo as /usr/local/share/locale/pt_BR/LC_MESSAGES/psensor.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/psensor.mo
installing sl.gmo as /usr/local/share/locale/sl/LC_MESSAGES/psensor.mo
installing sr.gmo as /usr/local/share/locale/sr/LC_MESSAGES/psensor.mo
installing sv.gmo as /usr/local/share/locale/sv/LC_MESSAGES/psensor.mo
installing tr.gmo as /usr/local/share/locale/tr/LC_MESSAGES/psensor.mo
installing uk.gmo as /usr/local/share/locale/uk/LC_MESSAGES/psensor.mo
installing zh_CN.gmo as /usr/local/share/locale/zh_CN/LC_MESSAGES/psensor.mo
if test "psensor" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed [email protected] [email protected] insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
		    /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/po'
Making install in src
make[1]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src'
Making install in lib
make[2]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src/lib'
make[3]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src/lib'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src/lib'
make[2]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src/lib'
Making install in glade
make[2]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src/glade'
make[3]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src/glade'
make[3]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/psensor'
 /usr/bin/install -c -m 644 psensor.glade psensor-appindicator.glade sensor-edit.glade psensor-pref.glade '/usr/local/share/psensor'
make[3]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src/glade'
make[2]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src/glade'
Making install in server
make[2]: Entering directory '/home/kevindurb/Downloads/psensor-1.2.0/src/server'
gcc -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../..  -Wall -Werror -DDEFAULT_WWW_DIR=\""/usr/local/share/psensor/www"\" -I../../src -I../../src/lib  -I/usr/include/json-c  -I/usr/include/p11-kit-1  -I/usr/include/libgtop-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread     -g -O2 -MT server.o -MD -MP -MF .deps/server.Tpo -c -o server.o server.c
server.c: In function ‘main’:
server.c:456:42: error: passing argument 5 of ‘MHD_start_daemon’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  456 |                              NULL, NULL, &cbk_http_request, server_data.sensors,
      |                                          ^~~~~~~~~~~~~~~~~
      |                                          |
      |                                          int (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, size_t *, void **) {aka int (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int *, void **)}
In file included from server.c:39:
/usr/include/microhttpd.h:2480:45: note: expected ‘MHD_AccessHandlerCallback’ {aka ‘enum MHD_Result (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int *, void **)’} but argument is of type ‘int (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, size_t *, void **)’ {aka ‘int (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int *, void **)’}
 2480 |                   MHD_AccessHandlerCallback dh, void *dh_cls,
      |                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~
cc1: all warnings being treated as errors
make[2]: *** [Makefile:449: server.o] Error 1
make[2]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src/server'
make[1]: *** [Makefile:619: install-recursive] Error 1
make[1]: Leaving directory '/home/kevindurb/Downloads/psensor-1.2.0/src'
make: *** [Makefile:514: install-recursive] Error 1

This seems to be the error: error: passing argument 5 of ‘MHD_start_daemon’ from incompatible pointer type [-Werror=incompatible-pointer-types]

Currently, I have enabled Alarms for temperatures over 90 degrees in my CPU.

However, when I open a heavy program or extract a zip package, the CPU temperature might spike to 92 degrees and drop immediately.

My suggestion is that the alarm has an option like this:

High Threshold: 90 degrees
Low Threshold: 0 degrees
Alarm after: X seconds off of the threshold

This way I could tell my computer that it should hibernate if the temperatures are over 90 degrees for over 5 minutes - then I can protect my gaming laptop from frying without false alarms.

What should I put in here to make it suspend at a particular temperature? I love psensor btw I've been using it for years now there's nothing else like it on linux and it's even better than core temp on windows in many ways.
I've tried "systemctl suspend" and I've tried entering a path to a shell script to execute this command.

Hi there,

If I reboot the system I can clear the values and history of psensor (like max/min temperatures reached), but this is not always convenient and I am not able to determine how to do this without rebooting the system. is there a file that I need to delete that would clear the psensor data and make it start again so that I can avoid rebooting after an external event (eg: air conditioner maintenance) that allows me to get more accurate reading of max and min values once that external event has passed?

Thanks in advance
Pete

I am using manjaro / archlinux and is using 1.2.1-4 version of psensor. I see the icon not being transparent like other tray icons I am using:

Currently, at least on my installation of Linux Mint 20.3 XFCE, left-clicking the tray icon does the exact same thing as right clicking.

I would think that it would make more sense that left-clicking would simply always "show" the program window while right-click can be used for the pop-up context menu (other programs such as nheko behave in such a manner).

The graphs dont refresh if I interact at all with the window after opening it,
only if I move the mouse over the edge of the graph area.

Ubuntu 22.04
5.15.0-40-generic

An improved icon is available. Can you please use this icon:

http://minhluan.net/site/assets/files/1186/psensor-icon.png

It's annoying to lose keyboard focus to an application that autostarts as part of the desktop background.

Unfortunately the option to show the sensordata next to the icon in the taskbar/menu in Gnome on Clearlinux is not available. Can you please support the option so the icon with sensordata (temp/usage) is visible in the taskbar/menu next tot the power/network/volume section.

I don't know why, but psensor was obtaining bad temperature measures from Kingston SA400S37480G that I can't read in any other place. Seems that the temperature is really readed in ºF and not ºC, because the conversion results in a good value in correct expected range.

# smartctl -A /dev/sda | grep -i temperature; smartctl -A /dev/sdb | grep -i temperature

194 Temperature_Celsius     0x0022   034   052   000    Old_age   Always       -       34 (Min/Max 21/52)
194 Temperature_Celsius     0x0022   033   054   000    Old_age   Always       -       33 (Min/Max 21/54)

# hddtemp /dev/sd[ab]

/dev/sda: KINGSTON SA400S37480G: 34°C
/dev/sdb: KINGSTON SA400S37480G: 33°C

Can I check something to give you better feedback details for solve this issue?

How are RPM GPU fan values retrieved by psensor?

I need a simple way to retrieve it with a command line base utility.
Please can you pointing me out which is the piece of code responsible for obtain these values?
Which is, under the hood, the nvml call toward the GPU driver to get exactly the live RPM values of the fans?

I already try though a simple python3 script using the following API:
py3nvml.nvmlUnitGetFanSpeedInfo

But doesn't work for my RTX 3080 (Driver version 525.85.05). It say:
py3nvml.py3nvml.NVMLError_InvalidArgument: Invalid Argument

uk.zip

https://imgur.com/a/lSYMpD2
There are two application icons in the tray. The first opens a window, the second opens a context menu. Previously, there was only one icon in the tray and I think two icons are a bug KDE 5.21.1 OpenSUSE tumbleweed.

Running sensors in part returns:

`k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +58.2°C
Tdie: +58.2°C

nvme-pci-0100
Adapter: PCI adapter
Composite: +55.9°C (low = -0.1°C, high = +74.8°C)
(crit = +79.8°C)

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: N/A

nvme-pci-2300
Adapter: PCI adapter
Composite: +53.9°C (low = -0.1°C, high = +74.8°C)
(crit = +79.8°C)`

Though none of this information is available in psensors. I imagine because in psensors >preferences>providers | hard disk drive there is no provision to select the appropriate support.

Kubuntu 21.04
Ryzon 5800X
MSI X570 Unity