Problemi aggiornamenti  [Solved]

Forum italiano degli utenti MX
Forum rules
Post Reply
Message
Author
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Problemi aggiornamenti  [Solved]

#1 Post by diabolikos »

Buongiorno a tutti,
è qualche giorno che Discover non riesce a portare gli aggiornamenti proposti, postando errori di questo tipo:
E: https://dl.google.com/linux/chrome/deb stable InRelease is not (yet) available (Impossibile iniziare la connessione a dl.google.com:443 (2a00:1450:4002:414::200e). - connect (101: La rete non è raggiungibile) Impossibile connettersi a dl.google.com:443 (142.250.180.174). - connect (111: Connessione rifiutata))
E: https://mxrepo.com/mx/repo bookworm InRelease is not (yet) available (Impossibile connettersi a mxrepo.com:443 (70.40.214.183). - connect (111: Connessione rifiutata))
la macchina naviga e pinga l'esterno tranquillamente...

Provando a lanciare gli aggiornamenti da terminale, ottengo errori anche lì.
E: https://dl.google.com/linux/chrome/deb stable InRelease is not (yet) available (Impossibile iniziare la connessione a dl.google.com:443 (2a00:1450:4002:414::200e). - connect (101: La rete non è raggiungibile) Impossibile connettersi a dl.google.com:443 (142.250.180.174). - connect (111: Connessione rifiutata))
E: https://mxrepo.com/mx/repo bookworm InRelease is not (yet) available (Impossibile connettersi a mxrepo.com:443 (70.40.214.183). - connect (111: Connessione rifiutata))
Se c'è un errore di repo, credo sia dovuto all'upgrade di versione da 21.3 a 23.

Grazie a chi vorrà rispondere....
Top
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Re: Problemi aggiornamenti

#2 Post by diabolikos »

Update:
Richiesta in automatico di nuovi aggiornamenti:
E: https://mxrepo.com/mx/repo bookworm InRelease is not (yet) available (Impossibile connettersi a mxrepo.com:443 (70.40.214.183). - connect (111: Connessione rifiutata))
E: http://deb.debian.org/debian bookworm-updates InRelease is not (yet) available (Impossibile iniziare la connessione a debian.map.fastlydns.net:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile) Impossibile connettersi a debian.map.fastlydns.net:80 (151.101.242.132). - connect (111: Connessione rifiutata) Impossibile iniziare la connessione a deb.debian.org:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile))
E: http://deb.debian.org/debian bookworm InRelease is not (yet) available (Impossibile iniziare la connessione a deb.debian.org:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile))
E: https://dl.google.com/linux/chrome/deb stable InRelease is not (yet) available (Impossibile iniziare la connessione a dl.google.com:443 (2a00:1450:4002:403::200e). - connect (101: La rete non è raggiungibile) Impossibile connettersi a dl.google.com:443 (142.250.180.174). - connect (111: Connessione rifiutata))
E: http://deb.debian.org/debian bookworm-updates InRelease is not (yet) available (Impossibile iniziare la connessione a debian.map.fastlydns.net:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile) Impossibile connettersi a debian.map.fastlydns.net:80 (151.101.242.132). - connect (111: Connessione rifiutata) Impossibile iniziare la connessione a deb.debian.org:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile))
E: http://deb.debian.org/debian bookworm InRelease is not (yet) available (Impossibile iniziare la connessione a deb.debian.org:80 (2a04:4e42:39::644). - connect (101: La rete non è raggiungibile))
E: https://mxrepo.com/mx/repo bookworm InRelease is not (yet) available (Impossibile connettersi a mxrepo.com:443 (70.40.214.183). - connect (111: Connessione rifiutata))
Top
User avatar
Eadwine Rose
Administrator
Posts: 15244
Joined: Wed Jul 12, 2006 2:10 am

Re: Problemi aggiornamenti

#3 Post by Eadwine Rose »

Si prega di condividere le informazioni complete sul sistema rapido, grazie.
MX-23.6_x64 July 31 2023 * 6.1.0-39amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Top
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Re: Problemi aggiornamenti

#4 Post by diabolikos »

Eadwine Rose wrote: Fri Jan 12, 2024 8:09 am Si prega di condividere le informazioni complete sul sistema rapido, grazie.
Spero sia sufficiente questo:

Code: Select all

System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64 Libretto
    July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Vmware System: VMware product: VMware Virtual Platform v: N/A serial: <superuser required>
    Chassis: No Enclosure type: 1 serial: <superuser required>
  Mobo: Intel model: 440BX Desktop Reference Platform serial: <superuser required> BIOS: Phoenix
    v: 6.00 date: 11/12/2020
