actionschnitzel/pigro-aid-

With a clear and graphically appealing GUI you can access the system deeply, overclock the Pi or replace the entire desktop environment. Everything you need to use the Pi as a desktop computer. PiGro does many commands that have to be entered via the terminal with one or two clicks of a button.

🍱 All Settings In One Place!

✔️ System Monitoring ✔️ System Configuration ✔️ Autostarts ✔️ Process Monitor & Killer ✔️ Update & Upgrade GUI ✔️Multi Install GUI ✔️ Change & Customize DE ✔️ Overclocking ✔️ Link Collection

PiGro - Just Click it! brings the normal desktop functionalities back to Pixel!

PiGro - Just Click it! is an all-inclusive graphical user interface (GUI) software that streamlines the process of managing all your Raspberry Pi settings from one convenient location. With PiGro, you can easily keep your software up-to-date, oversee the APT installer, Pi-Apps App Store, and Flatpak, configure autostarts, overclock your Pi, monitor the system's performance, back up your applications, install desktop environments, and customize your OS theme.

Designed with user-friendliness in mind, PiGro is easily accessible to users of all levels of expertise. Its intuitive interface and straightforward controls make it effortless to access and modify any settings you require.

Special thanks to the entire Pi-Apps-Team

Users on Pi-Apps

Since Version 23.04

---

Reviews

Blog by https://jhmulder.nl: "Swiss Knife For The Pi."

---

💾 Installation

App Center:

As DEBIAN Package:

Download latest.

If you have already installed Pigro via the script, remove: ~/-PiGro-Aid- and ~/.local/Share/Applications/Pigro.Desktop. Then Install the Debian Package.

---

Supported Systems:

Raspberry Pi 4 & 5 :

• Raspberry Pi OS (Bullseye/Bookworm): fully supported
• Ubuntu: fully supported
• Ubuntu MATE: fully supported
• Rhino Linux: fully supported (Scroll to Important)(Ricing via xfce-setting)
• MX Linux: fully supported

Desktops:

• XFCE4: fully supported
• Gnome: fully supported
• Mate: fully supported
• pi-lxde-wayland: fully supported

❗ Installation Process & Updates

• If you have installed PiGro via Pi-Apps, you will automatically receive an update notification.
• If you have installed PiGro via Package you can check for updates in the About TAB.

---

❗ Important

• If PiGro does not start after switching from Wayland to X11
• Buster is NOT supported anymore!
• XWayland Window Decorations wouldn't work when you change the Pixel Theme or Icon Theme [PiXnoir is an exception].
• Overclocking at your own risk.

---

🍔 Latest Changes

Changelog

---

🍩 Showcase

---

💕 You want support me?

PiGro is completely free. I put up to three hours into improvements and updates every day. Not to forget the countless hours I spend reading manuals and reference books. If you like my work, you can support me

pigro-aid-'s Issues

Pigro fails to start on Raspberry Pi 5 using "x" instead of wayland.

There is a bug in the Raspberry Pi 5 config that prevents "RealVnc" from starting (uses a Wayland based VNC?) unless you switch from Wayland to "X". When I did that, it made something incompatible with the PiGro config. Gui start does nothing and from the command line I see this error:

pi@MyPi5-01:~ $ pigro-jci
[Info] You are using PiGro 24.02
[Info] /home/pi/.config/autostart/ already exists
Traceback (most recent call last):
File "/opt/PiGro-JCI/src/main.py", line 7, in
from resorcess import *
File "/opt/PiGro-JCI/src/resorcess.py", line 179, in
theme = get_theme().lower()
^^^^^^^^^^^
File "/opt/PiGro-JCI/src/resorcess.py", line 158, in get_theme
theme = get_lxde_theme_name()
^^^^^^^^^^^^^^^^^^^^^
File "/opt/PiGro-JCI/src/resorcess.py", line 124, in get_lxde_theme_name
with open(config_file_path, "r") as file:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/.config/lxsession/LXDE-pi/desktop.conf'

Ethernet IP address not shown when using NetworkManager

