harlemsquirrel / gnome-shell-extension-sensory-perception Goto Github PK

View Code? Open in Web Editor NEW

This project forked from isdipesh/gnome-shell-extension-sensors

27.0 4.0 11.0 383 KB

Displays CPU/GPU/mobo/disk temperatures, voltages and fan speeds

Home Page: https://extensions.gnome.org/extension/1145/sensory-perception/

License: GNU General Public License v3.0

JavaScript 98.85% Shell 0.99% CSS 0.15%

hacktoberfest gnome-shell-extension

gnome-shell-extension-sensory-perception's Introduction

Sensory Perception

A GNOME Shell Extension

Warning

This extension is not longer maintained. Consider alternatives like https://github.com/corecoding/Vitals

Forked from https://github.com/xtranophilist/gnome-shell-extension-sensors

Requirements

This GNOME shell extension uses lm-sensors which must be installed.

# ArchLinux
sudo pacman -S lm_sensors

# Fedora
sudo dnf install lm_sensors

# Ubuntu
sudo apt install lm-sensors

Compatibility

GNOME version	Earliest extension version
42	v18
41	v15
40	v14
3.36	v12
3.34	v11
3.32	v12

GNOME Shell < 3.32 require v7.

Installation

GNOME Extensions Website

Visit https://extensions.gnome.org/extension/1145/sensory-perception/
Click the switch to install and enable the extension
Accept the prompt to install if not already installed

Manual

This is useful for developing and/or debugging.

As of GNOME 40, the extension system seems to reset the extension on it's own so symlinking can cause local repo to be clobbered.

Build and install on GNOME 40+

bin/build-dist.sh && gnome-extensions install --force dist/[email protected]

Then reload the shell (only works on XOrg) or reboot.

Symlinking (not recommended on GNOME 40+)

# Clone the repository
git clone https://github.com/HarlemSquirrel/gnome-shell-extension-sensory-perception.git
# Or download and unzip a release from https://github.com/HarlemSquirrel/gnome-shell-extension-sensory-perception/tags

# OPTIONAL: check out a specific tag or branch
git checkout v7

# Create a symlink to the local user's extensions directory
ln -s ~/gnome-shell-extension-sensory-perception ~/.local/share/gnome-shell/extensions/[email protected]

# Enable the extension
gnome-shell-extension-tool --enable [email protected]

Customizing labels

You may want to set the labels of your sensors to something like 'CPU' instead of 'temp1'. Every motherboard is different so you will need to set these labels manually. I created lm-sensors-chip-labels where I am adding the files I need for my machines. Feel free to open a PR and contribute!

The sensors.conf manual describes the full array of customizations.

Troubleshooting

Reloading

# This does not always work
gnome-shell-extension-tool -r [email protected]

One of the best ways to troubleshoot is to watch the logs with journalctl and restart the extension. You can reload this extension with the handy Gnome Shell Extension Reloader extension.

journalctl --since="`date '+%Y-%m-%d %H:%M'`" -f | grep sensory-perception

Launch preferences from a terminal

GNOME 40+

gnome-extensions prefs [email protected]

Earlier versions

gnome-shell-extension-prefs [email protected]

Build a zip file for distribution

bin/build-dist.sh

gnome-shell-extension-sensory-perception's People

Contributors

Stargazers

Watchers

Forkers

nickorr0617 queuecumber perlun rffontenelle axelsimon jose1711 zhangn1985 urbalazs rvenson shibingli muharemovic

gnome-shell-extension-sensory-perception's Issues

Gnome 41 support?

This extension was working perfectly with Fedora 34/Gnome 40 but its not supported on Fedora 35/Gnome 41. Hope the dev can take the time to update it :)

The applet ignores all voltage values in mV

Hi,
Thank you for maintaining this applet.
Here is my issue:
First, you can see my sensors output, and then the applet output. It seems that every value in mW is missing from the applet.

Unable to install in Ubuntu 20.04

Describe the bug
Extension is not usable in Ubuntu 20.04.
Fails to update in https://extensions.gnome.org/extension/1145/sensory-perception/

To Reproduce
Steps to reproduce the behavior:

Go to 'https://extensions.gnome.org/extension/1145/sensory-perception/
Click on "On slider "
Select install on dialog
Error shown

Expected behavior
Extension is installed

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Ubuntu
Version 20.04

$ gnome-shell --version
GNOME Shell 3.36.4

It causes sutter video playing in windowed mode.

