apt autoremove hangs at '('
Posted: Fri Feb 16, 2024 8:47 am
Hi guys!
I have a newer computer with MX21. However, today on my older computer with MX19, I ran an update and at the end it said the following:
apt autoremove libpango1.0-0 (1.42.4-8~deb10u1)
And it came back saying (essentially): Process halted, unexpected '('
I'm guessing that I should just run:
apt autoremove libpango1.0-0
apt autoremove libpangox-1.0-0
By themselves... But then I have to wonder, is it safe to do so? I mean, usually the specificity is important!
Also, I did try searching in the forum, and discovered other users where their somewhat similar problem has to do with old kernels, and header files listing, and de-listing. All very confusing. It seems like sometimes you have to use the command: apt purge xxxxx. I looked up MX Cleanup (mentioned there by Felix), and there are things in Cleanup involving kernels which I am frankly afraid to run, not knowing the full import of what i am doing.
So, any thoughts on this? Or should I do what one fellow suggested a long time ago: Just leave them be. These will pile up, but they're harmless!
And, as it happens, I can just forget about it these days, since in any case, I'll be installing MX 21 in a couple of months when MX 19 reaches its 'sell by' date, and maybe then on to MX 23. But if there is a simple, safe fix, I'll do it gladly!
Thanks...
And here's my Quick Info:
I have a newer computer with MX21. However, today on my older computer with MX19, I ran an update and at the end it said the following:
Well I'm not a power user, know little about linux, but this seemed simple enough, so I went into Yakuake and put in:The following packages were automatically installed and are no longer required:
libpango1.0-0 (1.42.4-8~deb10u1)
libpangox-1.0-0 (0.0.2-5+b2)
Use 'apt autoremove' to remove them.
apt autoremove libpango1.0-0 (1.42.4-8~deb10u1)
And it came back saying (essentially): Process halted, unexpected '('
I'm guessing that I should just run:
apt autoremove libpango1.0-0
apt autoremove libpangox-1.0-0
By themselves... But then I have to wonder, is it safe to do so? I mean, usually the specificity is important!
Also, I did try searching in the forum, and discovered other users where their somewhat similar problem has to do with old kernels, and header files listing, and de-listing. All very confusing. It seems like sometimes you have to use the command: apt purge xxxxx. I looked up MX Cleanup (mentioned there by Felix), and there are things in Cleanup involving kernels which I am frankly afraid to run, not knowing the full import of what i am doing.
So, any thoughts on this? Or should I do what one fellow suggested a long time ago: Just leave them be. These will pile up, but they're harmless!
And, as it happens, I can just forget about it these days, since in any case, I'll be installing MX 21 in a couple of months when MX 19 reaches its 'sell by' date, and maybe then on to MX 23. But if there is a simple, safe fix, I'll do it gladly!
Thanks...
And here's my Quick Info:
Code: Select all
System: Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma 5.14.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-19.4_kde_x64 patito feo March 31 2021
base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: TOSHIBA product: Satellite P770 v: PSBY1U-009005 serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: TOSHIBA model: PHRAA v: 1.00 serial: <filter> BIOS: TOSHIBA v: 2.20 date: 10/30/2012
Battery: ID-1: BAT1 charge: 0% condition: 7.1/48.6 Wh (14.6%) volts: 7.1 min: 10.8 model: COMPAL PABAS0241231 type: Li-ion
serial: <filter> status: Unknown
CPU: Info: Dual Core model: Intel Core i5-2410M bits: 64 type: MT MCP arch: Sandy Bridge family: 6 model-id: 2A (42)
stepping: 7 microcode: 2F cache: L2: 3 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18358
Speed: 2166 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 2166 2: 1924 3: 2131 4: 1888
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; 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: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Toshiba driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
Device-2: Alcor Micro type: USB driver: uvcvideo bus-ID: 1-1.4:3 chip-ID: 058f:b003 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: modesetting unloaded: fbdev,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.7x9.4") s-diag: 485mm (19.1")
Monitor-1: LVDS-1 res: 1600x900 hz: 60 dpi: 106 size: 382x215mm (15.0x8.5") diag: 438mm (17.3")
OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.3.5 compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Toshiba driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-5mx-amd64 running: yes
Sound Server-2: PulseAudio v: 12.2 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Toshiba driver: r8169 v: kernel port: e000
bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel modules: wl
port: e000 bus-ID: 03:00.0 chip-ID: 168c:002b class-ID: 0280
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 596.17 GiB used: 47.4 GiB (8.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS547564A9E384 size: 596.17 GiB block-size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: A60B scheme: MBR
Partition: ID-1: / raw-size: 19.92 GiB size: 19.48 GiB (97.80%) used: 11.24 GiB (57.7%) fs: ext4 dev: /dev/sda6 maj-min: 8:6
ID-2: /home raw-size: 194.15 GiB size: 190.1 GiB (97.91%) used: 36.16 GiB (19.0%) fs: ext4 dev: /dev/sda7
maj-min: 8:7
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 12.21 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda5 maj-min: 8:5
Sensors: System Temperatures: cpu: 61.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Packages: 2650 note: see --pkg apt: 2645 lib: 1543 flatpak: 5
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/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
2: deb http://mxrepo.com/mx/repo/ buster ahs
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 209 Uptime: 2h 5m wakeups: 3 Memory: 5.72 GiB used: 1.44 GiB (25.1%) Init: SysVinit v: 2.93 runlevel: 5
default: 5 tool: systemctl Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in default: Bash v: 5.0.3
running-in: quick-system-in inxi: 3.3.06