Page 1 of 1

"NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:18 pm
by AcsPrime
Hello,

I recently installed gcc10 and also cmake 3.16.
After this I rebooted and since then I get "NetworkManager is not running" when I over the Network manager icon.

I have done the following: sudo service networking start

I get: [ ok ]Configuring network interfaces in background... done.

And that when I hover the Network Manager icon I get: Networking disable.

I've tried googling for this but I only find WIFI related stuf.
How can I fix this? Before this big update I did do get gcc10 everything was working fine.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:25 pm
by dolphin_oracle
I presume you did a absolutely huge "update" from bullseye.

it more than likely broke some things in sysVinit when you did.

it is very possible the init script has been disabled. you can try

Code: Select all

sudo update-rc.d network-manager defaults
and see if that fixes anything. it won't if the /etc/NetworkManager script is missing.

other wise you can try putting

Code: Select all

/sbin/NetworkManager
in your /etc/rc.local file.


issues like this are why we don't support direct updates between major debian releases.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:47 pm
by AcsPrime
YES!!
Running /sbin/NetworkManager worked.
I did get an error when I tried running: sudo update-rc.d network-manager defaults
I got: update-rc.d: error: initscript does not exist: /etc/init.d/network-manager <-- is this bad?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:50 pm
by dolphin_oracle
it means you have the bullseye edition of network-manager. They removed the init script in bullseye. I actually wondered if an update would remove the script or not, it shouldn't have, but I guess their update is aggressive.

they aren't done either. I found that many init scripts get disabled out right in debian bullseye because they have neutered an app called "start-stop-daemon" that a lot of init scripts used.

everything will probably work if you switch to systemd booting. probably.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:52 pm
by AcsPrime
I didn't know I switched anything.
How can I switch to that?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:53 pm
by dolphin_oracle
it probably happened when you installed gcc10.

updating one of the core components of debian linux is not for the faint of heart.

Code: Select all

apt-history
will show what all got updated.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 3:59 pm
by AcsPrime
This is what I get when I try that out:
root@mx:~# apt-history
bash: apt-history: command not found
root@mx:~# apt history
E: Invalid operation history
root@mx:~#

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 4:06 pm
by dolphin_oracle
oh, right, debian removes python2, so apt-notifier (the parent package for apt-history) is probably gone too.... its in the middle of being updated for python3 now, but its not available yet.

you can try opening /var/log/apt/history.log in a text editor.


**edit* good info here are package update logs. https://www.linuxuprising.com/2019/01/h ... alled.html

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 4:10 pm
by AcsPrime
Here is what I updated:

Code: Select all

