Page 1 of 1

SOLVED - Something is broken w. my repos. How to fix?

Posted: Wed Nov 20, 2024 5:19 pm
by Caesar2
My last update really loused the system up. Thanks.

Code: Select all

System:
  Kernel: 5.8.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.0-3-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 November 11 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx 
  serial: <filter> UEFI-[Legacy]: American Megatrends v: 3103 date: 06/17/2020 
CPU:
  Info: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ 
  family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D cache: L2: 3 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 83834 
  Speed: 2224 MHz min/max: 1550/3500 MHz boost: disabled Core speeds (MHz): 
  1: 2224 2: 2259 3: 2344 4: 3192 5: 2063 6: 2904 7: 2290 8: 3214 9: 1876 
  10: 2117 11: 2909 12: 2321 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  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 AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Gigabyte driver: nvidia 
  v: 525.125.06 bus-ID: 08:00.0 chip-ID: 10de:1d01 class-ID: 0300 
  Device-2: Logitech QuickCam Communicate Deluxe type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 3-2:2 chip-ID: 046d:0992 class-ID: 0102 
  serial: <filter> 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1680x1050 s-dpi: 90 s-size: 474x303mm (18.7x11.9") 
  s-diag: 563mm (22.1") 
  Monitor-1: DVI-D-0 res: 1680x1050 hz: 60 dpi: 90 size: 474x296mm (18.7x11.7") 
  diag: 559mm (22") 
  OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 525.125.06 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GP108 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 08:00.1 chip-ID: 10de:0fb8 
  class-ID: 0403 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403 
  Device-3: Logitech QuickCam Communicate Deluxe type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 3-2:2 chip-ID: 046d:0992 class-ID: 0102 
  serial: <filter> 
  Sound Server-1: ALSA v: k5.8.0-3-amd64 running: yes 
  Sound Server-2: PulseAudio v: 12.2 running: yes 
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
  port: e000 bus-ID: 03:00.0 chip-ID: 8086:1539 class-ID: 0200 
  IF: eth0 state: up speed: 100 Mbps duplex: half mac: <filter> 
Drives:
  Local Storage: total: 3.64 TiB used: 1.87 TiB (51.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD4005FZBX-00K5WB0 
  size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT 
Partition:
  ID-1: / raw-size: 74.35 GiB size: 72.69 GiB (97.76%) used: 62.06 GiB (85.4%) 
  fs: ext4 dev: /dev/sda2 maj-min: 8:2 
Swap:
  Alert: No swap data was found. 
Sensors:
  System Temperatures: cpu: 27.5 C mobo: N/A gpu: nvidia temp: 40 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 38% 
Repos:
  Packages: note: see --pkg apt: 2595 lib: 1439 flatpak: 0 
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/airvpn-stable.list 
  1: deb http://eddie.website/repository/apt/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.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 https://mirrors.aliyun.com/mxlinux/mx/repo/ buster main non-free
  2: deb https://mirrors.aliyun.com/mxlinux/mx/repo/ buster ahs
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
  1: deb [arch=all, signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian/ stable main
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 288 Uptime: 2d 19h 26m wakeups: 1 Memory: 15.62 GiB 
  used: 2.86 GiB (18.3%) 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 

Re: Something is broken w. my repos. How to fix?

Posted: Wed Nov 20, 2024 5:27 pm
by j2mcgreg

Code: Select all

Distro: MX-19.4_KDE_x64 patito feo November 11 2020 
  base: Debian GNU/Linux 10 (buster) 
MX 19 has been retired and it's no longer supported. Your best course of action is to back up your data, do a clean install of MX 23 and then restore your data from the backup.

Re: Something is broken w. my repos. How to fix?

Posted: Wed Nov 20, 2024 5:31 pm
by karlchen
Hello, Caesar2.

Code: Select all

System:
  Kernel: 5.8.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.0-3-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 November 11 2020 
  base: Debian GNU/Linux 10 (buster) 
You are using an obsolete MX Linux 19.4 system. MX Linux 19.4 reached the end of its supported life time in the middle of this year.
End of supported lifetime means: no more software updates from the official software repositories, no more bugfixes, no more security patches.

Very likely nothing is broken with your software repositories. The thing is that no-one is maintaining the MX 19.4 / Debian 10 software repositories any longer.

You should seriously consider switching from MX 19.4 to a still supported MX Linux release like e.g. MX Linux 23.4, which will be supported till 2028, if my memory serves me right. MX 21.3 might be an option as well, but it will be supported till 2026 only.

Regards,
Karl

Re: Something is broken w. my repos. How to fix?

Posted: Wed Nov 20, 2024 8:24 pm
by Stevo
I do wonder what on earth those updates were.

Re: Something is broken w. my repos. How to fix?

Posted: Wed Nov 20, 2024 8:35 pm
by Kermit the Frog
Stevo wrote: Wed Nov 20, 2024 8:24 pm I do wonder what on earth those updates were.
:rofl:

Re: SOLVED - Something is broken w. my repos. How to fix?

Posted: Thu Nov 21, 2024 5:14 am
by artytux
If Mx 19 still working maybe @Caesar2 could check update history and let stevo breathe

Re: SOLVED - Something is broken w. my repos. How to fix?

Posted: Wed Dec 04, 2024 10:59 pm
by Caesar2
MX won't boot any longer but I'll try a guess as to when I updated it last and say surely within the last six months. I'm also thinking it could have been a customized version.

Re: SOLVED - Something is broken w. my repos. How to fix?

Posted: Wed Dec 04, 2024 11:49 pm
by MXRobo
I do wonder if the guy in post #4 was being appropriately facetious.
Considering the following:
MX 19 has been retired and it's no longer supported....
End of supported lifetime means: no more software updates from the official software repositories....
Post #5
No "?" at end of first sentence.
-------------------------------------
P.S.
You should seriously consider switching from MX 19.4 to a still supported MX Linux release like e.g. MX Linux 23.4,....
Or just forget everything and wait until MX 49 comes out. :p

Regards, Good Luck

Re: SOLVED - Something is broken w. my repos. How to fix?

Posted: Thu Dec 05, 2024 2:47 pm
by Stevo
MXRobo wrote: Wed Dec 04, 2024 11:49 pm I do wonder if the guy in post #4 was being appropriately facetious.
Considering the following:
MX 19 has been retired and it's no longer supported....
End of supported lifetime means: no more software updates from the official software repositories....
Post #5
No "?" at end of first sentence.
-------------------------------------
P.S.
You should seriously consider switching from MX 19.4 to a still supported MX Linux release like e.g. MX Linux 23.4,....
Or just forget everything and wait until MX 49 comes out. :p

Regards, Good Luck
Well, if the prior updates were over six months ago, there could have been some security updates from Debian as well as the last updates we did for MX 19, but nothing should have broken the GUI...maybe one of those GRUB updates from Debian, though????????? (extra question marks to make up for missing ones)