Describe the bug
If I watch videos in windowed mode, no matter in Firefox or MPV player, the video stutters a lot.

To Reproduce
Steps to reproduce the behavior:

enable this extension
Play videos in windowed mode.
See error

Expected behavior
Don't affect the video playing.

Desktop (please complete the following information):

OS: [Manjaro]

sensory-perception won't load

Describe the bug
State change on user///shell-extension/sensory-perception_HarlemSquirrel.github.io/* from installed to available is not OK
Extension "[email protected]" had error: TypeError: GObject.registerClass() used with invalid base class (is PanelMenuButton)
State change on user///shell-extension/sensory-perception_HarlemSquirrel.github.io/* from available to installed is not OK
sensory-perception_HarlemSquirrel.github.io has error: TypeError: GObject.registerClass() used with invalid base class (is PanelMenuButton)
Reloading completed : Sensory Perception : [email protected]

To Reproduce
Steps to reproduce the behavior:
Used journalctl --since="date '+%Y-%m-%d %H:%M'" -f | grep sensory-perception
and reloaded the extension

Desktop (please complete the following information):

OS: Ubuntu
Version 18.10
Gnome: 3.30.1
Sensory commit: aa0769c

Settings can't be opened

Describe the bug

The settings of extension [email protected] had an error:

GLib.ShellError: Text was empty (or contained only whitespace)

Stack trace:

_getSensorsLabels@/home/vadi/.local/share/gnome-shell/extensions/[email protected]/prefs.js:200:40
_init@/home/vadi/.local/share/gnome-shell/extensions/[email protected]/prefs.js:149:14
buildPrefsWidget@/home/vadi/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

To Reproduce
Install on Ubuntu 20.04 LTS and go to Settings

Expected behavior
Settings opens.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Ubuntu]
Version [e.g. 18.04]

Additional context
Add any other context about the problem here.

Not able to see settings for the extension

I just installed the extension and though of changing couple of things, but the extension popped up with a failure message.

To Reproduce
Steps to reproduce the behavior:

Go to the extension settings from Panel shortcut.

Here is the log:

The settings of extension [email protected] had an error:

GLib.ShellError: Text was empty (or contained only whitespace)

Stack trace:

_getSensorsLabels@/home/xa/.local/share/gnome-shell/extensions/[email protected]/prefs.js:200:40
_init@/home/xa/.local/share/gnome-shell/extensions/[email protected]/prefs.js:149:14
buildPrefsWidget@/home/xa/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

The icon is too big.

Describe the bug
Icon is too big, and the list is out of range of my screen

To Reproduce
Steps to reproduce the behavior:

Click on 'the indicator'

Expected behavior
I can scroll down the menu
Screenshots

Desktop (please complete the following information):

OS: [Manjaro]

Icons/Switches are not properly scaled

Describe the bug
Since Gnome 3.32 icons and switches are way to big. (Please see screenshots.) I'm on latest Arch and I have a 4K screen with 200% scale.

Screenshots

Desktop (please complete the following information):

OS: Arch Linux

setting can't be display

Describe the bug
click settings display an error:can't display setting.

To Reproduce
click settings display an error:can't display setting.

Expected behavior
no

Screenshots

Desktop:

OS: ubuntu
Version : 20.04.1

Additional context

technical details:

The settings of extension [email protected] had an error:

GLib.ShellError: 文本为空(或仅含空白字符)

Stack trace:

_getSensorsLabels@/home/dyllen/.local/share/gnome-shell/extensions/[email protected]/prefs.js:200:40
_init@/home/dyllen/.local/share/gnome-shell/extensions/[email protected]/prefs.js:149:14
buildPrefsWidget@/home/dyllen/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

pc:~$ journalctl --since="`date '+%Y-%m-%d %H:%M'`" -f | grep sensory-perception
10月 11 23:07:06 dyllen-MS-7C02 gnome-shell[2156]: [email protected]: ERROR Future _init: Error: Array element (type filename) may not be null
10月 11 23:07:21 dyllen-MS-7C02 gnome-shell[2156]: [email protected]: ERROR Future _init: Error: Array element (type filename) may not be null
10月 11 23:07:36 dyllen-MS-7C02 gnome-shell[2156]: [email protected]: ERROR Future _init: Error: Array element (type filename) may not be null
10月 11 23:07:51 dyllen-MS-7C02 gnome-shell[2156]: [email protected]: ERROR Future _init: Error: Array element (type filename) may not be null