Start-Date: 2021-02-17  19:27:48
Commandline: apt install gcc
Requested-By: acs (1000)
Install: libx265-192:amd64 (3.4-2, automatic), libqpdf28:amd64 (10.1.0-1, automatic), librabbitmq4:amd64 (0.10.0-1, automatic), gir1.2-nm-1.0:amd64 (1.28.0-2+b1, automatic), liblist-moreutils-xs-perl:amd64 (0.430-2, automatic), libpython3.9-minimal:amd64 (3.9.1-4, automatic), python3-xapian:amd64 (1.4.18-1, automatic), libpython3.9-stdlib:amd64 (3.9.1-4, automatic), gcc-10-base:i386 (10.2.1-6, automatic), libraw20:amd64 (0.20.2-1, automatic), libpocketsphinx3:amd64 (0.8+5prealpha+1-13, automatic), libcdio19:amd64 (2.1.0-2, automatic), libicu67:amd64 (67.1-6, automatic), perl-modules-5.32:amd64 (5.32.1-2, automatic), libpython3.9:amd64 (3.9.1-4, automatic), python3.9:amd64 (3.9.1-4, automatic), libextutils-pkgconfig-perl:amd64 (1.16-1.1, automatic), libmozjs-78-0:amd64 (78.4.0-2, automatic), libmpdec3:amd64 (2.5.1-1, automatic), libapt-pkg6.0:amd64 (2.1.20, automatic), libvpx6:amd64 (1.9.0-1, automatic), libcrypt1:amd64 (1:4.4.17-1, automatic), libcrypt1:i386 (1:4.4.17-1, automatic), libusbmuxd6:amd64 (2.0.2-3, automatic), system-keyboard-qt:amd64 (21.02.02, automatic), libperl5.32:amd64 (5.32.1-2, automatic), libmd4c0:amd64 (0.4.7-1, automatic), libsnmp40:amd64 (5.9+dfsg-3+b1, automatic), libx264-160:amd64 (2:0.160.3011+gitcde9a93-2+b2, automatic), python3.9-minimal:amd64 (3.9.1-4, automatic), libqt5qmlmodels5:amd64 (5.15.2+dfsg-4, automatic), libxxhash0:amd64 (0.8.0-2, automatic), pkg-config:amd64 (0.29.2-1, automatic), libilmbase25:amd64 (2.5.4-1, automatic), libmypaint-1.5-1:amd64 (1.6.0-2, automatic), python3-pyqt5.sip:amd64 (12.8.1-1+b2, automatic), libhogweed6:amd64 (3.6-2, automatic), qt5-style-plugin-cleanlooks:amd64 (5.0.0+git23.g335dbec-4+b3, automatic), libreadline8:amd64 (8.1-1, automatic), libopenexr25:amd64 (2.5.4-1, automatic), libmysofa1:amd64 (1.2~dfsg0-1, automatic), qt5-gtk2-platformtheme:amd64 (5.0.0+git23.g335dbec-4+b3, automatic), libgcc-s1:i386 (10.2.1-6, automatic), gir1.2-ayatanaappindicator3-0.1:amd64 (0.5.5-2, automatic), libnettle8:amd64 (3.6-2, automatic), libnsl2:amd64 (1.3.0-2, automatic), libmfx1:amd64 (21.1.0-1, automatic), libcodec2-0.9:amd64 (0.9.2-4, automatic), libffi7:amd64 (3.3-5, automatic), qt5-style-plugin-plastique:amd64 (5.0.0+git23.g335dbec-4+b3, automatic), ocl-icd-libopencl1:amd64 (2.2.14-2, automatic), libextutils-depends-perl:amd64 (0.8000-1, automatic), libjson-c5:amd64 (0.15-2, automatic), libgdk-pixbuf-xlib-2.0-0:amd64 (2.40.2-2, automatic), qt5-style-plugin-motif:amd64 (5.0.0+git23.g335dbec-4+b3, automatic), libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1, automatic), libxcb-xinput0:amd64 (1.14-3, automatic), libsphinxbase3:amd64 (0.8+5prealpha+1-12, automatic), libsrt1.4-gnutls:amd64 (1.4.2-1.3, automatic), libdouble-conversion3:amd64 (3.1.5-6.1, automatic)
Upgrade: libjson-glib-1.0-0:amd64 (1.4.4-2, 1.6.0-3), manpages:amd64 (4.16-2, 5.10-1), perl-base:amd64 (5.28.1-6+deb10u1, 5.32.1-2), libossp-uuid-perl:amd64 (1.6.2-1.5+b7, 1.6.2-1.5+b9), network-manager-pptp:amd64 (1.2.8-2, 1.2.8-3+b2), hplip-data:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), qt5-style-plugins:amd64 (5.0.0+git23.g335dbec-2+b17, 5.0.0+git23.g335dbec-4+b3), libavformat58:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libsnappy1v5:amd64 (1.1.7-1, 1.1.8-1), libb-hooks-op-check-perl:amd64 (0.22-1+b1, 0.22-1+b3), libavfilter7:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libqt5svg5:amd64 (5.11.3-2, 5.15.2-2), libplist3:amd64 (2.0.1~git20190104.3f96731-1, 2.2.0-6), libcups2:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libnih-dbus1:amd64 (1.0.3-10+b2, 1.0.3-11), libqt5test5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), python3-distutils:amd64 (3.7.3-1, 3.9.1-2), libnet-ssleay-perl:amd64 (1.85-2+b1, 1.88-3+b1), liblist-moreutils-perl:amd64 (0.416-1+b4, 0.430-2), libxapian30:amd64 (1.4.11-1, 1.4.18-1), gvfs-bin:amd64 (1.38.1-5, 1.46.2-1), qt5-gtk-platformtheme:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), printer-driver-hpcups:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), libdw1:amd64 (0.176-1.1, 0.182+20210205-1), libgirepository-1.0-1:amd64 (1.58.3-2, 1.66.1-1+b1), libimage-magick-q16-perl:amd64 (8:6.9.10.23+dfsg-2.1+deb10u1, 8:6.9.11.60+dfsg-1), apt-xapian-index:amd64 (0.49, 0.52), libgdk-pixbuf2.0-0:amd64 (2.38.1+dfsg-1, 2.40.2-2), libqt5help5:amd64 (5.11.3-4, 5.15.2-3), onboard-common:amd64 (1.4.1-4, 1.4.1-5), libgnutls-openssl27:amd64 (3.6.7-4+deb10u6, 3.7.0-5), libswresample3:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libwbclient0:amd64 (2:4.9.5+dfsg-5+deb10u1, 2:4.13.4+dfsg-1), libqt5sensors5:amd64 (5.11.3-2, 5.15.2-2), libgegl-0.4-0:amd64 (0.4.16-0.1~mx19+1, 1:0.4.26-2), onboard:amd64 (1.4.1-4+b1, 1.4.1-5+b3), libgjs0g:amd64 (1.54.3-1, 1.66.2-1), libxkbfile1:amd64 (1:1.0.9-2+b11, 1:1.1.0-1), libmount1:amd64 (2.33.1-0.1, 2.36.1-6), libdevel-callchecker-perl:amd64 (0.008-1, 0.008-1+b2), libelf1:amd64 (0.176-1.1, 0.182+20210205-1), cpp:amd64 (4:8.3.0-1, 4:10.2.1-1), python3-reportlab-accel:amd64 (3.5.13-1+deb10u1, 3.5.59-1), zlib1g:amd64 (1:1.2.11.dfsg-1, 1:1.2.11.dfsg-2), libgegl-common:amd64 (0.4.16-0.1~mx19+1, 1:0.4.26-2), libtirpc-common:amd64 (1.1.4-0.4, 1.3.1-1), python3-gi-cairo:amd64 (3.30.4-1, 3.38.0-2), libbit-vector-perl:amd64 (7.4-1+b5, 7.4-1+b7), libimage-sane-perl:amd64 (0.14-1+b3, 5-1+b1), libqt5dbus5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libfilesys-df-perl:amd64 (0.92-6+b4, 0.92-6+b6), python3-pyqt5:amd64 (5.11.3+dfsg-1+b3, 5.15.2+dfsg-3), libqt5sql5-sqlite:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libcdio-cdda2:amd64 (10.2+0.94+2-4, 10.2+2.0.0-1+b2), python3-pil:amd64 (5.4.1-2+deb10u2, 8.1.0-1), libgdata22:amd64 (0.17.9-3, 0.17.13-3), libc6:amd64 (2.28-10, 2.31-9), libc6:i386 (2.28-10, 2.31-9), gimp-data:amd64 (2.10.12-0.1~mx19+1, 2.10.22-2), gcc:amd64 (4:8.3.0-1, 4:10.2.1-1), liblocale-gettext-perl:amd64 (1.07-3+b4, 1.07-4+b1), libqt5widgets5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), python3:amd64 (3.7.3-1, 3.9.1-1), locales:amd64 (2.28-10, 2.31-9), cups-server-common:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libnm0:amd64 (1.14.6-2+deb10u1, 1.28.0-2+b1), python3-psutil:amd64 (5.5.1-1, 5.8.0-1), python3-sip:amd64 (4.19.14+dfsg-2, 4.19.24+dfsg-2), gsettings-desktop-schemas:amd64 (3.28.1-1, 3.38.0-2), libcurses-perl:amd64 (1.36-1+b5, 1.37-1+b1), cups-common:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), network-manager:amd64 (1.14.6-2+deb10u1, 1.28.0-2+b1), libterm-readkey-perl:amd64 (2.38-1, 2.38-1+b2), p11-kit-modules:amd64 (0.23.15-2+deb10u1, 0.23.22-1), libx11-6:amd64 (2:1.6.7-1+deb10u1, 2:1.7.0-2), librubberband2:amd64 (1.8.1-7, 1.9.0-1), libpostproc55:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), python3-cups:amd64 (1.9.73-2+b1, 2.0.1-4+b1), libtalloc2:amd64 (2.1.14-2, 2.3.1-2+b1), libqt5xml5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libqt5qml5:amd64 (5.11.3-4, 5.15.2+dfsg-4), libcairo-perl:amd64 (1.106-3+b1, 1.109-1), mx-installer:amd64 (21.2, 21.2.01), libcdio-paranoia2:amd64 (10.2+0.94+2-4, 10.2+2.0.0-1+b2), gimp:amd64 (2.10.12-0.1~mx19+1, 2.10.22-2), libc-l10n:amd64 (2.28-10, 2.31-9), libparams-classify-perl:amd64 (0.015-1+b1, 0.015-1+b3), libqt5gui5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), ppp:amd64 (2.4.7-2+4.1+deb10u1, 2.4.9-1+1), libva2:amd64 (2.4.0-1, 2.10.0-1), python3-minimal:amd64 (3.7.3-1, 3.9.1-1), gvfs-libs:amd64 (1.38.1-5, 1.46.2-1), blueman:amd64 (2.0.8-1+deb10u1, 2.1.4-1+b1), libc-bin:amd64 (2.28-10, 2.31-9), libqt5webchannel5:amd64 (5.11.3-2, 5.15.2-2), libimobiledevice6:amd64 (1.2.1~git20181030.92c5462-2+deb10u1, 1.3.0-6), python3-evdev:amd64 (1.1.2+dfsg-1+b10, 1.4.0+dfsg-1), hplip:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), libnih1:amd64 (1.0.3-10+b2, 1.0.3-11), libnewt0.52:amd64 (0.52.20-8, 0.52.21-4+b3), libnet-dbus-perl:amd64 (1.1.0-5+b1, 1.2.0-1+b1), libpython3-stdlib:amd64 (3.7.3-1, 3.9.1-1), libbabl-0.1-0:amd64 (0.1.66-0.1~mx19+1, 1:0.1.82-1), libhpmud0:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), samba-common:amd64 (2:4.9.5+dfsg-5+deb10u1, 2:4.13.4+dfsg-1), libtirpc3:amd64 (1.1.4-0.4, 1.3.1-1), libavcodec58:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libqt5webkit5:amd64 (5.212.0~alpha2-21, 5.212.0~alpha4-11), libglib2.0-bin:amd64 (2.58.3-2+deb10u2, 2.66.7-1), libselinux1:amd64 (2.8-1+b1, 3.1-2+b2), libjson-glib-1.0-common:amd64 (1.4.4-2, 1.6.0-3), libavutil56:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), python3-lib2to3:amd64 (3.7.3-1, 3.9.1-2), libqt5core5a:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libglib-perl:amd64 (3:1.329-1, 3:1.329.3-1+b1), libwebpmux3:amd64 (0.6.1-2, 0.6.1-2+b1), libswscale5:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libgdk-pixbuf2.0-common:amd64 (2.38.1+dfsg-1, 2.42.2+dfsg-1), libsdl2-2.0-0:amd64 (2.0.9+dfsg1-1, 2.0.14+dfsg2-3), printer-driver-hpijs:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), libtdb1:amd64 (1.3.16-2+b1, 1.4.3-1+b1), manpages-dev:amd64 (4.16-2, 5.10-1), python3-dbus:amd64 (1.2.8-3, 1.2.16-5), libsane-hpaio:amd64 (3.19.6+dfsg0-1~mx19+1, 3.20.11+dfsg0-2), libqt5opengl5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), gvfs:amd64 (1.38.1-5, 1.46.2-1), python3-cairo:amd64 (1.16.2-1+b1, 1.16.2-4+b2), libc-dev-bin:amd64 (2.28-10, 2.31-9), libgimp2.0:amd64 (2.10.12-0.1~mx19+1, 2.10.22-2), python3-gi:amd64 (3.30.4-1, 3.38.0-2), libgnutls30:amd64 (3.6.7-4+deb10u6, 3.7.0-5), python3-pikepdf:amd64 (1.0.5+dfsg-3~deb10u1, 1.17.3+dfsg-4), libfreetype6:amd64 (2.9.1-3+deb10u2, 2.10.4+dfsg-1), libcairo-gobject-perl:amd64 (1.004-3+b1, 1.005-2+b2), libva-x11-2:amd64 (2.4.0-1, 2.10.0-1), libva-wayland2:amd64 (2.4.0-1, 2.10.0-1), perl:amd64 (5.28.1-6+deb10u1, 5.32.1-2), gvfs-common:amd64 (1.38.1-5, 1.46.2-1), libp11-kit0:amd64 (0.23.15-2+deb10u1, 0.23.22-1), cups-bsd:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libaudio-flac-header-perl:amd64 (2.4-3+b1, 2.4-3+b3), libxml-parser-perl:amd64 (2.44-4, 2.46-2), libva-drm2:amd64 (2.4.0-1, 2.10.0-1), cups-core-drivers:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), cups-daemon:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libmp3-tag-perl:amd64 (1.13-1.1, 1.13-1.2), libqt5network5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libglib-object-introspection-perl:amd64 (0.047-1, 0.049-1+b1), libtasn1-6:amd64 (4.13-3, 4.16.0-2), libqt5designer5:amd64 (5.11.3-4, 5.15.2-3), libqt5positioning5:amd64 (5.11.3+dfsg-2, 5.15.2+dfsg-2), libcupsimage2:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libtext-iconv-perl:amd64 (1.7-5+b7, 1.7-7+b1), libaudio-scan-perl:amd64 (1.01-1+b1, 1.01-1+b3), onboard-data:amd64 (1.4.1-4, 1.4.1-5), python3-lxml:amd64 (4.3.2-1+deb10u2, 4.6.2-1), libstdc++6:amd64 (8.3.0-6, 10.2.1-6), cups:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libtevent0:amd64 (0.9.37-1, 0.10.2-1), cups-client:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), cups-ipp-utils:amd64 (2.2.10-6+deb10u4, 2.3.3op2-2), libhtml-parser-perl:amd64 (3.72-3+b3, 3.75-1+b1), libqt5quick5:amd64 (5.11.3-4, 5.15.2+dfsg-4), gvfs-daemons:amd64 (1.38.1-5, 1.46.2-1), libglib2.0-0:amd64 (2.58.3-2+deb10u2, 2.66.7-1), libheif1:amd64 (1.3.2-2~deb10u1, 1.11.0-1), libavresample4:amd64 (7:4.1.6-1~mx19+2, 7:4.3.1-8), libproc-processtable-perl:amd64 (0.56-1, 0.59-2+b1), libde265-0:amd64 (1.0.3-1+b1, 1.0.8-1), libqt5sql5:amd64 (5.11.3+dfsg1-1+deb10u4, 5.15.2+dfsg-4), libx11-xcb1:amd64 (2:1.6.7-1+deb10u1, 2:1.7.0-2), python3-apt:amd64 (1.8.4.3, 2.1.7), libmypaint-common:amd64 (1.3.0-3mx19+1, 1.6.0-2), libtext-charwidth-perl:amd64 (0.04-7.1+b1, 0.04-10+b1)
Remove: python-tdb:amd64 (1.3.16-2+b1), libphonon4:amd64 (4:4.10.2-1), gvfs-backends:amd64 (1.38.1-5), python-samba:amd64 (2:4.9.5+dfsg-5+deb10u1), smbc:amd64 (1.2.2-4+b3), python-smbc:amd64 (1.0.15.6-1+b2), libc6-dev:amd64 (2.28-10), qdbus:amd64 (4:4.8.7+dfsg-18+deb10u1), libelf-dev:amd64 (0.176-1.1), python-gi:amd64 (3.30.4-1), samba:amd64 (2:4.9.5+dfsg-5+deb10u1), g++:amd64 (4:8.3.0-1), libqtcore4:amd64 (4:4.8.7+dfsg-18+deb10u1), python-gobject:amd64 (3.30.4-1), zlib1g-dev:amd64 (1:1.2.11.dfsg-1), fskbsetting:amd64 (0.5.3.5mx19+1), build-essential:amd64 (12.6), libqtgui4:amd64 (4:4.8.7+dfsg-18+deb10u1), samba-libs:amd64 (2:4.9.5+dfsg-5+deb10u1), gvfs-fuse:amd64 (1.38.1-5), g++-8:amd64 (8.3.0-6), apt-notifier:amd64 (20.11.01mx19+1), libqtdbus4:amd64 (4:4.8.7+dfsg-18+deb10u1), python3-smbc:amd64 (1.0.15.6-1+b2), phonon-backend-gstreamer:amd64 (4:4.9.0-1), mx-fluxbox-about:amd64 (20.08.04), libsmbclient:amd64 (2:4.9.5+dfsg-5+deb10u1), smbclient:amd64 (2:4.9.5+dfsg-5+deb10u1), samba-common-bin:amd64 (2:4.9.5+dfsg-5+deb10u1), mx-fluxbox:amd64 (21.01.01), hardinfo:amd64 (0.5.1+git20180227-2), libqt4-xml:amd64 (4:4.8.7+dfsg-18+deb10u1), python-pyqt5:amd64 (5.11.3+dfsg-1+b3), libqt4-dbus:amd64 (4:4.8.7+dfsg-18+deb10u1), libqt4-opengl:amd64 (4:4.8.7+dfsg-18+deb10u1), libstdc++-8-dev:amd64 (8.3.0-6), system-config-samba:amd64 (1.2.63-1mx17+1)
End-Date: 2021-02-17  20:21:27