This may already be fixed in PiGro 24, but I just wanted to mention that in PiOS Bullseye, if you use raspi-config to switch to NetworkManager, no IP address is displayed on the PiGro dashboard.

23.04: Known Problems On PiOS Bookworm

• Resize Lock is not working
• Frame sizes are not matching
• Dashboard > System: None
  x Some folder related buttons wouldn't open | Was fixed be thr Pi Devs
• Look & Feel > PIXEL Tweaks is locked due to DE is not recognized

Please be patient. Actually PiGo 24.0 was already completely thought out, but the new PiOS has messed up some things.

PiGro startet nicht

Guten Abend,

ich bekomme PiGro auf Raspberry OS / Bookworm einfach nicht gestartet. Wenn ich es über den Desktop Link starte, passiert gar nichts. Wenn ich es im Terminal ausführe, bekomme ich folgende Meldung:

[Info] You are using PiGro 24.01
[Info] /home/pi/.config/autostart/ already exists
[Info] 2438 .deb Packages Installed
[Info] Snap is installed, and there are 12 packages installed.
[Info] Flatpak is installed. List will be added
Added Flatpak cache.
[Info] Pi-Apps is installed. List will be added
[Info] Raspberry Pi Model: Raspberry Pi 4 Model B Rev 1.5
Traceback (most recent call last):
File "/opt/PiGro-JCI/src/main.py", line 273, in
app = MainApplication()
^^^^^^^^^^^^^^^^^
File "/opt/PiGro-JCI/src/main.py", line 146, in init
self.dash_tab = DashTab(self.notebook)
^^^^^^^^^^^^^^^^^^^^^^
File "/opt/PiGro-JCI/src/tabs/dash_tab.py", line 461, in init
self.update_labels()
File "/opt/PiGro-JCI/src/tabs/dash_tab.py", line 556, in update_labels
f"{get_window_manager_name()}",
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/PiGro-JCI/src/tabs/dash_tab.py", line 535, in get_window_manager_name
result = subprocess.run(
^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/subprocess.py", line 548, in run
with Popen(*popenargs, **kwargs) as process:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/subprocess.py", line 1024, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.11/subprocess.py", line 1901, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'wmctrl'

Ich habe es überprüft, wmctrl ist installiert. Wieso kann der Pfad nicht gefunden werden?
Wie kann ich das beheben?
Vielen Dank im Voraus!

To Do List 25.01

• apt-mark showmanual
• subcommand instead of os.popen
• Full use of ttk plus yaru-theme
• x86_64 Support
• aarch64 non Pi Support

Test

/polls Option1 'Option 2' "Option 3"

Widevine info outdated

I'm pretty sure 64-bit Bullseye and Bookworm have had a 64-bit compatible version of libwidevinecdm0 out for a while now. (citation needed)
Your Tuning tab still says that the 32-bit Chromium is necessary for DRM support, which has been true, but it no longer is.

Please do not take my word for it; I avoid using DRM but this is my current understanding of the situation: that widevine now works for 64-bit Chromium.

Test

/polls Option1 'Option 2' "Option 3"

Automatically replace with the following markdown =>

Version 24.0 Progress

Testing

• Coding Phase
• Start Test Phase
• Review Feedback
• RC1 State
• Fine Tuning
• Release Jan' 24

1st Test Feedback

• Remove PiGro.desktop file
• Check Update && Upgrade does not all upgrades [Not reproduceble yet]
• Check Raspi-Config CLI in SYSTEM
• Check Papirus not working [ Tool will be improved]
• Check set Theme, Icons, Cursor [ PiOS is not able to be riced]
• Check folder not opening
• Chack Tuning States not displayed
  Fixed in: c183ea3 , 1a11ff0 , 75f060d , e9739c7

2st Test Feedback

• Add solution to recover lxterminal as default(while installing DEB)
• The theming for PiOS X11 & Wayland
• Improve Screenshot scaling in Software
• Improve Software Tab LODING TIME
• One Click instead of Double Click in Software
• passwordless SUDO?
• Raspi Appearance Settings Doubled
• More ToolTips
• Check for misspelled words
• Button state at interupt
• Bring back one-click installers
• Implement More Ram installer

Verified

• Raspberry Pi 5 compatibility
• Raspberry Pi 4 compatibility
• Raspberry Pi OS compatibility
• Ubuntu 23.10 compatibility
• Raspberry Pi OS Legacy compatibility
• Raspberry Pi OS Buster DROPED!
• Implement amd64 DEV-MODE
• Implementation of gsettings for better system access
• Split PiGro into separate files
• Global Theme Method
• Dependency gdebi
• Dependency mousepad
• Dependency wmctrl

To-Do

Dashboard

• All Live Stats
• Snap Package Counter
• Check Internet Connection
• Arm Model
• Distro Logos

Update

• All Actions with pkexec
• Replace dpkg -i with gdebi >>>> add gdebi to Dependiencies
• Add Update Snap Button
• Add Nala
• Add Flatpak

Sources

• Add Button to open Folder

System

• Disable Button if tool not installed
• Remove "Update Linux Kernel" > Not working anymore
• Fix FM GODE MODE
• Add sudo dpkg-reconfigure keyboard-configuration f6e8b59
• Add sudo dpkg-reconfigure locales f6e8b59
• Add dmesg --follow f6e8b59

Look

• Remove Tasksel, Change DE, Change WM
• Disable Buttons that not work in Bullseye

Autostart

• Theme Widgets

Tasks

• Theme Button

Software

• Make all Tabs alike APT
• Move Nice 2 Have to Software Tab

Tuning

• Disable Pi4 Presets on Pi5
• Add new Overvoltage SpinBox
• Merge Custom Setting with Current Settings
• Remove Chromium32 installer
• Improve SWAP/Z-RAM Management

All

• Dash
• Update
• Source
• System
• Look
• Auto
• Task
• Software
• Nice
• Tuning
• Backup
• Links
• About
• PopUps
• Resorcess

Impressions

Does ZRAM actually do anything?

It looks like pigro only installs zram-tools. Does that automatically set up zram as a swapspace, or is the user expected to do that manually?

I suggest reading the Pi-Apps zram script. https://github.com/Botspot/pi-apps/blob/master/apps/More%20RAM/install

Test

Test:
/polls Option1 'Option 2' "Option 3"

24.03 To Do List

• Full Upgrade without function c7d33a9
• No Screenshot on some Flatpaks 10b5afc
• Add -y to all update options c7d33a9
• Remove PiKiss from Quick Install (Pi-Apps) 3b4195b
• Check if lxde-pi config exsists 7bb4bdd
• Test PiGro on Ubuntu 24.04

Feel free to add some more bugs ;-)

