Your message dated Sun, 28 Apr 2024 18:13:02 -0700 with message-id <caczd_tbmfh8xj_379m+pkxywrhw-frugd+ekg7njtp-tyce...@mail.gmail.com> and subject line Re: conky-std: please implement an alternative way to distinguish among hwmon devices has caused the Debian Bug report #684425, regarding conky-std: please implement an alternative way to distinguish among hwmon devices to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 684425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: conky-std Version: 1.9.0-2 Severity: wishlist Hello, thanks for maintaining conky in Debian! I have a problem with the hwmon object. One line in my ~/.conkyrc reads: ${color green}CPU Temp.:$color ${hwmon 0 temp 1 1 273} K${color green} - MB Temp.:$color ${hwmon 0 temp 2 1 273} K${color green} - CPU Fan:$color ${hwmon 0 fan 1 0.10472 0} rad/s Please note that, if you need to review the rest of my ~/.conkyrc, it's documented on my website: http://www.inventati.org/frx/ Here, to be more precise: http://www.inventati.org/frx/doc/nanodocs/testing_workstation_desktopconf.html#system-monitor Well, unfortunately there are two hwmon devices on my system: $ tree /sys/class/hwmon/hwmon?/ /sys/class/hwmon/hwmon0/ ├── device -> ../../../coretemp.0 ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── subsystem -> ../../../../../class/hwmon └── uevent /sys/class/hwmon/hwmon1/ ├── device -> ../../../ATK0110:00 ├── fan1_input ├── fan1_label ├── fan1_max ├── fan1_min ├── fan2_input ├── fan2_label ├── fan2_max ├── fan2_min ├── fan3_input ├── fan3_label ├── fan3_max ├── fan3_min ├── in0_input ├── in0_label ├── in0_max ├── in0_min ├── in1_input ├── in1_label ├── in1_max ├── in1_min ├── in2_input ├── in2_label ├── in2_max ├── in2_min ├── in3_input ├── in3_label ├── in3_max ├── in3_min ├── name ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── subsystem -> ../../../../../../../../class/hwmon ├── temp1_crit ├── temp1_input ├── temp1_label ├── temp1_max ├── temp2_crit ├── temp2_input ├── temp2_label ├── temp2_max └── uevent 6 directories, 57 files The problem is that, on each reboot, they may be assigned to hwmon0 and hwmon1 or the other way around, unpredictably. So, in some cases my conky configuration works fine with ${hwmon 0 ...}, while in the other cases it should instead have ${hwmon 1 ...}! When the configuration is wrong, conky spits errors at startup, such as: Conky: can't open '/sys/class/hwmon/hwmon0/temp1_input': No such file or directory please check your device or remove this var from Conky I searched the web and found that I am not the only one who has this same problem with conky. Unfortunately, I have found no real solution. Among the suggestions that can be found in the wild, I've seen people who modify their ~/.conkyrc on the fly with sed (frankly speaking, an ugly hack), people who blacklisted some kernel modules in order to have only one hwmon device (I don't consider this to be an acceptable solution), and so forth... I think the real solution should be found (or implemented) within the conky configuration syntax, but I failed to find a suitable strategy based upon the existing settings and objects. I suggest that the solution is implemented *in* conky. My idea is that conky should read the available /sys/class/hwmon/hwmon?/ directories at startup and look at their /sys/class/hwmon/hwmon?/device symlinks. These symlinks point to ../../../NAME : the mapping between hwmon device numbers and those names should be stored in memory by conky. After that, conky should allow the syntax ${hwmon NAME ...} and automatically find the corresponding hwmon device number, by using the previously built mapping. This way, I could write ${hwmon ATK0110:00 ...} in my ~/.conkyrc and forget about the device number. I hope this can be implemented: please forward this bug report upstream. Thanks for your time! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages conky-std depends on: ii libaudclient2 3.2.3-1 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libcurl3-gnutls 7.26.0-1 ii libdbus-glib-1-2 0.100-1 ii libglib2.0-0 2.32.3-1 ii libimlib2 1.4.5-1 ii libiw30 30~pre9-8 ii liblua5.1-0 5.1.5-2 ii libncurses5 5.9-10 ii libtinfo5 5.9-10 ii libx11-6 2:1.5.0-1 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxft2 2.3.1-1 ii libxml2 2.8.0+dfsg1-5 ii libxmmsclient6 0.8+dfsg-4 conky-std recommends no packages. Versions of packages conky-std suggests: pn apcupsd <none> ii audacious 3.2.3-1 pn moc <none> pn mpd <none> pn xmms2 <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.11.6-1 Closing since upstream has implemented this [1], as mentioned earlier by Jmkr. [1] https://github.com/brndnmtthws/conky/commit/14e3b80c45254743e962f88d
--- End Message ---
