Removing unwanted upgrades [Solved]

[Bierhundt]

Code: Select all

Snapshot created on: 20210215_2039
System:    Host: <filter> Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-17-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo November 11  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0K42JR v: A01 serial: <filter> BIOS: Dell v: A17 date: 05/12/2017 
Battery:   ID-1: BAT0 charge: 38.6 Wh condition: 38.6/62.2 Wh (62%) volts: 12.3/11.1 
           model: Sanyo DELL H3K580C type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20216 
           Speed: 1647 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1463 
           2: 1463 3: 1463 4: 1460 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0a6c 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1440x900~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0be3 
           Sound Server: ALSA v: k4.19.0-17-amd64 
Network:   Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e 
           v: 3.2.6-k port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Device-2: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Dell Inspiron M5010 / XPS 8300 driver: wl v: kernel port: 7000 
           bus ID: 03:00.0 chip ID: 14e4:4727 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 698.64 GiB used: 27.56 GiB (3.9%) 
           ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS721075A9E630 size: 698.64 GiB 
           block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: A3K0 scheme: MBR 
Partition: ID-1: / raw size: 632.68 GiB size: 621.75 GiB (98.27%) used: 27.56 GiB (4.4%) 
           fs: ext4 dev: /dev/sda6 
           ID-2: swap-1 size: 4.88 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 66.0 C mobo: N/A sodimm: 45.0 C gpu: nouveau temp: 76 C 
           Fan Speeds (RPM): cpu: 2863 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 193 Uptime: 2h 09m Memory: 3.78 GiB used: 1.12 GiB (29.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I've looked in the manual for the answer to this question, but found nothing that helped me under the heading that gave info about the auto-updater. I keep getting up-grades for stuff I don't use, like Bluetooth, something called blue-z, etc. I don't need/use Bluetooth for anything and I assume that blue-z is related to that, since they both came on the same upgrade list. I removed them from the list, but when I clicked on 'upgrade', they were right back on there and then it was too late to remove them as it had already started to work.I suppose I could just copy the list and use apt-get in a terminal or Synaptic, but the auto-updater is so easy to use and it tells me if I can/need to remove 'no-longer-needed' items. {Maybe, just maybe, I'm getting lazier in my old age!}
Is there a simpler way to remove these useless items from the list, or would I be better off just using one of the two other options? Also, is there some where on this forum (or even on the Debian site), that I can check to see if what I think may be useless is actually a dependency that is needed for something else that is installed? I know I've got a big HD in this lappy, but I hate to have a bunch of useless/extraneous libraries/dependencies for apps that I don't use. Would I be causing myself grief if I removed apps like Bluetooth or other stuff that came with the MX that I have installed? I only surf the net, check emails, use Libre Office, and watch You Tube, etc.. Linux has always been secure for me, as opposed to Winblows.

