Description of problem: When running, the applet prints this message to the journal every 5 seconds: gnome-shell[1815]: /usr/share/gnome-shell/extensions/system-monitor.gmail.com/gpu_usage.sh: line 34: nvidia-set//tings: No such file or directory Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Enable the extension using gnome-tweaks 2. 3. Actual results: Expected results: Additional info: Removing "//" fixes the problem
Hello, Thanks for reporting this issue. It has been already reported upstream and a patch has been proposed as a pull request here: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/pull/544 I'll link this bug report to this pull request, and if in a few days it doesn't get fixed, I'll add the patch to the Fedora package. Please, feel free to make any comment about this issue. Cordially, -- NVieville
FEDORA-2020-8c52e3d8d4 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8c52e3d8d4
FEDORA-2020-4285c80c86 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4285c80c86
FEDORA-EPEL-2020-b9d2e6e9a4 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b9d2e6e9a4
FEDORA-EPEL-2020-37d3b5c1fc has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-37d3b5c1fc
FEDORA-2020-4285c80c86 has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4285c80c86` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4285c80c86 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-37d3b5c1fc has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-37d3b5c1fc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-b9d2e6e9a4 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b9d2e6e9a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1ae7e7c1ff has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-1ae7e7c1ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1ae7e7c1ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-8c52e3d8d4 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8c52e3d8d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8c52e3d8d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1ae7e7c1ff has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-8c52e3d8d4 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4285c80c86 has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-37d3b5c1fc has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-b9d2e6e9a4 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.