Start-Date: 2021-02-17  20:58:24
Commandline: apt-get -o=Dpkg::Use-Pty=0 install -y -t mx cmake-qt-gui cmake-doc cmake-data cmake cmake-curses-gui
Requested-By: acs (1000)
Install: libjs-jquery:amd64 (3.5.1+dfsg+~3.5.5-7, automatic), libjs-underscore:amd64 (1.9.1~dfsg-1, automatic), cmake-qt-gui:amd64 (3.16.3-1~mx19+1), cmake-curses-gui:amd64 (3.16.3-1~mx19+1), libjs-sphinxdoc:amd64 (3.4.3-1, automatic), cmake-doc:amd64 (3.16.3-1~mx19+1)
Upgrade: cmake-data:amd64 (3.13.4-1, 3.16.3-1~mx19+1), cmake:amd64 (3.13.4-1, 3.16.3-1~mx19+1)
End-Date: 2021-02-17  20:58:43

Start-Date: 2021-02-19  20:41:13
Commandline: apt-get install vim
Requested-By: acs (1000)
Install: vim-runtime:amd64 (2:8.2.2434-1, automatic), vim:amd64 (2:8.2.2434-1)
Upgrade: vim-common:amd64 (2:8.1.0875-5, 2:8.2.2434-1), vim-tiny:amd64 (2:8.1.0875-5, 2:8.2.2434-1)
End-Date: 2021-02-19  20:41:21
So is the final solution to fix this issue to add "/sbin/NetworkManager" to "/etc/rc.local"

