fmujakitz
commented
1 year ago Hi, I've noticed you're doing the reads as sudo. Are you able to read the temps as a user?
Closed MichNLGithub closed 1 year ago
fmujakitz
commented
1 year ago Hi, I've noticed you're doing the reads as sudo. Are you able to read the temps as a user?
MichNLGithub
commented
1 year ago Hi, I've noticed you're doing the reads as sudo. Are you able to read the temps as a user?
Hi, yes i can read temps as a user.
fmujakitz
commented
1 year ago Okay... is there anything logged in the journal, related to the extension/gnome-shell?
np422
commented
1 year ago I have the same error and get the following from journalctl /usr/bin/gnome-shell
Jan 06 18:30:12 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:12 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:17 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:17 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:22 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:22 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:27 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:27 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:32 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:32 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:37 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:37 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:42 orville gnome-shell[3542]: JS ERROR: TypeError: row[4].split(...)[1] is undefined
parse@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:249:18
execute@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:64:25
async*update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:267:26
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:59
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 06 18:30:42 orville gnome-shell[3542]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the fai>
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:484:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9$ cat /proc/acpi/ibm/thermal
temperatures: 46 44 49 0 44 44 45
$ cat /proc/acpi/ibm/fan
status: enabled
speed: 2334
level: auto
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 20
On-line CPU(s) list: 0-19
Vendor ID: GenuineIntel
Model name: 12th Gen Intel(R) Core(TM) i7-12800H
CPU family: 6
Model: 154
Thread(s) per core: 2
Core(s) per socket: 14
Socket(s): 1
Stepping: 3
CPU max MHz: 3700.0000
CPU min MHz: 400.0000
BogoMIPS: 5606.40
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xt
opology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave av
x f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req umip pku ospke waitpkg g
fni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr flush_l1d arch_capabilities
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 544 KiB (14 instances)
L1i: 704 KiB (14 instances)
L2: 11.5 MiB (8 instances)
L3: 24 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-19
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Srbds: Not affected
Tsx async abort: Not affected
$ lsblk
AME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 146.9M 1 loop /snap/chromium/2254
loop2 7:2 0 55.6M 1 loop /snap/core18/2632
loop3 7:3 0 55.6M 1 loop /snap/core18/2667
loop4 7:4 0 63.2M 1 loop /snap/core20/1738
loop5 7:5 0 63.3M 1 loop /snap/core20/1778
loop6 7:6 0 55M 1 loop /snap/cups/872
loop7 7:7 0 163.3M 1 loop /snap/firefox/1635
loop8 7:8 0 238.4M 1 loop /snap/firefox/2211
loop9 7:9 0 219M 1 loop /snap/gnome-3-34-1804/77
loop10 7:10 0 400.8M 1 loop /snap/gnome-3-38-2004/112
loop11 7:11 0 346.3M 1 loop /snap/gnome-3-38-2004/119
loop12 7:12 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop13 7:13 0 115.8M 1 loop /snap/slack/68
loop14 7:14 0 45.9M 1 loop /snap/snap-store/582
loop15 7:15 0 45.9M 1 loop /snap/snap-store/638
loop16 7:16 0 49.6M 1 loop /snap/snapd/17883
loop17 7:17 0 304K 1 loop /snap/snapd-desktop-integration/43
loop18 7:18 0 304K 1 loop /snap/snapd-desktop-integration/49
loop19 7:19 0 92.3M 1 loop /snap/whatsapp-for-linux/49
nvme0n1 259:0 0 1.9T 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
└─nvme0n1p2 259:2 0 1.9T 0 part
├─vgubuntu-root 253:0 0 1.8T 0 lvm /var/snap/firefox/common/host-hunspell
│ /
└─vgubuntu-swap_1 253:1 0 1.9G 0 lvm [SWAP]
$ sensors
ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +30.0°C
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +46.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 4: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 8: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 12: +39.0°C (high = +100.0°C, crit = +100.0°C)
Core 16: +41.0°C (high = +100.0°C, crit = +100.0°C)
Core 20: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 24: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 25: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 26: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 27: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 28: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 29: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 30: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 31: +38.0°C (high = +100.0°C, crit = +100.0°C)
BAT0-acpi-0
Adapter: ACPI interface
in0: 17.38 V
ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)
thinkpad-isa-0000
Adapter: ISA adapter
fan1: 1761 RPM
CPU: +44.0°C
GPU: +42.0°C
temp3: +45.0°C
temp4: +0.0°C
temp5: +42.0°C
temp6: +43.0°C
temp7: +43.0°C
temp8: N/A
nvme-pci-0400
Adapter: PCI adapter
Composite: +40.9°C (low = -5.2°C, high = +83.8°C)
(crit = +87.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +44.0°C (crit = +128.0°C)
np422
commented
1 year ago 
np422
commented
1 year ago 
np422
commented
1 year ago Let me know if I can provide any other info that would be useful!
fmujakitz
commented
1 year ago @np422 Thanks! The log was enough, and the fix is already in main. You can build it and test on your own, or wait until it's reviewed and approved on gnome exts. Let me know if it solves the issue
@MichNLGithub ping
edit: It's already available on gnome exts
np422
commented
1 year ago Thank you, now it works!
I had some issues upgrading via the gnome-ext website, but I manually removed it and installed it from source and everything worked fine.
np422
commented
1 year ago I still get some funky messages from the journal.
Jan 08 16:54:05 orville gnome-shell[270523]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 08 16:54:10 orville gnome-shell[270523]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 08 16:54:15 orville gnome-shell[270523]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9
Jan 08 16:54:20 orville gnome-shell[270523]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Indicator/this._update@/home/niklas/.local/share/gnome-shell/extensions/thinkpadthermal@moonlight.drive.vk.gmail.com/extension.js:487:34
setInterval/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:103:9The indicator looks fine though.
np422
commented
1 year ago 
fmujakitz
commented
1 year ago I'll wait for feedback from @MichNLGithub, and close this issue afterwards.
Regarding those warnings, there is an open issue for that, and I'm not really sure how to debug it, as I'm not seeing those warnings...
Are you by any chance running anything that is accessing tpacpi?
np422
commented
1 year ago Not that I know of.
fmujakitz
commented
1 year ago Thinkfan maybe?
np422
commented
1 year ago Nope, no thinkfan.
fmujakitz
commented
1 year ago @np422 If you find time and will, feel free to investigate more. I would be interested in your findings.
@MichNLGithub I'm gonna assume this issue has been resolved on your end and close it.
See screenshot below, in top bar it doesn't show any stats and also no Thermal info, CPU or Fan Control stats.
Log:
linux@pop-os: sudo cat /proc/acpi/ibm/thermal temperatures: 43 0 0 0 0 0 0 0
linux@pop-os: sudo cat /proc/acpi/ibm/fan status: enabled speed: 2585 level: auto
linux@pop-os: lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 36 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz CPU family: 6 Model: 58 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 Stepping: 9 CPU max MHz: 3800.0000 CPU min MHz: 1200.0000 BogoMIPS: 5587.06 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse 36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop _tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadli ne_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd i brs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep er ms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization: VT-x Caches (sum of all):
L1d: 128 KiB (4 instances) L1i: 128 KiB (4 instances) L2: 1 MiB (4 instances) L3: 8 MiB (1 instance) NUMA:
NUMA node(s): 1 NUMA node0 CPU(s): 0-7 Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX disabled L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnera ble Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected Srbds: Vulnerable: No microcode Tsx async abort: Not affected
linux@pop-os: lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 461.8G 0 part / └─sda2 8:2 0 4G 0 part
└─cryptswap 253:0 0 4G 0 crypt [SWAP] sdb 8:16 0 119.2G 0 disk
├─sdb1 8:17 0 8M 0 part
├─sdb2 8:18 0 512B 0 part
├─sdb3 8:19 0 512B 0 part
├─sdb4 8:20 0 512B 0 part
├─sdb5 8:21 0 512B 0 part
├─sdb6 8:22 0 16M 0 part
├─sdb7 8:23 0 16M 0 part
└─sdb8 8:24 0 113.8G 0 part
linux@pop-os:~$ sensors thinkpad-isa-0000 Adapter: ISA adapter fan1: 2585 RPM fan2: 65535 RPM CPU: +44.0°C
GPU: +0.0°C
temp3: +0.0°C
temp4: +0.0°C
temp5: +0.0°C
temp6: +0.0°C
temp7: +0.0°C
temp8: +0.0°C
BAT0-acpi-0 Adapter: ACPI interface in0: 11.78 V
curr1: 0.00 A
coretemp-isa-0000 Adapter: ISA adapter Package id 0: +47.0°C (high = +87.0°C, crit = +105.0°C) Core 0: +44.0°C (high = +87.0°C, crit = +105.0°C) Core 1: +44.0°C (high = +87.0°C, crit = +105.0°C) Core 2: +45.0°C (high = +87.0°C, crit = +105.0°C) Core 3: +45.0°C (high = +87.0°C, crit = +105.0°C)
acpitz-acpi-0 Adapter: ACPI interface temp1: +44.0°C (crit = +100.0°C) temp2: +26.8°C (crit = +99.0°C)