MX Update manager says it can't connect to the network
MX Update manager says it can't connect to the network
It pops up when I start MX and says there are updates available. When I click on View and then Update All, it says "No Network Connection Available.." However, it is mistaken because I am able to get to this forum and post. Is this a bug everybody is getting or just me?
Its always worked before.
Its always worked before.
Re: MX Update manager says it can't connect to the network
Just messing around, I tried the command line:
>sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
bridge-utils libappstream-glib8 libatk1.0-0:i386 libaudclient2 libboost-log1.74.0 libboost-program-options1.74.0
libboost-regex1.74.0 libcmis-0.5-5v5 libfaudio0 libfaudio0:i386 libgee-0.8-2 libircclient1 liblxc1 libmpg123-0:i386 libmwaw-0.3-3
libnumbertext-1.0-0 libnumbertext-data libopenal1:i386 liborcus-0.16-0 liborcus-parser-0.16-0 libpango1.0-0 libpoppler102:i386
libqrcodegencpp1 libreoffice-kf5 libreoffice-plasma libreoffice-qt5 libsdbus-c++0 libsdl2-image-2.0-0 libsndio7.0:i386 libstb0
libstb0:i386 libvkd3d-shader1:i386 libvkd3d1 libvkd3d1:i386 libwine libwine:i386 libxmmsclient6 libxnvctrl0 lxc wine-gecko2.47.2
wine-gecko2.47.2:i386 wine-staging-i386:i386
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
bind9-dnsutils bind9-host mlocate network-manager-openconnect openconnect
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Why is it keeping 5 packages behind? They sound like they might be important.
>sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
bridge-utils libappstream-glib8 libatk1.0-0:i386 libaudclient2 libboost-log1.74.0 libboost-program-options1.74.0
libboost-regex1.74.0 libcmis-0.5-5v5 libfaudio0 libfaudio0:i386 libgee-0.8-2 libircclient1 liblxc1 libmpg123-0:i386 libmwaw-0.3-3
libnumbertext-1.0-0 libnumbertext-data libopenal1:i386 liborcus-0.16-0 liborcus-parser-0.16-0 libpango1.0-0 libpoppler102:i386
libqrcodegencpp1 libreoffice-kf5 libreoffice-plasma libreoffice-qt5 libsdbus-c++0 libsdl2-image-2.0-0 libsndio7.0:i386 libstb0
libstb0:i386 libvkd3d-shader1:i386 libvkd3d1 libvkd3d1:i386 libwine libwine:i386 libxmmsclient6 libxnvctrl0 lxc wine-gecko2.47.2
wine-gecko2.47.2:i386 wine-staging-i386:i386
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
bind9-dnsutils bind9-host mlocate network-manager-openconnect openconnect
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Why is it keeping 5 packages behind? They sound like they might be important.
Re: MX Update manager says it can't connect to the network
We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Forum Rules
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.
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.
Re: MX Update manager says it can't connect to the network
Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: MX Update manager says it can't connect to the network
See Below:
Code: Select all
System: Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.3_KDE_x64 Wildflower January 15 2023
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: AZW model: SEi v: V1.0 serial: <filter>
UEFI: American Megatrends LLC. v: TL55T201 date: 06/30/2022
CPU: Info: Quad Core model: 11th Gen Intel Core i5-11320H bits: 64 type: MT MCP
arch: Tiger Lake family: 6 model-id: 8C (140) stepping: 2 microcode: 34 cache:
L2: 8 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 50995
Speed: 814 MHz min/max: 400/4500 MHz Core speeds (MHz): 1: 814 2: 934 3: 3200 4: 3200
5: 3200 6: 3200 7: 1200 8: 3200
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 mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.5x10.9")
s-diag: 523mm (20.6")
Monitor-1: HDMI-1 res: 1680x1050 hz: 60 dpi: 90 size: 474x296mm (18.7x11.7")
diag: 559mm (22")
OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 22.0.5
direct render: Yes
Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403
Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel modules: wl port: 4000
bus-ID: 00:14.3 chip-ID: 8086:a0f0 class-ID: 0280
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
v: kernel port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 3-10:9 chip-ID: 8087:0026
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 200f hci-v: 5.2 rev: 200f
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept
service-classes: rendering, capturing, object transfer, audio
Drives: Local Storage: total: 1.38 TiB used: 376.2 GiB (26.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8SEP4512N-A0
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4
type: SSD serial: <filter> rev: SBM01100 temp: 41.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 04RL scheme: MBR
Partition: ID-1: / raw-size: 468.68 GiB size: 460.25 GiB (98.20%) used: 27.32 GiB (5.9%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 282 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors: System Temperatures: cpu: 47.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Packages: 2740 note: see --pkg apt: 2733 lib: 1606 flatpak: 7
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/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/winehq-bullseye.sources
1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bullseye main
Info: Processes: 249 Uptime: 1h 11m wakeups: 0 Memory: 15.41 GiB used: 2.54 GiB (16.5%)
Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A alt: 10
Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: UEFI
Re: MX Update manager says it can't connect to the network
Does it show the same, when you click on the MX Updater icon within the systray?n4mwd wrote: Mon Jul 22, 2024 6:33 pm It pops up when I start MX and says there are updates available. When I click on View and then Update All, it says "No Network Connection Available.." However, it is mistaken because I am able to get to this forum and post. Is this a bug everybody is getting or just me?
Its always worked before.
Re: MX Update manager says it can't connect to the network
[/quote]
Does it show the same, when you click on the MX Updater icon within the systray?
[/quote]
Yes. However, it is no longer in the systray now that I have run >sudo apt upgrade
Apparently the apt program doesn't suffer from the same affliction. However, it does report 5 apps that it held back.
When I go to the Start->SYSTEM->DISCOVER it says "Cannot refresh cache whilst offline". Discover is the MX updater.
Does it show the same, when you click on the MX Updater icon within the systray?
[/quote]
Yes. However, it is no longer in the systray now that I have run >sudo apt upgrade
Apparently the apt program doesn't suffer from the same affliction. However, it does report 5 apps that it held back.
When I go to the Start->SYSTEM->DISCOVER it says "Cannot refresh cache whilst offline". Discover is the MX updater.
Re: MX Update manager says it can't connect to the network
Ahh, sorry you should have mentioned discover, which is not the same as "MX Updater".n4mwd wrote: Mon Jul 22, 2024 7:52 pmYes. However, it is no longer in the systray now that I have run >sudo apt upgradeDoes it show the same, when you click on the MX Updater icon within the systray?
Apparently the apt program doesn't suffer from the same affliction. However, it does report 5 apps that it held back.
When I go to the Start->SYSTEM->DISCOVER it says "Cannot refresh cache whilst offline". Discover is the MX updater.
Can't help with Discover, maybe it was a bit buggy in MX-21.
Re: MX Update manager says it can't connect to the network
We have also seen kernel 6.0.0 be rather strange and cause weird issues in various places, possibly changing to a higher version kernel might resolve this. (I would suggest checking out a 6.6.x liquorix kernel - simple to install and test, simple to roll back if it doesnt help.)
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: MX Update manager says it can't connect to the network
It was working fine before, however, it apparently left me on an older version of MX while the rest of the world moved on.CharlesV wrote: Mon Jul 22, 2024 8:11 pm We have also seen kernel 6.0.0 be rather strange and cause weird issues in various places, possibly changing to a higher version kernel might resolve this. (I would suggest checking out a 6.6.x liquorix kernel - simple to install and test, simple to roll back if it doesnt help.)
Could you point me to the "simple" instructions on how to upgrade my kernel and revert it if I don't like it? I would like to upgrade to the latest stable MX if I can do it risk free, Obviously the updater isn't going to do it.