uninstall programms, restore previous system-state?

[Nitya Deva]

I have recently (yesterday) installed an amount of application. Now my system is not as fast anymore as I think it should be. Is there a possibility to easily uninstall everything of the last 24 hours? I am happy to be able to see the new programs via the terminal, but the command
sudo apt-get remove --purge
always says:

Code: Select all

E: Paket automake.md5sums kann nicht gefunden werden.
E: Mittels des Musters »automake.md5sums« konnte kein Paket gefunden werden.
E: Mittels regulärem Ausdruck »automake.md5sums« konnte kein Paket gefunden werden.

Which means that the application couldn't be found. And it seems it doesn't matter what name I enter instead of automake.md5sums!

So, how to uninstall the latest programs or maybe how to restore an earlier system-state?

Thank you very much!

[Larry78723]

Please open a terminal full screen and run the following command

Code: Select all

inxi -Fxzd

Highlight the results and copy them (ctrl-shift-c) and enclose the results between the code markers by selecting </> from the mini toolbar above the textbox where you type your reply then paste (ctrl-v) them in your reply.

The results will help us to help you.

[karlchen]

Hello, Nitya Deva.

I assume that you do not use Timeshift?!

In case you used Timeshift and in case you had created a new Timeshift system snapshot right before installing software updates, returning to the previous system state would be relatively simple, by restoring your system to the last Timeshift snapshot.

In case there is no such Timeshift snapshot, to which the system could be reverted, reverting is a manual procedure.
You can launch Synaptic Package Manager from the Mint application menu.
Inside Synaptic, you navigate to File => History.
In its History, Synaptic logs every update installation, every new installation and every removal operation. The History is ordered by day and time in descending order, i.e. from most recent to oldest.
So you navigate to "May 2019" and then to the appropriate day.

For each update/installation/uninstallation, you will find the details in the right hand pane of the History window.
You can mark the content of the complete right hand pane, by pressing <Ctrl>A <Ctrl>C.
You can paste the copied history text into a text editor e.g. and print it out. (You will need the print out for the steps below)

Synaptic has logged in detail

• the name and the precise version of each software package, which has been newly installed
  (reverting the installation means marking the same software package for removal in Synaptic and applying the operation)
• the name of each software package, which has been updated. Synaptic precisely tells from which previous version the package has been updated to which new version.
  (reverting the update means marking the same software package, clicking on "Package" => "Force Version" => selecting the version before the update and applying the version downgrade)
• the name of each software package, which has been removed.
  (reverting the removal means marking the same software package for installation and applying the installation)

HTH,
Karl

[Nitya Deva]

Please open a terminal full screen and run the following command

Code: Select all

inxi -Fxzd

Code: Select all

inxi -Fxzd
System:    Host: nitya-davas Kernel: 4.15.0-45-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 2.24.30)
           Distro: Linux Mint 18.3 Sylvia
Machine:   Mobo: Acer model: Nami_CZL v: V1.08
           Bios: Insyde v: V1.08 date: 09/15/2015
CPU:       Quad core AMD A4-7210 APU with AMD Radeon R3 Graphics (-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 14373
           clock speeds: max: 1800 MHz 1: 1193 MHz 2: 1142 MHz 3: 1143 MHz
           4: 1172 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R3 Graphics]
           bus-ID: 00:01.0
           Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.00hz
           GLX Renderer: AMD MULLINS (DRM 2.50.0 / 4.15.0-45-generic, LLVM 6.0.0)
           GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel bus-ID: 00:14.2
           Card-2 Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio
           driver: snd_hda_intel bus-ID: 00:01.1
           Sound: Advanced Linux Sound Architecture v: k4.15.0-45-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 2000 bus-ID: 02:00.0
           IF: enp2s0 state: down mac: <filter>
           Card-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
           driver: ath10k_pci bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 1000.2GB (4.6% used)
           ID-1: /dev/sda model: WDC_WD10JPVX size: 1000.2GB
           Optical: No optical drives detected.
