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]: Conky picks up on "ERROR: Can't get value of subfeature temp3_max: I/O error" from sensors module #1596

Open
Besensacus opened this issue Jul 21, 2023 · 1 comment
Labels
bug Bug report or bug fix PR priority: low A low priority issue or PR text Issue or PR related to `conky.text` variables triage Issue that hasn't been verified

Comments

@Besensacus
Copy link

What happened?

Conky gets data from sensors command.

${color8}CPU Temp:${color8}${font} ${font :size=10}${alignr}${exec sensors | grep Tctl | cut -c 16-22}${voffset 5}
${color8}Fan RPM:${color8}${exec sensors | grep fan1 | cut -c 14-17}

When I run the sensors command there are two errors present due to an nvme drive.

nvme-pci-0100
Adapter: PCI adapter
Composite: +43.9°C (low = -20.1°C, high = +83.8°C)
(crit = +88.8°C)
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
Sensor 2: +57.9°C (low = +0.0°C, high = +0.0°C)

These kind of errors have been around for a long time in sensors output and I can't find any way to fix sensors module.
It seems this temp3 is advertised by the drive but no value is provided.

My issue right now is that Conky is picking up these errors and generate events in syslog every few seconds if I use any of the code lines which pulls data from sensors.

cip@pop-os:~$ tail /var/log/syslog
Jul 21 19:05:57 pop-os conky.desktop[965321]: ERROR: Can't get value of subfeature temp3_max: I/O error
Jul 21 19:05:57 pop-os conky.desktop[965332]: ERROR: Can't get value of subfeature temp3_max: I/O error
Jul 21 19:05:58 pop-os conky.desktop[965337]: ERROR: Can't get value of subfeature temp3_min: I/O error
Jul 21 19:05:58 pop-os conky.desktop[965349]: ERROR: Can't get value of subfeature temp3_min: I/O error
Jul 21 19:05:58 pop-os conky.desktop[965337]: ERROR: Can't get value of subfeature temp3_max: I/O error
Jul 21 19:05:58 pop-os conky.desktop[965349]: ERROR: Can't get value of subfeature temp3_max: I/O error
Jul 21 19:05:59 pop-os conky.desktop[965359]: ERROR: Can't get value of subfeature temp3_min: I/O error
Jul 21 19:05:59 pop-os conky.desktop[965371]: ERROR: Can't get value of subfeature temp3_min: I/O error
Jul 21 19:05:59 pop-os conky.desktop[965359]: ERROR: Can't get value of subfeature temp3_max: I/O error
Jul 21 19:05:59 pop-os conky.desktop[965371]: ERROR: Can't get value of subfeature temp3_max: I/O error

cip@pop-os:~$ conky
conky: desktop window (400010) is subwindow of root window (6c4)
conky: window type - normal
conky: drawing to created window (0xa400002)
conky: drawing to double buffer
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
^Cconky: received SIGHUP, SIGINT, or SIGTERM to terminate. bye!

Is there any way to stop Conky from generating these events ?
It is filling up my syslog.

Version

1.19.2

Which OS/distro are you seeing the problem on?

Ubuntu

Conky config

No response

Stack trace

No response

Relevant log output

No response

@Besensacus Besensacus added bug Bug report or bug fix PR triage Issue that hasn't been verified labels Jul 21, 2023
@Besensacus
Copy link
Author

Besensacus commented Jul 22, 2023

#921
Found some info in this post.
Based on this post, conky can run in quite mode and it will not generate logs.
Command conky -q
I have tried to add quiet = true in conkyrc file but it did not helped.
What worked was to add -q in the startup application command.

image

@Caellian Caellian added priority: low A low priority issue or PR text Issue or PR related to `conky.text` variables labels Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report or bug fix PR priority: low A low priority issue or PR text Issue or PR related to `conky.text` variables triage Issue that hasn't been verified
Projects
None yet
Development

No branches or pull requests

2 participants