The point is that I read all of your answers, but unfortunately not all of them are useful.
You advised me to remove unwanted packages. I did it, and then my operating system stopped working.
So it comes out that I would have to ask you before each packet removal. Even before removal of those, which are theoretically extra and not important.
In my opinion, all my questions are different, but of course the "Diocese belongs to you" and you can throw me out of your Forum. This will be the fastest and the simplest answer to all my questions.
And one more thing: Someone wise once said:
"There are no stupid questions, there are only stupid answers."
However, if you decide otherwise, please tell me which of the following packages I can remove without worries that the operating system will not survive:601:ii libnotify-bin 0.7.6-2svn1 amd64 sends desktop notifications to a notification daemon (Utilities)
356:ii libdee-1.0-4:amd64 1.2.7+15.04.20150304-0ubuntu2 amd64 model to synchronize multiple instances over DBus - shared lib
1098:ii zeitgeist-core 0.9.16-0ubuntu4 amd64 event logging framework - engine
875:ii mtools 4.0.18-2ubuntu0.16.04 amd64 Tools for manipulating MSDOS files
1053:ii vbetool 1.1-3 amd64 run real-mode video BIOS code to alter hardware state
1054:ii virtualbox-guest-utils 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 x86 virtualization solution - non-X11 guest utilities
1055:ii virtualbox-guest-x11 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 x86 virtualization solution - X11 guest utilities
1078:ii xserver-common 2:1.18.4-0ubuntu0.7 all common files used by various X servers
1079:ii xserver-xorg 1:7.7+13ubuntu3 amd64 X.Org X server
1080:ii xserver-xorg-core 2:1.18.4-0ubuntu0.7 amd64 Xorg X server - core server
1081:ii xserver-xorg-input-all 1:7.7+13ubuntu3 amd64 X.Org X server -- input driver metapackage
1082:ii xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 amd64 X.Org X server -- evdev input driver
1083:ii xserver-xorg-input-synaptics 1.8.2-1ubuntu3 amd64 Synaptics TouchPad driver for X.Org server
1084:ii xserver-xorg-input-vmmouse 1:13.1.0-1ubuntu2 amd64 X.Org X server -- VMMouse input driver to use with VMWare
1085:ii xserver-xorg-input-wacom 1:0.32.0-0ubuntu3 amd64 X.Org X server -- Wacom input driver
1086:ii xserver-xorg-video-all 1:7.7+13ubuntu3 amd64 X.Org X server -- output driver metapackage
1087:ii xserver-xorg-video-amdgpu 1.1.2-0ubuntu0.16.04.1 amd64 X.Org X server -- AMDGPU display driver
1088:ii xserver-xorg-video-ati 1:7.7.0-1 amd64 X.Org X server -- AMD/ATI display driver wrapper
1089:ii xserver-xorg-video-fbdev 1:0.4.4-1build5 amd64 X.Org X server -- fbdev display driver
1090:ii xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 amd64 X.Org X server -- Intel i8xx, i9xx display driver
1091:ii xserver-xorg-video-nouveau 1:1.0.12-1build2 amd64 X.Org X server -- Nouveau display driver
1092:ii xserver-xorg-video-qxl 0.1.4-3ubuntu3 amd64 X.Org X server -- QXL display driver
1093:ii xserver-xorg-video-radeon 1:7.7.0-1 amd64 X.Org X server -- AMD/ATI Radeon display driver
1094:ii xserver-xorg-video-vesa 1:2.3.4-1build2 amd64 X.Org X server -- VESA display driver
1095:ii xserver-xorg-video-vmware 1:13.1.0-2ubuntu3 amd64 X.Org X server -- VMware display driver
and all basic functionalities still will work fine, such as GUI, WIFI, the possibility of installing new packages and applications, etc. etc.
That depends on your hardware! You should probably google every package against your computers hardware specs, and see if you need them. Otherwise install systemback make a restore point, and remove them 1 by 1 and keep redoing it until you get it right. But first you need to google how to boot to the command line and run the necessary commands to restore your systemback, backup.
This is the way you learn. or better yet install a virtual pc and install bodhi on it. Then you won't wreck your os past your experience to fix it. But you will have to learn about virtual pc's too.
Your question has already been answered. all the packages installed on bodhi are required for operation on a wide array of hardware. It is not built to just run one persons hardware.Go to the full post