Gnome Tweak Option error

The settings of extension [email protected] had an error:

GLib.ShellError: Text was empty (or contained only whitespace)

Stack trace:

_getSensorsLabels@/home/afwcxx/.local/share/gnome-shell/extensions/[email protected]/prefs.js:200:40
_init@/home/afwcxx/.local/share/gnome-shell/extensions/[email protected]/prefs.js:149:14
buildPrefsWidget@/home/afwcxx/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Does not work in Fedora 34

But update it no?

The settings of extension [email protected] had an error:

GLib.ShellError: Il testo era vuoto (oppure conteneva unicamente spazi bianchi)

Stack trace:

_getSensorsLabels@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:205:40
_init@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:154:14
buildPrefsWidget@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:286:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:209:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Fedora 34 extension does not work

GLib.ShellError: Il testo era vuoto (oppure conteneva unicamente spazi bianchi)

Stack trace:
_getSensorsLabels@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:205:40
_init@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:154:14
buildPrefsWidget@/home/X555LP/.local/share/gnome-shell/extensions/[email protected]/prefs.js:286:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:209:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Translation in UI not shown

Describe the bug
I am using my computer with german interface. After installing this extension the UI is still in english. The translation file de.po is availible in the extension folder.

To Reproduce
Steps to reproduce the behavior:

You need a system language which is not english, f.e. german
Install this ext.
After relogin or Alt+F2 + r the UI of this ext. is still english

Expected behavior
See this ext. with german interface
Screenshots

Desktop (please complete the following information):

Ubuntu 19.04
Gnome 3.32.1

Does not work on 3.38

Hi!

I add this patch to get it to work. I hope that this helps

$ diff -pbaur /tmp/extension.js extension.js
--- /tmp/extension.js	2020-10-03 07:45:30.948829630 +0200
+++ extension.js	2020-10-03 07:44:26.064459625 +0200
@@ -34,12 +34,15 @@ const SensorsItem = class SensoryPercept
         this._menuItem._label = label;
         this._menuItem._value = value;
 