One more quick question; is there a user-friendly/easy-to-use 'recovery' version of MX that someone could recommend for reviving my other lappy, which has MX on it (I think it's v.16 or v.17)? If so, I'd appreciate it if someone could leave me a link so's I can download it. The older/other lappy has Linux and Winblows 7 on it. I need to get into the Linux partition for my beer recipes on the Brewtarget app. and then I'll keep it handy, just in case I screw up something else on this current install!

THX
Bierhundt

[jeffreyC]

Can you just uninstall the package(s) that you are not using?

Or does something else that you want to keep depend on it? If that is the case you would be better off keeping it updated.

[Huckleberry Finn]

... yes, some of them may be dangerous due to dependencies. But at least you can see and/or just stop upgrading:

sudo apt-mark hold packagename

( .. and unhold to let it back )

(You can also lock / unlock version in Synaptic)
_________________________________________

and ... apt depends ( and ) apt rdepends ...

.. i.e.

Code: Select all

apt depends bluez

Code: Select all

apt rdepends bluez

________________________________________

P.S. You can start live session on the older laptop with 19.4 usb (you can also use your snapshot iso from this laptop - MX Snapshot first, then MX Live Usb Maker. But if the other one is 32bit, then you need the official 32bit iso.. You can also consider antiX Base version).

This one at the moment is one of the older machines and it's flying with all releases of MX (19.4 at the moment).. So, don't worry about it ... Just uncheck some apps that you don't want every boot - from "Session & Startup" - Autostart .. Also you can login with Fluxbox (Click Session Switcher on top bar on login screen)...

[Bierhundt]

... yes, some of them may be dangerous due to dependencies. But at least you can see and/or just stop upgrading:

sudo apt-mark hold packagename

( .. and unhold to let it back )

(You can also lock / unlock version in Synaptic)
_________________________________________

and ... apt depends ( and ) apt rdepends ...

.. i.e.

Code: Select all

apt depends bluez

Code: Select all

apt rdepends bluez

________________________________________

P.S. You can start live session on the older laptop with 19.4 usb (you can also use your snapshot iso from this laptop - MX Snapshot first, then MX Live Usb Maker. But if the other one is 32bit, then you need the official 32bit iso.. You can also consider antiX Base version).

This one at the moment is one of the older machines and it's flying with all releases of MX (19.4 at the moment).. So, don't worry about it ... Just uncheck some apps that you don't want every boot - from "Session & Startup" - Autostart .. Also you can login with Fluxbox (Click Session Switcher on top bar on login screen)...

It's been so long since I used Fluxbox, I'm not sure I could find my way around it anymore (LOL). Thanx for the help, I'll try out the hold and the depends and see what I can see. I've forgotten a lot over the years, and not kept up with aa lot of the CLI, so it will probably take me a while to get everything straightened out. i appreciate your advice.

[JayM]

Code: Select all

Snapshot created on: 20210215_2039
System:    Host: <filter> Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-17-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo November 11  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0K42JR v: A01 serial: <filter> BIOS: Dell v: A17 date: 05/12/2017 
Battery:   ID-1: BAT0 charge: 38.6 Wh condition: 38.6/62.2 Wh (62%) volts: 12.3/11.1 
           model: Sanyo DELL H3K580C type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20216 
           Speed: 1647 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1463 
           2: 1463 3: 1463 4: 1460 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:0a6c 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1440x900~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio 
           vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3b56 
           Device-2: NVIDIA High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0be3 
           Sound Server: ALSA v: k4.19.0-17-amd64 
Network:   Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e 
           v: 3.2.6-k port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Device-2: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Dell Inspiron M5010 / XPS 8300 driver: wl v: kernel port: 7000 
           bus ID: 03:00.0 chip ID: 14e4:4727 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 698.64 GiB used: 27.56 GiB (3.9%) 
           ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS721075A9E630 size: 698.64 GiB 
           block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: A3K0 scheme: MBR 
Partition: ID-1: / raw size: 632.68 GiB size: 621.75 GiB (98.27%) used: 27.56 GiB (4.4%) 
           fs: ext4 dev: /dev/sda6 
           ID-2: swap-1 size: 4.88 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 66.0 C mobo: N/A sodimm: 45.0 C gpu: nouveau temp: 76 C 
           Fan Speeds (RPM): cpu: 2863 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 193 Uptime: 2h 09m Memory: 3.78 GiB used: 1.12 GiB (29.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I've looked in the manual for the answer to this question, but found nothing that helped me under the heading that gave info about the auto-updater. I keep getting up-grades for stuff I don't use, like Bluetooth, something called blue-z, etc. I don't need/use Bluetooth for anything and I assume that blue-z is related to that, since they both came on the same upgrade list. I removed them from the list, but when I clicked on 'upgrade', they were right back on there and then it was too late to remove them as it had already started to work.I suppose I could just copy the list and use apt-get in a terminal or Synaptic, but the auto-updater is so easy to use and it tells me if I can/need to remove 'no-longer-needed' items. {Maybe, just maybe, I'm getting lazier in my old age!}
Is there a simpler way to remove these useless items from the list, or would I be better off just using one of the two other options? Also, is there some where on this forum (or even on the Debian site), that I can check to see if what I think may be useless is actually a dependency that is needed for something else that is installed? I know I've got a big HD in this lappy, but I hate to have a bunch of useless/extraneous libraries/dependencies for apps that I don't use. Would I be causing myself grief if I removed apps like Bluetooth or other stuff that came with the MX that I have installed? I only surf the net, check emails, use Libre Office, and watch You Tube, etc.. Linux has always been secure for me, as opposed to Winblows.

One more quick question; is there a user-friendly/easy-to-use 'recovery' version of MX that someone could recommend for reviving my other lappy, which has MX on it (I think it's v.16 or v.17)? If so, I'd appreciate it if someone could leave me a link so's I can download it. The older/other lappy has Linux and Winblows 7 on it. I need to get into the Linux partition for my beer recipes on the Brewtarget app. and then I'll keep it handy, just in case I screw up something else on this current install!

THX
Bierhundt

This was the post containing the solution? It's your initial post, and if it has the solution why did you even post?

Guide - How to ask for help:

When and if a solution is found that satisfies you, please let others know. Click on the check mark at the top right of the post, preferably the post that solved the problem. It will add [Solved] to the post title.

Rules of these Forums:

When a solution is found to a help request mark your topic as "solved" by clicking the check symbol at the top right of the post providing the solution. This will add [Solved] to the post title and will make it easier for others who are searching for a solution to the same issue.

New Forum Features:

When a post has given a working solution to your problem, you can now mark it solved by clicking the check mark at the upper right of the post giving the solution. {Solved} will be added to the post title. Only mark the post that has given a working solution. [Solved] will show in any topics lists. If at a later time the solution is not working the thread starter or a moderator can remove the solved designation.

Instructions for marking posts solved are given in three places, all linked to in the "Welcome!" section at the top of every page.

[Bierhundt]

JayM...
Ummmm, so I screwed up how? Why the flames?
Maybe you missed this?

It's been so long since I used Fluxbox, I'm not sure I could find my way around it anymore (LOL). Thanx for the help, I'll try out the hold and the depends and see what I can see. I've forgotten a lot over the years, and not kept up with a lot of the CLI, so it will probably take me a while to get everything straightened out. I appreciate your advice.

And I checked that it was solved.

I'll be asking another question soon becuz in doing what I did, I did screw up my current install, (Operator Error) -----

I just don't understand your post - it seems like you were angry about something I did, or didn't do. Peace!

[JayM]

I'm trying in my own not-very-sweet way to get you to read and correctly follow the instructions.

If someone with a problem searches the forum (as they should do before posting a help request) and they see a topic that's been properly marked solved, if they click on the green word [Solved} it takes them directly to the post that contains the solution so they don't have to read the entire thread and figure out which post actually solved the problem. In this thread they're taken to your very first post in which you asked for help with something which is very unhelpful to others. RichB didn't write all of those instructions because he enjoys typing. They're there because they're meant to be followed so other people can enjoy the benefits of the already-posted solutions without having to ask for help for something that's already been covered in the forum, and so the volunteers who try to help people don't have to type the same solutions over and over.

[Bierhundt]