Discrepancy in upgradeable package results between MXPI_EnabledRepos and MX Updater [Solved]

[retroD0d0]

How do's All! Hope everyone is tossing and turning at night in anticipation of MX25.

I wanted to report an anomaly (bug?) I have experienced now and in the past. A discrepancy in the upgradeable package list between Enabled Repos in MXPI and MX Updater. In the screenshot, you can see (despite refreshing) MXPI fails to detect the latest Service-Manager patch.

I'm guessing the fact MX updater refreshes it's lists with 'apt update' and MXPI uses 'sudo apt-get update' has something to do with it.

I asked AI, it reckons it's because 'apt update' can read phased updates (whatever that means).

Anyone experienced this issue. I have recreated the phenomenon across two MX23 installations. The QSI of my present desktop below.

Code: Select all

Snapshot created on: 20250530_0142
System:
  Kernel: 5.10.230-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.230-antix.1-amd64-smp root=UUID=<filter> ro quiet
    splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto May 19  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: M4A78-VM v: Rev X.0x serial: <superuser required>
    BIOS: American Megatrends v: 0601 date: 04/08/2009
CPU:
  Info: model: AMD Phenom II X2 545 bits: 64 type: MCP arch: K10 level: v1 built: 2009-13
    process: AMD 45nm family: 0x10 (16) model-id: 4 stepping: 2 microcode: 0x10000DB
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 256 KiB desc: d-2x64 KiB; i-2x64 KiB
    L2: 1024 KiB desc: 2x512 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3000 boost: disabled scaling: driver: acpi-cpufreq
    governor: schedutil cores: 1: 800 2: 800 bogomips: 12034
  Flags: ht lm nx pae sse sse2 sse3 sse4a svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Caicos PRO [Radeon HD 7450] vendor: PC Partner / Sapphire driver: radeon v: kernel
    arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm built: 2009-15 pcie: gen: 2 speed: 5 GT/s
    lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:677b
    class-ID: 0300 temp: 36.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Sony TV serial: <filter> built: 2010 res: 1920x1080
    hz: 60 dpi: 30 gamma: 1.2 size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: AMD CAICOS (DRM 2.50.0 / 5.10.230-antix.1-amd64-smp
    LLVM 15.0.6) direct-render: Yes
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:14.2
    chip-ID: 1002:4383 class-ID: 0403
  Device-2: AMD Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM R5 230/235/235X OEM]
    vendor: PC Partner / Sapphire driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aa98 class-ID: 0403
  API: ALSA v: k5.10.230-antix.1-amd64-smp 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e800 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros AR922X Wireless Network Adapter driver: ath9k v: kernel modules: wl
    bus-ID: 04:07.0 chip-ID: 168c:0029 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 223.57 GiB used: 140.08 GiB (62.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: Q300. size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 12.3 scheme: MBR
Partition:
  ID-1: / raw-size: 223.57 GiB size: 219 GiB (97.96%) used: 140.08 GiB (64.0%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 37.0 C gpu: radeon temp: 36.0 C
  Fan Speeds (RPM): cpu: 1159 psu: 0 case-1: 1232
  Power: 12v: 12.16 5v: N/A 3.3v: 3.23 vbat: N/A
Repos:
  Packages: 2096 pm: dpkg pkgs: 2084 libs: 1018 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  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/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://ftp.saix.net/pub/linux/distributions/mxlinux/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
    1: deb https://download.onlyoffice.com/repo/debian/ squeeze main
  No active apt repos in: /etc/apt/sources.list.d/vscodium.list
Info:
  Processes: 193 Uptime: 42m wakeups: 1 Memory: 7.76 GiB used: 1.85 GiB (23.8%) 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: BIOS (legacy, CSM, MBR)

[dolphin_oracle]

at the moment I cannot duplicate this, but that doesn't mean it can't happen. there is a lot of things that can be going on.

so what happens if you simulate an upgrade (this won't make any changes).

Code: Select all

sudo apt full-upgrade -s

[siamhie]

No discrepancy.
mx-service-manager is listed under the MX Test Repo tab and not under the Enabled Repo tab.

msm.png

[dolphin_oracle]

No discrepancy.
mx-service-manager is listed under the MX Test Repo tab and not under the Enabled Repo tab.


msm.png

it shouldn't be. its not for me, and the OP doesn't appear to have the test repo enabled.


edit @siamhie actually your image is just showing it installed, which would be correct. any upgrade would be in the "enabled" tab though. also the repo version should be displayed there.

[siamhie]

No discrepancy.
mx-service-manager is listed under the MX Test Repo tab and not under the Enabled Repo tab.


msm.png

it shouldn't be. its not for me, and the OP doesn't appear to have the test repo enabled.


edit @siamhie actually your image is just showing it installed, which would be correct. any upgrade would be in the "enabled" tab though. also the repo version should be displayed there.

Can MX Updater pick up the test repo if the user went to the test repo tab while having MXPI open?

[dolphin_oracle]

No discrepancy.
mx-service-manager is listed under the MX Test Repo tab and not under the Enabled Repo tab.


msm.png

it shouldn't be. its not for me, and the OP doesn't appear to have the test repo enabled.


edit @siamhie actually your image is just showing it installed, which would be correct. any upgrade would be in the "enabled" tab though. also the repo version should be displayed there.

Can MX Updater pick up the test repo if the user went to the test repo tab while having MXPI open?

yes, but mx-service-manager is not in the test repo.

[siamhie]

edit @siamhie actually your image is just showing it installed, which would be correct. any upgrade would be in the "enabled" tab though. also the repo version should be displayed there.

That's because I installed the latest version from this thread. viewtopic.php?p=829140#p829140

[siamhie]

Can MX Updater pick up the test repo if the user went to the test repo tab while having MXPI open?

yes, but mx-service-manager is not in the test repo.

Gotcha.

[dolphin_oracle]

maybe more likely is that the ftp.saix.net repo is so slow that mx-packageinstaller's downloading of the lists is not complete. I've been trying manually and I've gotten multiple partial downloads.

I don't quite remember how the information is populated.

[fehlix]

I wanted to report an anomaly (bug?) I have experienced now and in the past. A discrepancy in the upgradeable package list between Enabled Repos in MXPI and MX Updater. In the screenshot, you can see (despite refreshing) MXPI fails to detect the latest Service-Manager patch.

Thanks for the report.

I'm guessing the fact MX updater refreshes it's lists with 'apt update' and MXPI uses 'sudo apt-get update' has something to do with it.

You guessed probaly wrongly.

I asked AI, it reckons it's because 'apt update' can read phased updates (whatever that means).

Smart, but "phased updates" is not utilized (yet ) in Debian, that is an Ubuntu thing. So maybe the answer you got is not applicable for Debian and MX Linux.

OK, and yes, I can reproduce this issue:
Here booted on fresh ISO MX-23.6_August_x64.iso
apt update show me 13 packages are available for upgrade:

Code: Select all

sudo apt update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease      
Hit:3 http://deb.debian.org/debian bookworm InRelease                              
Hit:4 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo bookworm InRelease
Reading package lists... Done                                
Building dependency tree... Done
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.

And here what MX Updater gives me:
The hint "bubble" on the icon, with the same number

mx-updater-icon-hint.jpg

The MX Update "View and Upgrade" window show also the same number of available upgrades:

mx-updater-full-upgrade.jpg

Or for better readability the text of the MX Updater in "View and Upgrade" window:

Code: Select all

  full upgrade
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Calculating upgrade...
  The following packages will be upgraded:
     firefox (141.0.3~mozillabinaries-1mx23+1 => 142.0~mozillabinaries-1mx23+1)
     gir1.2-javascriptcoregtk-4.0 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     gir1.2-webkit2-4.0 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     libjavascriptcoregtk-4.0-18 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     libjavascriptcoregtk-4.1-0 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     libwebkit2gtk-4.0-37 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     libwebkit2gtk-4.1-0 (2.48.3-1~deb12u1 => 2.48.5-1~deb12u1)
     libxslt1.1 (1.1.35-1+deb12u1 => 1.1.35-1+deb12u2)
     live-kernel-updater (0.2.30+5 => 0.2.30+6)
     mx-conky (25.08.1 => 25.08.2)
     mx-repo-manager (25.5.01 => 25.08)
     mx-service-manager (25.8 => 25.08.06)
     mx-system (25.04.03mx23 => 25.08.01mx23)
  13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 140 MB of archives.
  After this operation, 2,053 kB of additional disk space will be used.

And also the apt list --upgradable command run in the terminal show exactly the same number:

apt_lits_upgradable.jpg

Here for better readability as text,
apt list --upgradable show this:

Code: Select all

apt -qq list --upgradable 
firefox/mx 142.0~mozillabinaries-1mx23+1 amd64 [upgradable from: 141.0.3~mozillabinaries-1mx23+1]
gir1.2-javascriptcoregtk-4.0/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
gir1.2-webkit2-4.0/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
libjavascriptcoregtk-4.0-18/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
libjavascriptcoregtk-4.1-0/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
libwebkit2gtk-4.0-37/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
libwebkit2gtk-4.1-0/oldstable-security 2.48.5-1~deb12u1 amd64 [upgradable from: 2.48.3-1~deb12u1]
libxslt1.1/oldstable-security 1.1.35-1+deb12u2 amd64 [upgradable from: 1.1.35-1+deb12u1]
live-kernel-updater/mx,mx 0.2.30+6 all [upgradable from: 0.2.30+5]
mx-conky/mx 25.08.2 amd64 [upgradable from: 25.08.1]
mx-repo-manager/mx 25.08 amd64 [upgradable from: 25.5.01]
mx-service-manager/mx 25.08.06 amd64 [upgradable from: 25.8]
mx-system/mx,mx 25.08.01mx23 all [upgradable from: 25.04.03mx23]
demo@mx1:~/Desktop
$ apt -qq list --upgradable 2>/dev/null | wc -l
13

Now, let see what MXPI tells us.
After starting within "Enabled Repos" tabs it shows 7 upgrades available:

mxpi-list-upgradable-before-refresh-list.jpg

OK, now maybe let's refresh (Click on Refresh list) :

mxpi-list-upgradable.jpg

Now we are a bit closer, 12 upgrades available, but still something missing b/c apt told us we have 13.
So, I guess something related with the way MXPI detects and counts upgrades available.