I don't know how to switch to systemd booting.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 4:14 pm
by dolphin_oracle
for now, yes.

just warning you that with all those upgrades from bullseye, you now have a Frankenstein of an install. not saying it won't work for you, just expect problems installing apps from time to time, mostly due to conflicting support libraries. I happened to be working on the Network Manager already, so you got lucky there.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 4:24 pm
by AcsPrime
Ok, so are you saying I should just reinstall mx linux?
The thing is, I installed Linux on this machine because I wanted to try out some C++ projects that only run on Linux and that is why I needed gcc 10 (the project demands it).

What is the best option for me?
- Should I go with another distro?
- Should I reinstall and get gcc10 (and other tools) another way? (without breaking anything)
- Should I give up on linux all together and just stick with windows?
- Should I consult an oracle before I try to install anything as it seems linux (maybe this distro) breaks easy

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Feb 19, 2021 4:28 pm
by dolphin_oracle
if you need gcc10, you would be better off choosing a OS that has it already. debian bullseye, probably ubuntu, I would guess manjaro would all be OK. (not sure about ubuntu, might be gcc9).

linux doesn't break easy if you don't go adding repos that conflict with the distro.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Sat Feb 20, 2021 1:52 am
by SwampRabbit
AcsPrime wrote: Fri Feb 19, 2021 4:24 pm Ok, so are you saying I should just reinstall mx linux?
The thing is, I installed Linux on this machine because I wanted to try out some C++ projects that only run on Linux and that is why I needed gcc 10 (the project demands it).