• Merge dev > main

Ideas for 24.04 ?

- List install packages + uninstall option

apt list --manual-installed
flatpak list --columns=name --columns=application --app

Improvements

I recently tried PiGro and had a few suggestions to make.

• In install.sh, you can substantially speed up execution-time by installing all of the apt-packages at once.

  sudo apt-get install xterm python3-pil python3-pil.imagetk python3-pip mpg123 lolcat -y
  pip3 install psutil distro

• Several scripts refer to /home/pi. This will cause problems for anybody who is using any different username other than pi. I suggest you make use of the $HOME environment variable.
• For the 7000 people who have installed PiGro from Pi-Apps, all dependencies really should have been installed by Pi-Apps, rather than during first launch of PiGro. Please open a PR on the Pi-Apps repo to install xterm python3-pil python3-pil.imagetk python3-pip mpg123 lolcat.
• For overclocking, over_voltage can actually go all the way to 16. I currently have mine set at 14, and it's super stable.

Remove PiKISS from PiGro

We at Pi-Apps today finally had to stop offering PiKISS due to a history of it being poorly maintained and the combative behavior from the developer.
See: jmcerrejon/PiKISS#209 (comment)

PiGro currently has a one-click for installing PiGro from Pi-Apps, which will no longer work.
You could either add pikiss integration into PiGro yourself, or just remove it as we have done. It's up to you, but I thought it would be nice to let you know of the change before somebody complains that the piKiss install button stopped working.

Git Clone Error