Partition: ID-1: / size: 46G used: 37G (85%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 7.34GB used: 0.07GB (1%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 43.0C mobo: N/A gpu: 44.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 207 Uptime: 7:04 Memory: 2490.3/3404.8MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[Nitya Deva]

Hallo Karl,
I have installed Timeshift since the first days I have installed Linux. But it looks like I have never made an security copy of the system!
And in Synaptic the entries stop in Feb 2019! Probably I haven't installed any real package
When I enter
ls /var/lib/dpkg/info/ -ltc|more
in the terminal I find the following:

Code: Select all

insgesamt 117524
-rw-r--r-- 1 root root    8651 Mai 27 10:55 automake.md5sums
-rwxr-xr-x 1 root root     385 Mai 27 10:55 automake.postinst
-rwxr-xr-x 1 root root     790 Mai 27 10:55 automake.preinst
-rwxr-xr-x 1 root root     125 Mai 27 10:55 automake.prerm
-rw-r--r-- 1 root root    5048 Mai 27 10:55 automake.list
-rw-r--r-- 1 root root       0 Mai 27 10:52 libreadline-dev:amd64.md5sums
-rw-r--r-- 1 root root      65 Mai 27 10:52 libreadline-dev:amd64.list
-rw-r--r-- 1 root root     666 Mai 27 10:52 libreadline6-dev:amd64.md5sums
-rw-r--r-- 1 root root     569 Mai 27 10:52 libreadline6-dev:amd64.list
-rw-r--r-- 1 root root     429 Mai 27 10:52 libtinfo-dev:amd64.md5sums
-rw-r--r-- 1 root root     495 Mai 27 10:52 libtinfo-dev:amd64.list
-rw-r--r-- 1 root root   19851 Mai 27 10:51 libgtk2.0-dev.md5sums
-rwxr-xr-x 1 root root     281 Mai 27 10:51 libgtk2.0-dev.preinst
-rwxr-xr-x 1 root root     236 Mai 27 10:51 libgtk2.0-dev.prerm
-rw-r--r-- 1 root root   11602 Mai 27 10:51 libgtk2.0-dev.list
-rw-r--r-- 1 root root     296 Mai 27 10:51 libxdamage-dev:amd64.md5sums
-rw-r--r-- 1 root root     447 Mai 27 10:51 libxdamage-dev:amd64.list
-rw-r--r-- 1 root root     471 Mai 27 10:51 x11proto-damage-dev.md5sums
-rw-r--r-- 1 root root     421 Mai 27 10:51 x11proto-damage-dev.list
-rw-r--r-- 1 root root     377 Mai 27 10:51 libxcomposite-dev.md5sums
-rw-r--r-- 1 root root    1114 Mai 27 10:51 libxcomposite-dev.list
-rw-r--r-- 1 root root     488 Mai 27 10:51 x11proto-composite-dev.md5sums
-rw-r--r-- 1 root root     441 Mai 27 10:51 x11proto-composite-dev.list
-rw-r--r-- 1 root root     359 Mai 27 10:51 libxcursor-dev:amd64.md5sums
-rw-r--r-- 1 root root    1977 Mai 27 10:51 libxcursor-dev:amd64.list
-rw-r--r-- 1 root root     357 Mai 27 10:51 libxrandr-dev:amd64.md5sums
-rw-r--r-- 1 root root    1123 Mai 27 10:51 libxrandr-dev:amd64.list
-rw-r--r-- 1 root root     460 Mai 27 10:51 x11proto-randr-dev.md5sums
-rw-r--r-- 1 root root     409 Mai 27 10:51 x11proto-randr-dev.list
-rw-r--r-- 1 root root    3534 Mai 27 10:51 libxi-dev.md5sums
-rw-r--r-- 1 root root    3722 Mai 27 10:51 libxi-dev.list
-rw-r--r-- 1 root root     357 Mai 27 10:51 libxfixes-dev:amd64.md5sums
-rw-r--r-- 1 root root     507 Mai 27 10:51 libxfixes-dev:amd64.list
-rw-r--r-- 1 root root     466 Mai 27 10:51 x11proto-fixes-dev.md5sums
-rw-r--r-- 1 root root     415 Mai 27 10:51 x11proto-fixes-dev.list
-rw-r--r-- 1 root root     443 Mai 27 10:51 libxinerama-dev:amd64.md5sums
-rw-r--r-- 1 root root     748 Mai 27 10:51 libxinerama-dev:amd64.list
-rw-r--r-- 1 root root     319 Mai 27 10:51 x11proto-xinerama-dev.md5sums
-rw-r--r-- 1 root root     337 Mai 27 10:51 x11proto-xinerama-dev.list
-rw-r--r-- 1 root root    3648 Mai 27 10:51 libpango1.0-dev.md5sums
-rwxr-xr-x 1 root root     203 Mai 27 10:51 libpango1.0-dev.preinst
-rw-r--r-- 1 root root    2712 Mai 27 10:51 libpango1.0-dev.list
-rw-r--r-- 1 root root     401 Mai 27 10:51 libxft-dev.md5sums
-rw-r--r-- 1 root root     502 Mai 27 10:51 libxft-dev.list
-rw-r--r-- 1 root root    2243 Mai 27 10:51 libharfbuzz-dev.md5sums
-rw-r--r-- 1 root root    1563 Mai 27 10:51 libharfbuzz-dev.list
-rw-r--r-- 1 root root     171 Mai 27 10:51 libharfbuzz-gobject0:amd64.md5sums
-rw-r--r-- 1 root root     111 Mai 27 10:51 libharfbuzz-gobject0:amd64.shlibs
-rw-r--r-- 1 root root    1177 Mai 27 10:51 libharfbuzz-gobject0:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:51 libharfbuzz-gobject0:amd64.triggers
-rw-r--r-- 1 root root     317 Mai 27 10:51 libharfbuzz-gobject0:amd64.list
-rw-r--r-- 1 root root    1989 Mai 27 10:51 libgdk-pixbuf2.0-dev.md5sums
-rw-r--r-- 1 root root    1835 Mai 27 10:51 libgdk-pixbuf2.0-dev.list
-rw-r--r-- 1 root root    2473 Mai 27 10:51 libcairo2-dev.md5sums
-rw-r--r-- 1 root root    1856 Mai 27 10:51 libcairo2-dev.list
-rw-r--r-- 1 root root     282 Mai 27 10:51 libxcb-shm0-dev:amd64.md5sums
-rw-r--r-- 1 root root     407 Mai 27 10:51 libxcb-shm0-dev:amd64.list
-rw-r--r-- 1 root root     294 Mai 27 10:51 libxcb-render0-dev:amd64.md5sums
-rw-r--r-- 1 root root     428 Mai 27 10:51 libxcb-render0-dev:amd64.list
-rw-r--r-- 1 root root     392 Mai 27 10:51 libsm-dev:amd64.md5sums
-rw-r--r-- 1 root root     454 Mai 27 10:51 libsm-dev:amd64.list
-rw-r--r-- 1 root root     592 Mai 27 10:51 libice-dev:amd64.md5sums
-rw-r--r-- 1 root root     559 Mai 27 10:51 libice-dev:amd64.list
-rw-r--r-- 1 root root    3230 Mai 27 10:51 libxext-dev:amd64.md5sums
-rw-r--r-- 1 root root    3594 Mai 27 10:51 libxext-dev:amd64.list
-rw-r--r-- 1 root root    4634 Mai 27 10:51 x11proto-xext-dev.md5sums
-rw-r--r-- 1 root root    2734 Mai 27 10:51 x11proto-xext-dev.list
-rw-r--r-- 1 root root     377 Mai 27 10:51 libxrender-dev:amd64.md5sums
-rw-r--r-- 1 root root     495 Mai 27 10:51 libxrender-dev:amd64.list
-rw-r--r-- 1 root root     467 Mai 27 10:51 x11proto-render-dev.md5sums
-rw-r--r-- 1 root root     417 Mai 27 10:51 x11proto-render-dev.list
-rw-r--r-- 1 root root     869 Mai 27 10:51 libx11-dev:amd64.md5sums
-rw-r--r-- 1 root root     650 Mai 27 10:51 libx11-dev:amd64.list
-rw-r--r-- 1 root root     507 Mai 27 10:51 libxcb1-dev:amd64.md5sums
-rw-r--r-- 1 root root     488 Mai 27 10:51 libxcb1-dev:amd64.list
-rw-r--r-- 1 root root     333 Mai 27 10:51 libpthread-stubs0-dev:amd64.md5sums
-rw-r--r-- 1 root root     343 Mai 27 10:51 libpthread-stubs0-dev:amd64.list
-rw-r--r-- 1 root root    1186 Mai 27 10:50 xtrans-dev.md5sums
-rw-r--r-- 1 root root     779 Mai 27 10:50 xtrans-dev.list
-rw-r--r-- 1 root root    1602 Mai 27 10:50 x11proto-kb-dev.md5sums
-rw-r--r-- 1 root root    1053 Mai 27 10:50 x11proto-kb-dev.list
-rw-r--r-- 1 root root     834 Mai 27 10:50 x11proto-input-dev.md5sums
-rw-r--r-- 1 root root     618 Mai 27 10:50 x11proto-input-dev.list
-rw-r--r-- 1 root root     351 Mai 27 10:50 libxdmcp-dev:amd64.md5sums
-rw-r--r-- 1 root root     435 Mai 27 10:50 libxdmcp-dev:amd64.list
-rw-r--r-- 1 root root     913 Mai 27 10:50 libxau-dev:amd64.md5sums
-rw-r--r-- 1 root root     762 Mai 27 10:50 libxau-dev:amd64.list
-rw-r--r-- 1 root root    1948 Mai 27 10:50 x11proto-core-dev.md5sums
-rw-r--r-- 1 root root    1043 Mai 27 10:50 x11proto-core-dev.list
-rw-r--r-- 1 root root     776 Mai 27 10:50 xorg-sgml-doctools.md5sums
-rw-r--r-- 1 root root     562 Mai 27 10:50 xorg-sgml-doctools.list
-rw-r--r-- 1 root root   36630 Mai 27 10:50 libfontconfig1-dev:amd64.md5sums
-rw-r--r-- 1 root root   23646 Mai 27 10:50 libfontconfig1-dev:amd64.list
-rw-r--r-- 1 root root   16412 Mai 27 10:50 libfreetype6-dev:amd64.md5sums
-rw-r--r-- 1 root root   10666 Mai 27 10:50 libfreetype6-dev:amd64.list
-rw-r--r-- 1 root root     855 Mai 27 10:50 libpng12-dev:amd64.md5sums
-rw-r--r-- 1 root root    1075 Mai 27 10:50 libpng12-dev:amd64.list
-rw-r--r-- 1 root root    1500 Mai 27 10:50 libexpat1-dev:amd64.md5sums
-rw-r--r-- 1 root root    1311 Mai 27 10:50 libexpat1-dev:amd64.list
-rw-r--r-- 1 root root     187 Mai 27 10:50 libcairo-script-interpreter2:amd64.md5sums
-rw-r--r-- 1 root root      71 Mai 27 10:50 libcairo-script-interpreter2:amd64.shlibs
-rw-r--r-- 1 root root     558 Mai 27 10:50 libcairo-script-interpreter2:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:50 libcairo-script-interpreter2:amd64.triggers
-rw-r--r-- 1 root root     518 Mai 27 10:50 libcairo-script-interpreter2:amd64.list
-rw-r--r-- 1 root root    2670 Mai 27 10:50 libatk1.0-dev.md5sums
-rw-r--r-- 1 root root    1860 Mai 27 10:50 libatk1.0-dev.list
-rw-r--r-- 1 root root     301 Mai 27 10:50 gir1.2-gtk-2.0.md5sums
-rw-r--r-- 1 root root     318 Mai 27 10:50 gir1.2-gtk-2.0.list
-rw-r--r-- 1 root root     177 Mai 27 10:50 gir1.2-gdkpixbuf-2.0:amd64.md5sums
-rw-r--r-- 1 root root     403 Mai 27 10:50 gir1.2-gdkpixbuf-2.0:amd64.list
-rw-r--r-- 1 root root    2056 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.md5sums
-rwxr-xr-x 1 root root    1047 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.postinst
-rwxr-xr-x 1 root root     271 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.postrm
-rw-r--r-- 1 root root     236 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.shlibs
-rw-r--r-- 1 root root    6493 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.symbols
-rw-r--r-- 1 root root     189 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.triggers
-rw-r--r-- 1 root root    1747 Mai 27 10:50 libgdk-pixbuf2.0-0:amd64.list
-rw-r--r-- 1 root root     334 Mai 27 10:50 libgdk-pixbuf2.0-common.md5sums
-rw-r--r-- 1 root root     275 Mai 27 10:50 libgdk-pixbuf2.0-common.list
-rw-r--r-- 1 root root     212 Mai 27 10:50 libperl-dev.md5sums
-rwxr-xr-x 1 root root     182 Mai 27 10:50 libperl-dev.postinst
-rwxr-xr-x 1 root root     182 Mai 27 10:50 libperl-dev.postrm
-rwxr-xr-x 1 root root     182 Mai 27 10:50 libperl-dev.preinst
-rwxr-xr-x 1 root root     182 Mai 27 10:50 libperl-dev.prerm
-rw-r--r-- 1 root root     293 Mai 27 10:50 libperl-dev.list
-rw-r--r-- 1 root root    2615 Mai 27 10:50 libspice-client-glib-2.0-dev.md5sums
-rw-r--r-- 1 root root    2042 Mai 27 10:50 libspice-client-glib-2.0-dev.list
-rw-r--r-- 1 root root    4916 Mai 27 10:50 libssl-dev:amd64.md5sums
-rw-r--r-- 1 root root    2771 Mai 27 10:50 libssl-dev:amd64.list
-rw-r--r-- 1 root root    2188 Mai 27 10:50 libspice-protocol-dev.md5sums
-rw-r--r-- 1 root root    1456 Mai 27 10:50 libspice-protocol-dev.list
-rw-r--r-- 1 root root     240 Mai 27 10:50 libqtglib-2.0-0:amd64.md5sums
-rwxr-xr-x 1 root root     135 Mai 27 10:50 libqtglib-2.0-0:amd64.postinst
-rwxr-xr-x 1 root root     132 Mai 27 10:50 libqtglib-2.0-0:amd64.postrm
-rw-r--r-- 1 root root      32 Mai 27 10:50 libqtglib-2.0-0:amd64.shlibs
-rw-r--r-- 1 root root    9604 Mai 27 10:50 libqtglib-2.0-0:amd64.symbols
-rw-r--r-- 1 root root     286 Mai 27 10:50 libqtglib-2.0-0:amd64.list
-rw-r--r-- 1 root root     243 Mai 27 10:50 libqt5glib-2.0-0:amd64.md5sums
-rwxr-xr-x 1 root root     135 Mai 27 10:50 libqt5glib-2.0-0:amd64.postinst
-rwxr-xr-x 1 root root     132 Mai 27 10:50 libqt5glib-2.0-0:amd64.postrm
-rw-r--r-- 1 root root      34 Mai 27 10:50 libqt5glib-2.0-0:amd64.shlibs
-rw-r--r-- 1 root root    9458 Mai 27 10:50 libqt5glib-2.0-0:amd64.symbols
-rw-r--r-- 1 root root     291 Mai 27 10:50 libqt5glib-2.0-0:amd64.list
-rw-r--r-- 1 root root     364 Mai 27 10:50 libpixman-1-dev.md5sums
-rw-r--r-- 1 root root     462 Mai 27 10:50 libpixman-1-dev.list
-rw-r--r-- 1 root root     174 Mai 27 10:50 gir1.2-spice-client-glib-2.0.md5sums
-rw-r--r-- 1 root root     285 Mai 27 10:50 gir1.2-spice-client-glib-2.0.list
-rw-r--r-- 1 root root     266 Mai 27 10:50 libspice-client-glib-2.0-8:amd64.md5sums
-rw-r--r-- 1 root root     103 Mai 27 10:50 libspice-client-glib-2.0-8:amd64.shlibs
-rw-r--r-- 1 root root    8246 Mai 27 10:50 libspice-client-glib-2.0-8:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:50 libspice-client-glib-2.0-8:amd64.triggers
-rw-r--r-- 1 root root     447 Mai 27 10:50 libspice-client-glib-2.0-8:amd64.list
-rw-r--r-- 1 root root     379 Mai 27 10:50 spice-client-glib-usb-acl-helper.md5sums
-rwxr-xr-x 1 root root     226 Mai 27 10:50 spice-client-glib-usb-acl-helper.postinst
-rwxr-xr-x 1 root root     203 Mai 27 10:50 spice-client-glib-usb-acl-helper.postrm
-rw-r--r-- 1 root root     405 Mai 27 10:50 spice-client-glib-usb-acl-helper.list
-rw-r--r-- 1 root root     301 Mai 27 10:50 libusbredirhost1:amd64.md5sums
-rw-r--r-- 1 root root      35 Mai 27 10:50 libusbredirhost1:amd64.shlibs
-rw-r--r-- 1 root root     488 Mai 27 10:50 libusbredirhost1:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:50 libusbredirhost1:amd64.triggers
-rw-r--r-- 1 root root     369 Mai 27 10:50 libusbredirhost1:amd64.list
-rw-r--r-- 1 root root     250 Mai 27 10:50 libusbredirparser1:amd64.md5sums
-rw-r--r-- 1 root root      39 Mai 27 10:50 libusbredirparser1:amd64.shlibs
-rw-r--r-- 1 root root    2211 Mai 27 10:50 libusbredirparser1:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:50 libusbredirparser1:amd64.triggers
-rw-r--r-- 1 root root     303 Mai 27 10:50 libusbredirparser1:amd64.list
-rw-r--r-- 1 root root     226 Mai 27 10:49 libcacard0:amd64.md5sums
-rw-r--r-- 1 root root      23 Mai 27 10:49 libcacard0:amd64.shlibs
-rw-r--r-- 1 root root    2325 Mai 27 10:49 libcacard0:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:49 libcacard0:amd64.triggers
-rw-r--r-- 1 root root     263 Mai 27 10:49 libcacard0:amd64.list
-rwxr-xr-x 1 root root    7818 Mai 27 10:49 libssl1.0.0:amd64.postinst
-rw-r--r-- 1 root root    1413 Mai 27 10:49 libssl1.0.0:amd64.md5sums
-rwxr-xr-x 1 root root     206 Mai 27 10:49 libssl1.0.0:amd64.postrm
-rw-r--r-- 1 root root     179 Mai 27 10:49 libssl1.0.0:amd64.shlibs
-rw-r--r-- 1 root root  162263 Mai 27 10:49 libssl1.0.0:amd64.symbols
-rw-r--r-- 1 root root   33400 Mai 27 10:49 libssl1.0.0:amd64.templates
-rw-r--r-- 1 root root      60 Mai 27 10:49 libssl1.0.0:amd64.triggers
-rw-r--r-- 1 root root    1096 Mai 27 10:49 libssl1.0.0:amd64.list
-rw-r--r-- 1 root root    6588 Mai 27 10:49 libsystemd-dev:amd64.md5sums
-rw-r--r-- 1 root root   17480 Mai 27 10:49 libsystemd-dev:amd64.list
-rw-r--r-- 1 root root     605 Mai 27 10:49 systemd.conffiles
-rw-r--r-- 1 root root   31841 Mai 27 10:49 systemd.md5sums
-rwxr-xr-x 1 root root    7460 Mai 27 10:49 systemd.postinst
-rwxr-xr-x 1 root root    2017 Mai 27 10:49 systemd.postrm
-rwxr-xr-x 1 root root    2344 Mai 27 10:49 systemd.preinst
-rwxr-xr-x 1 root root    1342 Mai 27 10:49 systemd.prerm
-rw-r--r-- 1 root root      71 Mai 27 10:49 systemd.triggers
-rw-r--r-- 1 root root   28732 Mai 27 10:49 systemd.list
-rw-r--r-- 1 root root     224 Mai 27 10:49 libsystemd0:i386.md5sums
-rw-r--r-- 1 root root      25 Mai 27 10:49 libsystemd0:i386.shlibs
-rw-r--r-- 1 root root   18393 Mai 27 10:49 libsystemd0:i386.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:49 libsystemd0:i386.triggers
-rw-r--r-- 1 root root     247 Mai 27 10:49 libsystemd0:i386.list
-rw-r--r-- 1 root root     226 Mai 27 10:49 libsystemd0:amd64.md5sums
-rw-r--r-- 1 root root      25 Mai 27 10:49 libsystemd0:amd64.shlibs
-rw-r--r-- 1 root root   18393 Mai 27 10:49 libsystemd0:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:49 libsystemd0:amd64.triggers
-rw-r--r-- 1 root root     253 Mai 27 10:49 libsystemd0:amd64.list
-rw-r--r-- 1 root root     286 Mai 27 10:49 libpam-systemd:amd64.md5sums
-rwxr-xr-x 1 root root     224 Mai 27 10:49 libpam-systemd:amd64.postinst
-rwxr-xr-x 1 root root     193 Mai 27 10:49 libpam-systemd:amd64.postrm
-rwxr-xr-x 1 root root     193 Mai 27 10:49 libpam-systemd:amd64.preinst
-rwxr-xr-x 1 root root     898 Mai 27 10:49 libpam-systemd:amd64.prerm
-rw-r--r-- 1 root root     384 Mai 27 10:49 libpam-systemd:amd64.list
-rw-r--r-- 1 root root    1244 Mai 27 10:45 libudev-dev:amd64.md5sums
-rwxr-xr-x 1 root root     180 Mai 27 10:45 libudev-dev:amd64.postinst
-rwxr-xr-x 1 root root     180 Mai 27 10:45 libudev-dev:amd64.postrm
-rwxr-xr-x 1 root root     180 Mai 27 10:45 libudev-dev:amd64.preinst
-rwxr-xr-x 1 root root     180 Mai 27 10:45 libudev-dev:amd64.prerm
-rw-r--r-- 1 root root    3890 Mai 27 10:45 libudev-dev:amd64.list
-rw-r--r-- 1 root root     214 Mai 27 10:45 libudev1:i386.md5sums
-rw-r--r-- 1 root root      49 Mai 27 10:45 libudev1:i386.shlibs
-rw-r--r-- 1 root root    4080 Mai 27 10:45 libudev1:i386.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:45 libudev1:i386.triggers
-rw-r--r-- 1 root root     231 Mai 27 10:45 libudev1:i386.list
-rw-r--r-- 1 root root     216 Mai 27 10:45 libudev1:amd64.md5sums
-rw-r--r-- 1 root root      49 Mai 27 10:45 libudev1:amd64.shlibs
-rw-r--r-- 1 root root    4080 Mai 27 10:45 libudev1:amd64.symbols
-rw-r--r-- 1 root root      60 Mai 27 10:45 libudev1:amd64.triggers
-rw-r--r-- 1 root root     237 Mai 27 10:45 libudev1:amd64.list
-rw-r--r-- 1 root root     148 Mai 27 10:45 udev.conffiles
-rw-r--r-- 1 root root    5372 Mai 27 10:45 udev.md5sums
-rwxr-xr-x 1 root root    1771 Mai 27 10:45 udev.postrm
-rwxr-xr-x 1 root root    3217 Mai 27 10:45 udev.preinst
-rw-r--r-- 1 root root      34 Mai 27 10:45 udev.triggers
-rwxr-xr-x 1 root root    7624 Mai 27 10:45 udev.postinst
-rwxr-xr-x 1 root root    1679 Mai 27 10:45 udev.prerm
-rw-r--r-- 1 root root    4374 Mai 27 10:45 udev.list
-rw-r--r-- 1 root root    1395 Mai 27 10:45 libtool.md5sums
-rw-r--r-- 1 root root     952 Mai 27 10:45 libtool.list
-rw-r--r-- 1 root root     999 Mai 27 10:45 autotools-dev.md5sums
-rw-r--r-- 1 root root     811 Mai 27 10:45 autotools-dev.list
-rw-r--r-- 1 root root     594 Mai 27 10:35 stream2chromecast.md5sums
-rw-r--r-- 1 root root     461 Mai 27 10:35 stream2chromecast.list
-rw-r--r-- 1 root root    4589 Mai 26 21:19 autogen.md5sums
-rw-r--r-- 1 root root    2550 Mai 26 21:19 autogen.list
-rw-r--r-- 1 root root    2097 Mai 26 21:19 libopts25-dev:amd64.md5sums
-rw-r--r-- 1 root root    1413 Mai 26 21:19 libopts25-dev:amd64.list

...etc.
I would like to remove everything listed here.

[karlchen]

Hello, Nitya Deva.

The files in the directory /var/lib/dpkg/info are helper files, needed by the Linux Mint software management system.
They are not a list of files to uninstall. They can hardly be used to compile a list of software packages, which can be safely uninstalled.
The files do not tell you, whether the corresponding software packages have been newly installed or whether the corresponding software packages have been upgraded instead.

If your Synaptic history really stops 3 months ago, then the most likely reason is that you have re-configured Synaptic not to preserve the history.

Please, let us know the most recent modification dates of the 2 files term.log and history.log:
Terminal command: ls -l /var/log/apt/*.log

Another file which can be used to compile the list of
+ newly added (installed) software packages
+ upgraded software packages
+ removed software packages
is the file /var/log/dpkg.log. Though extracting the needed package names and version strings from dpkg.log is more hassle than simply picking them up from the Synaptic history.
But it would be feasible.

I do wonder a bit whether a pure belly feeling like

Now my system is not as fast anymore as I think it should be.

is a sufficient reason to take any drastic steps like reverting a large number of upgraded packages to their previous versions.

Regards,
Karl

[Nitya Deva]

Thank you very much, Karlchen.
the command:

ls -l /var/log/apt/*.log

shows:

-rw-r--r-- 1 root root 7098 Mai 27 10:55 /var/log/apt/history.log
-rw-r----- 1 root adm 40931 Mai 27 10:55 /var/log/apt/term.log

Isn't there a command like:

sudo apt-get remove --purge packagename

or

sudo apt purge packagename

?

Which I could use for each single one of the more than 50 entries of the 27th of May?

[gm10]

Isn't there a command like:

sudo apt-get remove --purge packagename

or

sudo apt purge packagename

?

Which I could use for each single one of the more than 50 entries of the 27th of May?

No, because you do not want to remove those packages, you want to downgrade them. While downgrading is possible in principle, the problem is that you do not have the old versions available anymore, for the repositories only hold the latest version at all times (plus, in case of upstream packages, the version the distribution originally released with - which in your case is a version from years ago so not recommended).

In case you used Timeshift and in case you had created a new Timeshift system snapshot right before installing software updates, returning to the previous system state would be relatively simple, by restoring your system to the last Timeshift snapshot.

Shameless plug: My version of Update Manager from my PPA has an option to automatically create a snapshot before applying updates. I find it super useful but Clem didn't want it for the official version at the time.

[karlchen]

Hello, Nitya Deva.

the command: ls -l /var/log/apt/*.log shows:

Code: Select all

-rw-r--r-- 1 root root  7098 Mai 27 10:55 /var/log/apt/history.log
-rw-r----- 1 root adm  40931 Mai 27 10:55 /var/log/apt/term.log

The file which holds the details for each software package, which was
+ added (newly installed)
+ upgraded from an older version to a newer version
+ removed
on May 27th, is the file /var/log/apt/history.log.

The file /var/log/apt/history.log is a pure text file and can be read with the help of the editor xed e.g.

So the technical details should be available, which would be needed in order to revert each operation executed on May 27th.
As has been stated more than once by me and by gm10, reverting would not mean uninstalling all the software packages, which the software management system touched on May 27th.
It would mean:
+ re-installing any package, which was uninstalled
+ un-installing any package, which was added
+ downgrading any package to the previous version, which had been upgraded.

gm10 may be right that downgrading to the previous version may not be possible in all those cases, where the previous version has been removed from the software repositories.

I still wonder whether your belly feeling of reduced performance is a good enough reason to revert the update operation May 27th.

Regards,
Karl

[ajgreeny]

You can list all packages installed by your package manager and the dates they were installed by running command

Code: Select all

grep -i " install " /var/log/dpkg.log.1 /var/log/dpkg.log

and if you really want to do so you can then uninstall or purge all all or any of them you installed on a particular date.

[karlchen]

Hi, ajgreeny.

Provided this statement

I have recently (yesterday) installed an amount of application.

really means that
+ a number of applications have been newly installed on the system (no updates)
+ precisely the same applications should be uninstalled again,
in this case, you are perfectly right.
grep -i " install " /var/log/dpkg.log.1 /var/log/dpkg.log can be used to identify the names of all added software packages.
As the day of installation is known, May 2th 2019, the command could be extended to list only the packages installed on that day:
grep -i " install " /var/log/dpkg.log.1 /var/log/dpkg.log | grep "2019-05-27"

Regards,
Karl
--
P.S.:
Really sorry for having made things much more complicated than they are, Nitya Deva, by trying to advise on how to revert a software upgrade operation manually, although only newly added software packages have to be identified and uninstalled again. Which is much less complicated.

[gm10]

+ precisely the same applications should be uninstalled again,

As I said above already, no, they shouldn't. OP wants to get rid of the update, not of the application as a whole. The only way to do that is to install the previous version of the same packages. ignore me

[karlchen]

Hi, gm10.

The first sentence in the first post suggests that it is all newly installed software (added, not upgraded).
I am afraid it was me who misinterpreted and thus introduced the much more complex situation of manually reverting a software upgrade.
Might be one more case, where I commited the mistake, which I blame others for: reading carelessly.

Karl

[ajgreeny]

+ precisely the same applications should be uninstalled again,

As I said above already, no, they shouldn't. OP wants to get rid of the update, not of the application as a whole. The only way to do that is to install the previous version of the same packages.

Surely, if the problems began immediately after installing the packages (NB; installing, not upgrading!) they should be purged to see if that removes the problem.
My suggested command shows only packages that were installed not those that were upgraded.

[karlchen]

Hello, Nitya Deva.

Provided you can confirm that
+ on My 27th, 2019, you only added applications to your system (i.e. new software installations, no software upgraded)
+ you wish to uninstall precisely the same list of applications,

then, please, ignore all the talk about Timeshift and about how to revert a software upgrade operation and directly jump to this post, submitted by ajgreeny.

Karl

[gm10]

Entirely my bad everyone, I'm bad at reading sometimes, for some reason I had thought from the beginning that this thread was about upgrades.