What is the best option for me?
- Should I go with another distro?
- Should I reinstall and get gcc10 (and other tools) another way? (without breaking anything)
- Should I give up on linux all together and just stick with windows?
- Should I consult an oracle before I try to install anything as it seems linux (maybe this distro) breaks easy
Consult and oracle? You just had THE dolphin_oracle help you.

I would start by learning HOW TO use MX a bit, you may find that it has most of what you need without going to great lengths.

MX Linux is based on Debian Stable, therefore it is and can be behind a bit like with gcc.

MX Linux (and Linux in general) does not break easily, unless you count easily as throwing it off the top of a sky scraper without a parachute.

If you have a question just ask before blindly following online tutorials or just randomly doing things. This goes for any Linux distro. ;)

cmake 3.16.3 is in the MX Package Installer under the MX Test Repo tab and the Debian Backports. Using this route may have saved you some trouble.

We have gcc 9 in an experimental repo, haven't used or tested it myself. gcc-10 won't come MX-19 safely (99.99% certain on this).

If you want a bleeding edge distro there are plenty out there. Fedora and Manjaro are two decent ones to look at.
You could go further and also have more fun by trying Arch, Gentoo/Funtoo out.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Apr 30, 2021 9:33 pm
by yoel
I had a corrupt installation of Network manager.
The internet wouldn't work at all but I managed to force the network card to work with this command:

Code: Select all

sudo dhclient eth0
Then you need to delete the broken network manager installation using synaptic. or try this:

Code: Select all

sudo apt-get remove --purge network-manager*
sudo apt autoremove
sudo apt update
sudo apt upgrade
Once the broken files have been removed and you are ready to reinstall network manager, install aptitude in the termina. This program will try to resolve installation issuesl:

Code: Select all

sudo apt-get install aptitude

Code: Select all

sudo aptitude install network-manager
After all this, my Network manager icon on the system tray was missing and I reinstalled from here:
https://packages.debian.org/buster/nm-tray

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Apr 30, 2021 10:23 pm
by JayM
Never mind.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Mon Aug 23, 2021 9:29 am
by jimbob1
Installed mx21 last night, when I rebooted, everything was working until I stupidly by habit clicked on update manager to install all uploads (noooo). Once finished, no internet access, today I tried tried this below and it worked!!!
So is the final solution to fix this issue to add "/sbin/NetworkManager" to "/etc/rc.local"
Thanks dolphin_oracle, :worship: saved me any further panic.

BTW - you guys are doing an awesome job, love MX - been using about a year now, would swap it for anything else :winner:

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Mon Nov 15, 2021 5:41 am
by zoli62
After upgrading from Mx Linux 19.4 to Mx Linux 21, I did not run the sudo apt get install network-manager-sysvinit-compat command, so the network manager is not running. I downloaded it from here. http://mxrepo.com/mx/repo/pool/main/n/n ... it-compat/ My question is can I manually install the downloaded package with dpkg instead of apt-get install?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Mon Nov 15, 2021 5:51 am
by Huckleberry Finn
zoli62 wrote: Mon Nov 15, 2021 5:41 amMy question is can I manually install the downloaded package with dpkg instead of apt-get install?
Yep :)

(Meanwhile this thread is old / mixed ... )

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Tue Nov 16, 2021 6:24 am
by zoli62
Huckleberry Finn wrote: Mon Nov 15, 2021 5:51 am
zoli62 wrote: Mon Nov 15, 2021 5:41 amMy question is can I manually install the downloaded package with dpkg instead of apt-get install?
Yep :)