-        this._menuItem.add(new St.Icon({
+		this._icon = new St.Icon({
             style_class: 'sensory-perception-sensor-icon',
             gicon: Utilities.giconFor('sensors-' + type + '-symbolic')
-        }));
-        this._menuItem.add(new St.Label({ text: label }));
-        this._menuItem.add(new St.Label({ text: value }), { align: St.Align.END });
+		});
+        this._menuItem.add_child(this._icon);
+		this._label = new St.Label({ text: label });
+        this._menuItem.add_child(this._label);
+        this._value = new St.Label({text: value, x_align: St.Align.END});
+        this._menuItem.add_child(this._value);
     }
 
     getPanelString() {

Latest update killed functionality to show sensor data

sensory perception worked fine until installing the latest update two day ago. It still shows SSD temp but no more CPU temp or fan rpm.

lm-sensors is installed and "sensors" output is like this:

~$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.04 V (min = +0.85 V, max = +1.60 V)
+3.3 Voltage: +3.38 V (min = +2.97 V, max = +3.63 V)
+5 Voltage: +5.12 V (min = +4.50 V, max = +5.50 V)
+12 Voltage: +12.16 V (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 1285 RPM (min = 600 RPM, max = 7200 RPM)
CHASSIS FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
POWER FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +37.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +36.0°C (high = +45.0°C, crit = +95.0°C)

sudo journalctl | grep sensory-perception
Okt 31 12:42:59 xxx gnome-shell[1251]: [email protected]: DEBUG Attempting to find sensors in path
Okt 31 12:43:35 xxx gnome-shell-ext[2286]: JS LOG: [email protected]: DEBUG Attempting to find sensors in path
Okt 31 12:44:46 xxx gnome-shell-ext[2354]: JS LOG: [email protected]: DEBUG Attempting to find sensors in path
Okt 31 12:45:36 xxx gnome-shell-ext[2587]: JS LOG: [email protected]: DEBUG Attempting to find sensors in path
Okt 31 12:54:25 xxx gnome-shell-ext[2587]: JS LOG: [email protected]: DEBUG Attempting to find sensors in path

No values for fan speed and voltage

Describe the bug

in settings fan speed an voltage is enabled but section and values are not shown and nothing from:

journalctl --since="date '+%Y-%m-%d %H:%M'" -f | grep sensory-perception

To Reproduce

installed by chome-web-extension

Expected behavior

shown sections and values

Screenshots
see below

Desktop (please complete the following information):

OS: Ubuntu 21.10
Gome-Shell: 40.5
Session: ubuntu-xorg
Version of lm-sensors (or lm_sensors) 3.6.0

Additional context

upower -i /org/freedesktop/UPower/devices/battery_BAT1 
  native-path:          BAT1
  vendor:               SAMSUNG Electronics
  model:                SR Real Battery
  serial:               123456789
  power supply:         yes
  updated:              Mi 22 Dez 2021 13:52:32 CET (89 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               charging
    warning-level:       none
    energy:              20,6176 Wh
    energy-empty:        0 Wh
    energy-full:         29,562 Wh
    energy-full-design:  44,5704 Wh
    energy-rate:         13,6819 W
    voltage:             8,306 V
    time to full:        39,2 minutes
    percentage:          77%
    capacity:            62,9252%
    technology:          lithium-ion
    icon-name:          'battery-full-charging-symbolic'
  History (charge):
    1640177552	77,000	charging
  History (rate):
    1640177552	13,682	charging

acpi -V
Battery 0: Charging, 80%, 00:24:46 until charged
Battery 0: design capacity 5880 mAh, last full capacity 3500 mAh = 59%
Adapter 0: on-line
Thermal 0: ok, 59.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 99.0 degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 97.0 degrees C
Thermal 1: active, 59.0 degrees C
Thermal 1: trip point 0 switches to mode critical at temperature 99.0 degrees C
Thermal 1: trip point 1 switches to mode passive at temperature 97.0 degrees C
Thermal 1: trip point 2 switches to mode active at temperature 71.0 degrees C
Thermal 1: trip point 3 switches to mode active at temperature 55.0 degrees C
Cooling 0: Processor 0 of 3
Cooling 1: Processor 0 of 3
Cooling 2: Fan 0 of 1
Cooling 3: Processor 0 of 3
Cooling 4: Processor 0 of 3
Cooling 5: intel_powerclamp no state information available
Cooling 6: Fan 0 of 1
Cooling 7: x86_pkg_temp no state information available

sensors
BAT1-acpi-0
Adapter: ACPI interface
in0:           8.32 V  
curr1:         1.58 A  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +58.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +58.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +57.0°C  (high = +100.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +59.0°C  (crit = +99.0°C)
temp2:        +59.0°C  (crit = +99.0°C)

Make it compatible with GNOME 44.2

Description

as stated in the title

"This extension is incompatible with your current GNOME version"

Steps to Reproduce

Expected Behavior

System

Make and model:
CPU:
GPU:
OS:
Sensors version:

Sensors Output

Setting are not working

On Ubuntu 18.04.01 LTS I can't open the sensor settings. Just a window with this content pops up:

GLib.ShellError: Text war leer (oder enthielt nur Leerraum)

Stack trace:
SensorsPrefsWidget<._getSensorsLabels@/home/marvin/.local/share/gnome-shell/extensions/[email protected]/prefs.js:164:29
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
SensorsPrefsWidget<._init@/home/marvin/.local/share/gnome-shell/extensions/[email protected]/prefs.js:113:5
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
buildPrefsWidget@/home/marvin/.local/share/gnome-shell/extensions/[email protected]/prefs.js:245:18
_selectExtension@resource:///org/gnome/shell/extensionPrefs/main.js:91:22
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_onCommandLine@resource:///org/gnome/shell/extensionPrefs/main.js:243:17
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
main@resource:///org/gnome/shell/extensionPrefs/main.js:397:5
@

:1:43

Use sensors JSON output

This requires lm-sensors 3.5.0 or newer. But makes parsing the output with JavaScript oh so much easier.

https://github.com/lm-sensors/lm-sensors/blob/1667b850a1ce38151dae17156276f981be6fb557/CHANGES

Latest updates show error and request running as root

Using F28, this extension worked fine until recently. Now it reads "Error" and on click recommends running as root.

Out of date for GNOME 40

Describe the bug
It is disable on GNOME 40 with state "out of date", also the Extensions viewer shows an error containing "TypeError: Gtk.RadioButton is not a constructor" (see full error log below)

To Reproduce
Steps to reproduce the behavior:

Update GNOME to release 40
Sensory Perception won't start
Run gnome-extensions info [email protected]
See "State: OUT OF DATE"
Open Extensions app
Browse the Sensory Perception extension
See error message

Expected behavior
To have Sensory Perception up and running.

Screenshots

Desktop (please complete the following information):

OS: Arch Linux 64-bit
Version: rolling release
Version of lm-sensors (or lm_sensors): 3.6.0

Additional context

Error message displayed in Extensions app:

TypeError: Gtk.RadioButton is not a constructor

Stack trace:
  _init@/home/rafael/.local/share/gnome-shell/extensions/[email protected]/prefs.js:84:33
  buildPrefsWidget@/home/rafael/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
  _init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:209:40
  OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
  run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
  main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
  run@resource:///org/gnome/gjs/modules/script/package.js:206:19
  start@resource:///org/gnome/gjs/modules/script/package.js:190:8
  @/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Output of gnome-extensions info [email protected]:

[email protected]
  Name: Sensory Perception
  Description: Shows CPU temperature, disk temperature, video card temperature, voltage and fan RPM (forked from xtranophilist/gnome-shell-extension-sensors)
  Path: /home/rafael/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/HarlemSquirrel/gnome-shell-extension-sensory-perception
  Version: 13
  State: OUT OF DATE

Settings are not working in GNOME Shell 3.32.1

Describe the bug
When opening the settings, an error is displayed.

To Reproduce
Steps to reproduce the behavior:

Go to https://extensions.gnome.org/local/
Click on 'Configure this extension' button
An error is displayed

Desktop (please complete the following information):

OS: Ubuntu 19.04
GNOME Shell: 3.32.1

Additional context

GLib.ShellError: Text was empty (or contained only whitespace)

Stack trace:
  _getSensorsLabels@/home/provelli/.local/share/gnome-shell/extensions/[email protected]/prefs.js:195:29
  _init@/home/provelli/.local/share/gnome-shell/extensions/[email protected]/prefs.js:143:5
  buildPrefsWidget@/home/provelli/.local/share/gnome-shell/extensions/[email protected]/prefs.js:276:18
  _selectExtension@resource:///org/gnome/shell/extensionPrefs/main.js:75:22
  _onCommandLine@resource:///org/gnome/shell/extensionPrefs/main.js:320:17
  main@resource:///org/gnome/shell/extensionPrefs/main.js:635:5
  @<main>:1:43

Add AUR support.

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Let people install it via AUR.

Describe alternatives you've considered
Support AUR.

Additional context
None.

Preferences fail to open on GNOME 3.36

Describe the bug
Preferences menu does not open.

To Reproduce
Steps to reproduce the behavior:

Click on app icon in top GNOME bar
Click on Settings
Nothing happens

Expected behavior
Preferences window should open.

Additional context

In the logs

Apr 06 22:00:41 lh-ryzen-desktop gnome-shell[1569]: JS ERROR: TypeError: App is null
                                                    _updateDisplay/<@/home/hs/.local/share/gnome-shell/extensions/[email protected]/extension.js:245:33
                                                    activate@resource:///org/gnome/shell/ui/popupMenu.js:191:14
                                                    vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:138:14

Settings Not Working on v7 (Gnome 3.32, gjs 1.56.0)

Sorry, I should have opened a new bug request, so that it doesn't get burried. See #7.

update for gnome 42

currently says outdated

Sensory Perception extension reports the wrong temperature parameter for some SSDs

Recently I rebuilt my computer with a new motherboard and a M.2 format system drive.
Sensory Perception was reporting the drive temperature as 100 ℃
but in CLI hddtemp was showing 33 ℃ and measuring the actual drive with an IR thermometer agrees with 33 ℃.
I have found out why this is.
Looking at S.M.A.R.T. data,there are two temperature attributes:
Attribute ID 194 Temperature which shows 33 ℃
and Attribute ID 231 which is Temperature for HDDs or Life Left for SSDs 100 - equates to a new drive.
So ,in my case Sensory Perception is reporting the Life Left value as Temperature.
This page shows the S.M.A.R.T. data information:https://en.wikipedia.org/wiki/S.M.A.R.T.#Known_ATA_S.M.A.R.T._attributes

The SSD is a KINGSTON SA400M8120G
Motherboard is: Asus Prime B-450M-A
CPU: AMD® Ryzen 5 2600 six-core processor × 12
Desktop: Ubuntu 19.10

No more display with gnome-shell 3.38

No more work in gnome shell 3.38 / Debian 11 Bullseye

No display of temperature

logs are filled with this messages

journalctl -f | grep sensory-perception
oct. 07 22:04:51 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:05:06 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:05:21 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:05:36 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:05:51 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:06:06 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:06:21 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:06:36 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:06:51 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:07:06 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:07:21 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:07:36 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:07:51 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:08:06 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:08:21 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:08:36 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null
oct. 07 22:08:51 debian gnome-shell[7362]: [email protected]: ERROR Future _readStdout: TypeError: meta is null

Sensor no longer visible in panel (always N/A)

I can no longer can see a sensor value in panel. Might've been caused by upgrading to Gnome 3.34.

Something's gone wrong (Not working on Ubuntu 19.04)

Describe the bug
When I click the settings in the menu I get the following error:

`The settings of extension [email protected] had an error:

GLib.ShellError: Text was empty (or contained only whitespace)

Stack trace:

_getSensorsLabels@~/.local/share/gnome-shell/extensions/[email protected]/prefs.js:195:29
_init@~/.local/share/gnome-shell/extensions/[email protected]/prefs.js:143:5
buildPrefsWidget@~/.local/share/gnome-shell/extensions/[email protected]/prefs.js:276:18
_selectExtension@resource:///org/gnome/shell/extensionPrefs/main.js:75:22
_onCommandLine@resource:///org/gnome/shell/extensionPrefs/main.js:320:17
main@resource:///org/gnome/shell/extensionPrefs/main.js:635:5
@<main>:1:43

To Reproduce
Steps to reproduce the behavior:

Go to the menu
Click on settings
See error

Expected behavior
To open the settings panel

Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Version 19.04

Click settings
Error displayed

Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Version 20.04

Additional context
trace:
The settings of extension [email protected] had an error:

GLib.ShellError: Il testo era vuoto (oppure conteneva unicamente spazi bianchi)

Stack trace:

_getSensorsLabels@/home/franco/.local/share/gnome-shell/extensions/[email protected]/prefs.js:200:40
_init@/home/franco/.local/share/gnome-shell/extensions/[email protected]/prefs.js:149:14
buildPrefsWidget@/home/franco/.local/share/gnome-shell/extensions/[email protected]/prefs.js:281:20
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Displayed names are useless

I'm running Ubuntu 21.10, and the names displays on the extension are completely useless. Here is the output of 'sensors':

nvme-pci-0800
Adapter: PCI adapter
Composite:    +33.9°C  (low  =  -5.2°C, high = +83.8°C)
                       (crit = +87.8°C)

amdgpu-pci-0900
Adapter: PCI adapter
vddgfx:        1.34 V  
vddnb:       999.00 mV 
edge:         +35.0°C  
power1:        4.00 mW 

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

And here is what the drop-down shows:

So, a few things wrong here:

'sensors' doesn't show the SSD drive, so where does that come from?
Using "Composite" for the NVME drives is dumb. What does that even mean, and why would you pick that string instead of "nvme-pci-0800"?
The extension gets the two "Composite" entries confused. Sometimes when I tell it to display the temp of one "Composite", it actually displays the temp of the other one.

What we need are three things:

The extension needs to use something other than the name to distinguish among different sensors, since the name could be duplicated.
It also needs to allow me to specify my own name for a given sensor, and not use whatever name 'sensors' spits out.
Frankly, the average of all temperatures is a pointless value to display.

can't disable wrong items values

I've a wrong lecture from my SSD, should be an option to disable some measures

Replace po translation files with mo files

Remove po folder
https://gjs.guide/extensions/review-guidelines/review-guidelines.html#don-t-include-unnecessary-files

Add locale folder with .mo files instead of po files.

harlemsquirrel / gnome-shell-extension-sensory-perception Goto Github PK

gnome-shell-extension-sensory-perception's Introduction

Sensory Perception

A GNOME Shell Extension

Requirements

Compatibility

Installation

GNOME Extensions Website

Manual

Build and install on GNOME 40+

Symlinking (not recommended on GNOME 40+)

Customizing labels

Troubleshooting

Reloading

Launch preferences from a terminal

Build a zip file for distribution

gnome-shell-extension-sensory-perception's People

Contributors

Stargazers

Watchers

Forkers

gnome-shell-extension-sensory-perception's Issues

Expected behavior See this ext. with german interface Screenshots

Description

Steps to Reproduce

Expected Behavior

System

Sensors Output

Recommend Projects

Recommend Topics

Recommend Org

Expected behavior
See this ext. with german interface
Screenshots