Page 6 of 7
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 8:46 pm
by CharlesV
dolphin_oracle wrote: Tue Jul 15, 2025 5:53 pm
CharlesV wrote: Tue Jul 15, 2025 3:00 pm
The following is a list that appears to be everything that was removed from a users machine in an update ...
this topic.
viewtopic.php?p=825328#p825328
Code: Select all
foliate:all 2.6.4-1+dfsg3
mx-apps:all 24.05.01
formatusb:amd64 25.06.01
mugshot:all 0.4.3-1
gir1.2-gst-plugins-base-1.0:amd64 1.22.0-3+deb12u4
gufw:all 22.04.0-1
gir1.2-webkit2-4.0:amd64 2.48.3-1~deb12u1
strawberry:amd64 1.1.3-1~mx23+1
gstreamer1.0-plugins-bad:amd64 1.22.0-4+deb12u6
hardinfo2:amd64 2.2.7-0.1~mx23+1
js8call:amd64 2.2.0+ds-5
swell-foop:amd64 1:41.1-1
libclutter-gtk-1.0-0:amd64 1.8.4-4+b1
libclutter-1.0-0:amd64 1.26.4+dfsg-4
libcogl-pango20:amd64 1.22.8-3+b1
libcogl-path20:amd64 1.22.8-3+b1
libcogl20:amd64 1.22.8-3+b1
xfdesktop4:amd64 4.20.0-1~mx23+2
yelp:amd64 42.2-1+deb12u1
libyelp0:amd64 42.2-1+deb12u1
network-manager-openconnect-gnome:amd64 1.2.8-3+deb12u1
libwebkit2gtk-4.0-37:amd64 2.48.3-1~deb12u1
libqt5multimedia5-plugins:amd64 5.15.8-2
libqt5multimediagsttools5:amd64 5.15.8-2
mx-boot-options:amd64 25.6
uefi-manager:amd64 25.6.01
mx-system:all 25.04.03mx23
qt6gtk2:amd64 0.4-1~mx23
mx-user:amd64 25.5.02
mx-snapshot:amd64 25.6.01
mx-viewer:amd64 25.7
libqt6webenginewidgets6:amd64 6.4.2-final+dfsg-1
libqt6webenginecore6-bin:amd64 6.4.2-final+dfsg-1
libqt6webenginecore6:amd64 6.4.2-final+dfsg-1
libqt6printsupport6:amd64 6.4.2+dfsg-10
libqt6quickwidgets6:amd64 6.4.2+dfsg-1
libqt6svg6:amd64 6.4.2-2
mx-repo-manager:amd64 25.5.01
mesa-utils:amd64 8.5.0-1
mesa-utils-bin:amd64 8.5.0-1
mx-bootrepair:amd64 25.6
mx-cleanup:amd64 25.7
mx-live-usb-maker:amd64 25.6
mx-remastercc:amd64 25.6.01
qt6-gtk-platformtheme:amd64 6.4.2+dfsg-10
xorg:amd64 1:7.7+23
xserver-xorg:amd64 1:7.7+23
virtualbox-guest-x11:amd64 7.0.22-0.1~mx23+1
vlc:amd64 3.0.21-0+deb12u1
vlc-plugin-video-output:amd64 3.0.21-0+deb12u1
xserver-xorg-video-all:amd64 1:7.7+23
xserver-xorg-video-vmware:amd64 1:13.3.0-3.1+b1
xserver-xorg-video-vesa:amd64 1:2.5.0-1+b1
xserver-xorg-input-all:amd64 1:7.7+23
xserver-xorg-input-libinput:amd64 1.2.1-1+b1
xserver-xorg-video-trident:amd64 1:1.4.0-1
xserver-xorg-video-tdfx:amd64 1:1.5.0-5
xserver-xorg-input-joystick:amd64 1:1.6.3-1.1
xserver-xorg-input-wacom:amd64 1.1.0-1
xserver-xorg-video-amdgpu:amd64 23.0.0-1
xserver-xorg-video-ati:amd64 1:19.1.0-3
xserver-xorg-video-cirrus:amd64 1:1.5.3-1+b5
xserver-xorg-video-fbdev:amd64 1:0.5.0-2
xserver-xorg-video-intel:amd64 2:2.99.917+git20210115-1
xserver-xorg-video-mach64:amd64 6.9.7-1
xserver-xorg-video-mga:amd64 1:2.0.0-1+b1
xserver-xorg-video-neomagic:amd64 1:1.3.0-2+b2
xserver-xorg-video-nouveau:amd64 1:1.0.17-2
xserver-xorg-video-qxl:amd64 0.1.5+git20200331-3
xserver-xorg-video-r128:amd64 6.12.1-1
xserver-xorg-video-radeon:amd64 1:19.1.0-3
xserver-xorg-video-savage:amd64 1:2.3.9-5
xserver-xorg-video-siliconmotion:amd64 1:1.7.9-4
xserver-xorg-video-sisusb:amd64 1:0.9.7-3
libqt6quick6:amd64 6.4.2+dfsg-1
libqt6opengl6:amd64 6.4.2+dfsg-10
xserver-xorg-core:amd64 2:21.1.7-3+deb12u10
tumbler:amd64 4.20.0-1~mx23+1
mx-packageinstaller:amd64 25.7
mx-packageinstaller-pkglist:all 25.07.03mx23
tumbler-plugins-extra:amd64 4.20.0-1~mx23+1
libgepub-0.7-0:amd64 0.7.0-2
libwebkit2gtk-4.1-0:amd64 2.48.3-1~deb12u1
libgstreamer-plugins-bad1.0-0:amd64 1.22.0-4+deb12u6
libqt6widgets6:amd64 6.4.2+dfsg-10
libgstreamer-gl1.0-0:amd64 1.22.0-3+deb12u4
libqt6gui6:amd64 6.4.2+dfsg-10
in this case
Code: Select all
sudo apt install foliate mx-apps formatusb mugshot gir1.2-gst-plugins-base-1.0 gufw gir1.2-webkit2-4.0 strawberry gstreamer1.0-plugins-bad hardinfo2 js8call swell-foop libclutter-gtk-1.0-0 libclutter-1.0-0 libcogl-pango20 libcogl-path20 libcogl20 xfdesktop4 yelp libyelp0 network-manager-openconnect-gnome libwebkit2gtk-4.0-37 libqt5multimedia5-plugins libqt5multimediagsttools5 mx-boot-options uefi-manager mx-system qt6gtk2 mx-user mx-snapshot mx-viewer libqt6webenginewidgets6 libqt6webenginecore6-bin libqt6webenginecore6 libqt6printsupport6 libqt6quickwidgets6 libqt6svg6 mx-repo-manager mesa-utils mesa-utils-bin mx-bootrepair mx-cleanup mx-live-usb-maker mx-remastercc qt6-gtk-platformtheme xorg xserver-xorg virtualbox-guest-x11 vlc vlc-plugin-video-output xserver-xorg-video-all xserver-xorg-video-vmware xserver-xorg-video-vesa xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-trident xserver-xorg-video-tdfx xserver-xorg-input-joystick xserver-xorg-input-wacom xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga xserver-xorg-video-neomagic xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-r128 xserver-xorg-video-radeon xserver-xorg-video-savage xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb libqt6quick6 libqt6opengl6 xserver-xorg-core tumbler mx-packageinstaller mx-packageinstaller-pkglist tumbler-plugins-extra libgepub-0.7-0 libwebkit2gtk-4.1-0 libgstreamer-plugins-bad1.0-0 libqt6widgets6 libgstreamer-gl1.0-0 libqt6gui6
would bring all that back.
Thank you !
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 8:48 pm
by CharlesV
kd4e wrote: Tue Jul 15, 2025 7:47 pm
Adrian wrote: Tue Jul 15, 2025 7:16 pm
m_pav wrote: Tue Jul 15, 2025 7:12 pm
In a terminally broken system (pun intended), it might be necessary to have an active wired LAN connection up and running before doing any of this, then test it with
followed by Adrians recommendation above when the connection is confirmed.
Sometimes a "dhclient" is enough to get an IP address, but it depends on specifics.
Nope. So, I went back in and ran "sudo apt update" then the long string - it completed without error.
However, when I rebooted from the ssd I was brought to the same login prompt.
odd-login-prompt-1.jpg
Should I choose the repair option at what I believe is the grub menu?
NOTE 1: This is 23.6 *not* AHS and *not* systemd, if that's relevant at all.
NOTE 2: Mea Culpa ... I just realized I was entering the wrong User at the odd login prompt. It's now allowed me to log in. When I try to get to the GUI - "startx" errors: /etc/X11/xinit/xserverrc: 3: exec: /usr/bin/X: not found.
NOTE 3: From what I'm reading I may need to reinstall xorg? Does this look right?
Code: Select all
sudo apt install xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-mouse xserver-xorg-input-evdev xserver-xorg-input-kbd
Some of those package were in the things that were removed and should have been reinstalled with the previous command. I dont believe it can hurt to try though .
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 9:18 pm
by kd4e
It's unclear to me why this is failing ...
xorg-fail-1.jpg
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 9:49 pm
by dolphin_oracle
kd4e wrote: Tue Jul 15, 2025 9:18 pm
It's unclear to me why this is failing ...
xorg-fail-1.jpg
X isn't installed.
give
a try. might get you further.
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 10:01 pm
by kd4e
That was the last piece - all good now.
Thanks!
You guys are just amazing!
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Tue Jul 15, 2025 11:50 pm
by CharlesV
kd4e wrote: Tue Jul 15, 2025 10:01 pm
That was the last piece - all good now.
Thanks!
You guys are just amazing!
Excellent! Glad your back up !!
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Wed Jul 16, 2025 5:41 am
by operadude
A bit nervous...Has this issue been fixed?
Got a message on my KDE install that there are 9 updates, all of which are listed in the previously-posted list of problematic updates. Well, not exactly; you'll see the minor, but I'm hoping, critical, difference:
Code: Select all
libegl-mesa0
libgbm1
libgl1-mesa-dri
libglx-mesa0
libxatracker2
mesa-libgallium
mesa-va-drivers
mesa-vdpau-drivers
mesa-vulkan-drivers
They all show the proposed upgrade as:
25.0.4-1~mx23ahs -> 25.0.4-1~mx23ahs+1
The previous post showing the proposed updates were to upgrade to:
Now, my updater in KDE (Discover) says it wants to upgrade to:
Can I assume that I am safe to upgrade?
And, yes,
@CharlesV, I DO HAVE a Timeshift Snapshot (I do weekly). I also have an MX-Snapshot from "...The 4th of July !!!..." (Sung to the tune of "Yankee Doodle Dandy").
Signed,
Nervous Nelly
P.S. Almost Forgot!:
Code: Select all
Snapshot created on: 20250704_1401
System:
Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
v: F5 date: 04/24/2017
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF8
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: indirect_target_selection status: Not affected
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: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 39.0 C
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
min: 640x480
API: OpenGL v: 4.5 Mesa 25.0.4-1~mx23ahs renderer: OLAND (radeonsi ACO DRM 2.50 6.1.0-37-amd64)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
API: ALSA v: k6.1.0-37-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
IF-ID-2: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 7.27 TiB used: 5.49 TiB (75.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 1B2QEXE7 temp: 30.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: CC25 scheme: GPT
Partition:
ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 15.32 GiB (62.7%) fs: ext4
dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.8 MiB (0.7%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.96 GiB (44.8%) fs: ext4
dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p10
maj-min: 259:10
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: radeon temp: 40.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 3077 libs: 1526 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 0
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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
2: deb https://mxrepo.com/mx/repo/ bookworm ahs
No active apt repos in: /etc/apt/sources.list.d/skype-stable.list
Info:
Processes: 253 Uptime: 48m wakeups: 3 Memory: 31.3 GiB used: 3.21 GiB (10.3%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Wed Jul 16, 2025 6:39 am
by dolphin_oracle
operadude wrote: Wed Jul 16, 2025 5:41 am
A bit nervous...Has this issue been fixed?
Got a message on my KDE install that there are 9 updates, all of which are listed in the previously-posted list of problematic updates. Well, not exactly; you'll see the minor, but I'm hoping, critical, difference:
Code: Select all
libegl-mesa0
libgbm1
libgl1-mesa-dri
libglx-mesa0
libxatracker2
mesa-libgallium
mesa-va-drivers
mesa-vdpau-drivers
mesa-vulkan-drivers
They all show the proposed upgrade as:
25.0.4-1~mx23ahs -> 25.0.4-1~mx23ahs+1
The previous post showing the proposed updates were to upgrade to:
Now, my updater in KDE (Discover) says it wants to upgrade to:
Can I assume that I am safe to upgrade?
And, yes, @CharlesV, I DO HAVE a Timeshift Snapshot (I do weekly). I also have an MX-Snapshot from "...The 4th of July !!!..." (Sung to the tune of "Yankee Doodle Dandy").
Signed,
Nervous Nelly
P.S. Almost Forgot!:
Code: Select all
Snapshot created on: 20250704_1401
System:
Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
v: F5 date: 04/24/2017
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF8
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: indirect_target_selection status: Not affected
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: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 39.0 C
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
min: 640x480
API: OpenGL v: 4.5 Mesa 25.0.4-1~mx23ahs renderer: OLAND (radeonsi ACO DRM 2.50 6.1.0-37-amd64)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
API: ALSA v: k6.1.0-37-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
IF-ID-2: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 7.27 TiB used: 5.49 TiB (75.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 1B2QEXE7 temp: 30.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: CC25 scheme: GPT
Partition:
ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 15.32 GiB (62.7%) fs: ext4
dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.8 MiB (0.7%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.96 GiB (44.8%) fs: ext4
dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p10
maj-min: 259:10
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: radeon temp: 40.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 3077 libs: 1526 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 0
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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
2: deb https://mxrepo.com/mx/repo/ bookworm ahs
No active apt repos in: /etc/apt/sources.list.d/skype-stable.list
Info:
Processes: 253 Uptime: 48m wakeups: 3 Memory: 31.3 GiB used: 3.21 GiB (10.3%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Those are the fixed mess packages so should be ok.
Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Wed Jul 16, 2025 7:06 am
by operadude
@dolphin_oracle Thank You
EDIT:
Marking as "SOLVED"...
Woops: Not my Thread

Re: Urgent warning! Repo broken DO NOT UPDATE
Posted: Wed Jul 16, 2025 8:09 am
by m_pav
Thread marked as solved, a good team effort. I selected Timb4cqs post because I had to choose one that best reflected that things were OK now.