(Meanwhile this thread is old / mixed ... )
The thread is really old, but it just got in front of my eyes. :) Of course, I did the upgrade from 19.4 to 21 based on the Debian Way, and although I read the migration information, I didn't pay attention to everything and did not install the correct network manager. :) In this regard, let me ask why is mxlinux 21 using sysvinit instead of systemd?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Tue Nov 16, 2021 7:53 am
by Huckleberry Finn
zoli62 wrote: Tue Nov 16, 2021 6:24 amwhy is mxlinux 21 using sysvinit instead of systemd?
You know, you can boot with systemd ("Advanced Options" in Grub) furthermore, can make it default ( Menu => "MX Boot Options" : "Boot to" ). Shortly, MX prefers SysV for this or that reason but doesn't force anyone to use this or that :)

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Wed Nov 17, 2021 5:58 am
by zoli62
Huckleberry Finn wrote: Tue Nov 16, 2021 7:53 am
zoli62 wrote: Tue Nov 16, 2021 6:24 amwhy is mxlinux 21 using sysvinit instead of systemd?
You know, you can boot with systemd ("Advanced Options" in Grub) furthermore, can make it default ( Menu => "MX Boot Options" : "Boot to" ). Shortly, MX prefers SysV for this or that reason but doesn't force anyone to use this or that :)
I remember when the introduction of systemd met with resistance from the community. Since I use multiple systems in parallel, for testing purposes, I don't use MX Linux Grub, so I can't configure it to start with systemd. :) I just find it interesting that MX Linux has migrated from systemd to Sysvinit by default.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Wed Nov 17, 2021 6:37 am
by Huckleberry Finn
zoli62 wrote: Wed Nov 17, 2021 5:58 amI don't use MX Linux Grub, so I can't configure it to start with systemd.
Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd
Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Thu Nov 18, 2021 11:20 am
by zoli62
Huckleberry Finn wrote: Wed Nov 17, 2021 6:37 am
zoli62 wrote: Wed Nov 17, 2021 5:58 amI don't use MX Linux Grub, so I can't configure it to start with systemd.
Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd
Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Thu Nov 18, 2021 12:18 pm
by dolphin_oracle
zoli62 wrote: Thu Nov 18, 2021 11:20 am
Huckleberry Finn wrote: Wed Nov 17, 2021 6:37 am
zoli62 wrote: Wed Nov 17, 2021 5:58 amI don't use MX Linux Grub, so I can't configure it to start with systemd.
Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd
Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?
network-manager-sysvinit-compat doens't do anything under systemd. it exits without action, because network-manager already provides a systemd service file for startup.

the live system is designed to be used under sysvinit. snapshot and the installer will still work, but certain activities like semi-automatic persistence file saving and a few other odds and ends on the live system will not. but on an installed system, you don't lose anything.

and if you leave sysvinit installed, the live snapshots will use sysvinit automatically.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Thu Nov 18, 2021 12:43 pm
by zoli62
dolphin_oracle wrote: Thu Nov 18, 2021 12:18 pm
zoli62 wrote: Thu Nov 18, 2021 11:20 am
Huckleberry Finn wrote: Wed Nov 17, 2021 6:37 am Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd
Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?
network-manager-sysvinit-compat doens't do anything under systemd. it exits without action, because network-manager already provides a systemd service file for startup.

the live system is designed to be used under sysvinit. snapshot and the installer will still work, but certain activities like semi-automatic persistence file saving and a few other odds and ends on the live system will not. but on an installed system, you don't lose anything.

and if you leave sysvinit installed, the live snapshots will use sysvinit automatically.

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Thu Nov 18, 2021 1:05 pm
by dolphin_oracle
zoli62 wrote: Thu Nov 18, 2021 12:43 pm

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?
some of us are old farts that like sysVinit.

but mostly the live-usb system works just better with sysvinit.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 11:51 am
by zoli62
Huckleberry Finn wrote: Wed Nov 17, 2021 6:37 am
zoli62 wrote: Wed Nov 17, 2021 5:58 amI don't use MX Linux Grub, so I can't configure it to start with systemd.
Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd
Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub
After making the desired changes, I typed the string containing systemd after the existing kernel parameter, and interestingly, I got to the emergency shell after the next boot. Then, of course, I edited the grub.cfg file with nano and deleted the string containing systemd at the appropriate places in the file. I then started the other distro with my own grub (Kubuntu), logged in, issued a sudo update-grub command, rebooted, and then was able to log in to MX Linux normally. What could have caused this?

PS.
If I made the desired changes to the / etc / default / grub file and then ran a sudo update-grub command, the next boot was successful. I checked the contents of the / etc / default / grub file and the GRUB_CMDLINE_LINUX_DEFAULT line was missing the] init = / lib / systemd / systemd string I typed earlier. However, a grub.bak file was created. So it looks like the system didn't allow me to save the changes, even though I made them as root. . This is a different problem from the previous one, I just supplemented what I described earlier.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 11:55 am
by zoli62
dolphin_oracle wrote: Thu Nov 18, 2021 1:05 pm
zoli62 wrote: Thu Nov 18, 2021 12:43 pm

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?
some of us are old farts that like sysVinit.

but mostly the live-usb system works just better with sysvinit.
I agree. Nor did I applaud my joy when systemd was introduced as an old adult warrior on Debian. :)

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 1:02 pm
by Huckleberry Finn
This is a thread from Feb 19 and last reply was on 23 Aug

Also we still don't have your "Quick System Info". How can anyone "guess" what happened / how / why / why not ... ?

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 2:30 pm
by zoli62
Huckleberry Finn wrote: Fri Nov 19, 2021 1:02 pm This is a thread from Feb 19 and last reply was on 23 Aug

Also we still don't have your "Quick System Info". How can anyone "guess" what happened / how / why / why not ... ?
I manually upgraded from MX Linux 19.4 to MX Linux 21 based on an unofficial Wiki described on the MX Linux website. The system information based on inxi -M is as follows:

Code: Select all

System:    Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.16.0 
           Distro: MX-21_x64 Wildflower October 21  2019 
Machine:   Type: Laptop System: LENOVO product: 20AT0030UK v: ThinkPad L440 
           serial: <root required> 
           Mobo: LENOVO model: 20AT0030UK v: 0B98401 Pro serial: <root required> UEFI: LENOVO 
           v: J4ET81WW(1.81) date: 08/14/2015 
Battery:   ID-1: BAT0 charge: 53.5 Wh condition: 70.8/71.3 Wh (99%) 
CPU:       Topology: Dual Core model: Intel Core i5-4200M bits: 64 type: MT MCP 
           L2 cache: 3072 KiB 
           Speed: 798 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 807 2: 864 3: 798 4: 798 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I217-V driver: e1000e 
           IF: eth0 state: down mac: 54:ee:75:0a:e1:33 
           Device-2: Intel Wireless 7260 driver: iwlwifi 
           IF: wlan0 state: down mac: e2:42:aa:19:ed:f7 
           Device-3: ZTE WCDMA MSM ZTE Mobile Broadband type: USB driver: cdc_ether,usb-storage 
           IF: usb0 state: up speed: N/A duplex: N/A mac: f6:f6:67:f3:51:ae 
Drives:    Local Storage: total: 447.13 GiB used: 13.18 GiB (2.9%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB 
Partition: ID-1: / size: 27.09 GiB used: 13.18 GiB (48.6%) fs: ext4 dev: /dev/sda5 
           ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 46.0 C mobo: 35.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 203 Uptime: 7m Memory: 7.69 GiB used: 676.9 MiB (8.6%) Shell: bash 
           inxi: 3.0.36

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 5:49 pm
by Huckleberry Finn
Huckleberry Finn wrote: Fri Nov 19, 2021 1:02 pm "Quick System Info".
zoli62 wrote: Fri Nov 19, 2021 2:30 pminxi -M is as follows
:lipsrsealed:

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Fri Nov 19, 2021 5:51 pm
by Eadwine Rose
Find it in the menu, run it, paste in a reply. Don't edit.

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Sat Nov 20, 2021 4:15 am
by zoli62
Eadwine Rose wrote: Fri Nov 19, 2021 5:51 pm Find it in the menu, run it, paste in a reply. Don't edit.

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, plank wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_x64 Wildflower October 21  2019 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 20AT0030UK v: ThinkPad L440 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 20AT0030UK v: 0B98401 Pro serial: <filter> UEFI: LENOVO 
           v: J4ET81WW(1.81) date: 08/14/2015 
Battery:   ID-1: BAT0 charge: 7.5 Wh condition: 70.8/71.3 Wh (99%) volts: 11.7/10.8 
           model: SMP 45N1149 type: Li-ion serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i5-4200M bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: 28 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19953 
           Speed: 947 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 992 2: 867 3: 972 4: 911 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           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 generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I217-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: 5080 
           bus ID: 00:19.0 chip ID: 8086:153b 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus ID: 02:00.0 
           chip ID: 8086:08b2 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 447.13 GiB used: 9.82 GiB (2.2%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: B1C2 scheme: GPT 
Partition: ID-1: / raw size: 27.77 GiB size: 27.09 GiB (97.52%) used: 9.82 GiB (36.3%) fs: ext4 
           dev: /dev/sda5 
           ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 41.0 C mobo: 24.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     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 main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-dev.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ bullseye main non-free
           2: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/testrepo/ bullseye test
           Active apt repos in: /etc/apt/sources.list.d/opera-developer.list 
           1: deb https://deb.opera.com/opera-developer/ stable non-free #Opera Browser (final releases)
           Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
           1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi-snapshot.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/snapshot/deb/ stable main
Info:      Processes: 216 Uptime: N/A Memory: 7.69 GiB used: 603.7 MiB (7.7%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Sat Nov 20, 2021 10:05 am
by Huckleberry Finn

Re: "NetworkManager is not running/Networking disabled" after update

Posted: Mon Jan 31, 2022 9:52 pm
by anyrug
yoel wrote: Fri Apr 30, 2021 9:33 pm I had a corrupt installation of Network manager.
The internet wouldn't work at all but I managed to force the network card to work with this command:

Code: Select all

sudo dhclient eth0
Then you need to delete the broken network manager installation using synaptic. or try this:

Code: Select all

sudo apt-get remove --purge network-manager*
sudo apt autoremove
sudo apt update
sudo apt upgrade
Once the broken files have been removed and you are ready to reinstall network manager, install aptitude in the termina. This program will try to resolve installation issuesl:

Code: Select all

sudo apt-get install aptitude

Code: Select all

sudo aptitude install network-manager
After all this, my Network manager icon on the system tray was missing and I reinstalled from here:
https://packages.debian.org/buster/nm-tray
how do you install the last link about the icon in the tray. also thank You for the help I’m new at this