CPU:
  Info: model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64 type: MCP arch: Zen 3 gen: 4
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80)
    stepping: 0 microcode: 0xFFFFFFFF
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 1024 KiB desc: 2x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1996 min/max: N/A cores: 1: 1996 2: 1996 bogomips: 7984
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  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: retbleed status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
    empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:0f.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx 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: Virtual-1 mapped: Virtual1 res: 1920x1080 hz: 60 size: N/A modes: max: 1920x1080
    min: 640x480
  API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes
Audio:
  Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 v: kernel
    bus-ID: 02:03.0 chip-ID: 1274:1371 class-ID: 0401
  API: ALSA v: k6.1.0-10-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 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine type: network bridge
    driver: N/A modules: i2c_piix4 port: N/A bus-ID: 00:07.3 chip-ID: 8086:7113 class-ID: 0680
  Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000
    v: kernel port: 2000 bus-ID: 02:01.0 chip-ID: 8086:100f class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 50 GiB used: 420.43 GiB (840.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VMware model: Virtual SATA Hard Drive size: 50 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0001
    scheme: MBR
Partition:
  ID-1: / raw-size: 50 GiB size: 48.91 GiB (97.83%) used: 18.8 GiB (38.4%) 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: 2 GiB used: 1.52 GiB (75.8%) priority: -2 file: /swap/swap
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 3000 libs: 1693 tools: apt,apt-get,aptitude,nala,synaptic 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/brave-browser-release.list
    1: deb [arch=amd64] 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/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 309 Uptime: 6h 20m wakeups: 7487 Memory: 3.82 GiB used: 3.19 GiB (83.4%)
  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)
Top
User avatar
j2mcgreg
Global Moderator
Posts: 7198
Joined: Tue Oct 23, 2007 12:04 pm

Re: Problemi aggiornamenti

#5 Post by j2mcgreg »

Vai su MX Tools --> Repo Manager e cambia il tuo repository principale ad Alblasserdam, Paesi Bassi. Quindi disconnettiti/accedi e prova ad aggiornare nuovamente.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Re: Problemi aggiornamenti

#6 Post by diabolikos »

j2mcgreg wrote: Fri Jan 12, 2024 8:43 am Vai su MX Tools --> Repo Manager e cambia il tuo repository principale ad Alblasserdam, Paesi Bassi. Quindi disconnettiti/accedi e prova ad aggiornare nuovamente.
No, non ha funzionato. Lunedì al ritorno in ufficio potrò essere più preciso e fornire altri dettagli.
Top
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Re: Problemi aggiornamenti

#7 Post by diabolikos »

j2mcgreg wrote: Fri Jan 12, 2024 8:43 am Vai su MX Tools --> Repo Manager e cambia il tuo repository principale ad Alblasserdam, Paesi Bassi. Quindi disconnettiti/accedi e prova ad aggiornare nuovamente.
Fatto tentativo questa mattina... questo il risultato.
<html>Scaricamento del pacchetto non riuscito:<br/><br/>E: http://nl.mxrepo.com/mx/repo bookworm/main amd64 ddm-mx all 24.01.01 is not (yet) available (Impossibile iniziare la connessione a nl.mxrepo.com:80 (2a04:52c0:101:5f3::3658). - connect (101: La rete non è raggiungibile) Impossibile connettersi a nl.mxrepo.com:80 (5.2.64.114). - connect (111: Connessione rifiutata))
E: http://nl.mxrepo.com/mx/repo bookworm/main amd64 lo-main-helper all 24.01.4mx23 is not (yet) available (Impossibile iniziare la connessione a nl.mxrepo.com:80 (2a04:52c0:101:5f3::3658). - connect (101: La rete non è raggiungibile))
E: http://nl.mxrepo.com/mx/repo bookworm/main amd64 mx-packageinstaller-pkglist all 24.01.4mx23 is not (yet) available (Impossibile iniziare la connessione a nl.mxrepo.com:80 (2a04:52c0:101:5f3::3658). - connect (101: La rete non è raggiungibile))
E: http://nl.mxrepo.com/mx/repo bookworm/main amd64 mx-repo-list all 24.1 is not (yet) available (Impossibile iniziare la connessione a nl.mxrepo.com:80 (2a04:52c0:101:5f3::3658). - connect (101: La rete non è raggiungibile))
</html>
Top
diabolikos
Posts: 25
Joined: Thu Mar 23, 2023 10:07 am

Re: Problemi aggiornamenti

#8 Post by diabolikos »

Non erano allineati i repository con la nuova versione di Debian. Adesso tutto OK.
Top
Post Reply

Return to “Forum Italiano”