Once the bug is fixed you can revert the changes by deleting the copied file using the following command: rm ~/.config/autostart/sktop Save the changes in the file by pressing Ctrl+ O and Enter. Look for the line X-GNOME-Autostart-enabled=true and change true to false. The last command will open the file sktop in the text editor nano. Sudo chown $USER:$USER ~/.config/autostart/sktop If you don't want to use the Startup Applications app, you can achieve the same goal with the following commands: sudo cp /etc/xdg/autostart/sktop ~/.config/autostart/
This will return the HP icon in the system tray. Once the bug is fixed open this app and check this box. While the bug gets fixed you may want to disable the hplip-systray using the Startup Application app.Īs you see above, I have unchecked the box next to HP System Tray Service. If for some reason you don't want to use the older version of the app, then read on. When the bug is fixed and a newer version of gnome-shell-extension-appindicator is released, or if you want to undo the changes by this workaround, open the terminal again, and use the following command: sudo apt-mark unhold gnome-shell-extension-appindicator The second command makes sure the app is not updated to the newer version during the next update. The first command installs the older, working version of the app gnome-shell-extension-appindicator. Sudo apt-mark hold gnome-shell-extension-appindicator
#Smartram in the system tray install#
Open a terminal by pressing Ctrl+ Alt+ T and enter the following commands: sudo apt install gnome-shell-extension-appindicator=33-1 Workaround 1: Go Back to the Previous Version Or add yourself as "This bug affects you" to an existing bug report.
Please file a bug report from the Ubuntu terminal: ubuntu-bug gnome-shell-extension-appindicator It seems to happens when gnome-shell-extension-appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1. The version 33.1-0ubuntu0.20.04.2 of gnome-shell-extension-appindicator released for Ubuntu 20.04 does not have this problem! Original answer follows: It is a bug
0 kommentar(er)