At the moment there is a bug when cloning from Pigro. This only appears with Raspberry Pi OS (Buster/Lagecy). Version 23.01 and 23.02 are mixed and the program will crash. To fix this you can use the DEV Branch Installer. This is not affected by the bug! Before that, you should delete the Pigro-Aid- in your home directory.

Command:
wget -qO- https://raw.githubusercontent.com/actionschnitzel/PiGro-Aid-/installer/dev_test_install.sh |bash

Why require xterm?

PiGro appears to use x-terminal-emulator as all other programs do, but for some reason PiGro also lists xterm as a required dependency. Why is that?
I personally don't like installing xterm, because whenever a new terminal is installed, update-alternatives will switch to treat the new terminal as user-preferred. Meaning that on fresh PiOS, before installing PiGro, opening a terminal means you get the nice lxterminal which is fast, easy to read, well-themed, and supports copy-and-paste. But after installing PiGro, now the rest of the system will use xterm, which uses a much smaller font, is not themed well, does not support clipboard...

Have you considered using something like the pi-apps terminal-run script instead? Terminal-run is special in that it supports the user's choice of terminal, but allows you to run newline-separated lists of commands while setting the terminal title. https://github.com/Botspot/pi-apps/blob/master/etc/terminal-run

Check Folders not opening

Xterm FIX

If Xterm is missing on your OS the PI will freeze.

FIX: sudo apt-get install xterm

Installer is fixed

To Do 24.02

• Change config.txt path for PiOS to /boot/firmware/config.txt

Make ~/PiGro-Aid-/scripts/fmsudo executable when installing

Otherwise you get a 'permission denied' error when clicking on 'FM God Mode' in the 'system tab'.

A port to Ubuntu is on the way.

A port to Ubuntu is on the way.

-Main problem: The .desktop files are not displayed in the menu and (no matter how) they are not executable ...

The rest works

-.-

Improvements to System tab

On my Bullseye 64-bit system, deskpi-config is not a working command, yet PiGro displays the button and is not disabling the button. I just installed your updated PiGro from your PR on pi-apps. Was deskpi something that was supposed to be pulled in as a dependency?

Also, consider adding a button that opens a terminal and runs dmesg --follow. This is very useful to diagnose USB disconnection issues and is a good way to monitor any other hot-swapping peripheral changes as they occur in real time.

Pi-Gro won't start after update

Error on startup.

OS: Raspbian GNU/Linux 10 (buster)
OS architecture: 32-bit
Kernel: armv7l 5.10.103-v7l+
Device model: Raspberry Pi 4 Model B Rev 1.2 
Cpu name: Cortex-A72
Ram size: 3.65 GB
Raspberry Pi OS image version: 2021-05-07
Language: en_US.UTF-8

pi@raspberrypi:~ $ /home/pi/PiGro-Aid-/start.sh
[Info]: Hi,pi waz uuuuup?!
[Info]: /home/pi is your home directory!
[Info]: PiGro directory is /home/pi
[Info]: Folder: .pigro exsists
[Info]: pigro.conf exsists
[Info]: Your Distro is: raspbian
[Info]: Your DE is: LXDE
[Info]: Pi-Apps is installed list will be added
[Info]: Snap is installed
[Info]: Flatpak is installed
[Info]: 9 Flatpaks are installed
[Info]: pigro.conf exists
[Info]: 4043 .deb Packages Installed
[Info]: Dark Theme
Traceback (most recent call last):
  File "/home/pi/PiGro-Aid-/src/pigro_main.py", line 7368, in <module>
    app = MainApplication()
  File "/home/pi/PiGro-Aid-/src/pigro_main.py", line 49, in __init__
    file=f"{Application_path}/images/icons/logo.png")
  File "/usr/lib/python3.7/tkinter/__init__.py", line 3545, in __init__
    Image.__init__(self, 'photo', name, cnf, master, **kw)
  File "/usr/lib/python3.7/tkinter/__init__.py", line 3501, in __init__
    self.tk.call(('image', 'create', imgtype, name,) + options)
_tkinter.TclError: couldn't open "/home/pi/images/icons/logo.png": no such file or directory