this post was submitted on 15 Aug 2025
32 points (100.0% liked)

Linux

57549 readers
821 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

I edited the new debian.sources file in /etc/apt/sources.list.d according to debian instructions, started to upgrade and successfuly upgraded to 13.0, at least core debian (can use mpv, vlc, thunar, libreoffice...)

Problem is, this notebook with debian 13.0 doesnt have a working network manager and there are still 900 packages that need upgrading.

The command I entered in the terminal: sudo systemctl status NetworkManager.service returns: unit NetworkManager.service could not be found.

I have an android phone I thought I could use as a network hotspot or maybe tether, but debian 13.0 doesnt recognize it, so I really dont know what to do

Lan cable didnt work either.

Help appreciated

ETA: THANK YOU GUYS FOR YOUR AWESOME HELP!!!

special thanks to InnerScientist and stuner for their approach but what worked was what IHave69XiBucks proposed.

top 14 comments
sorted by: hot top controversial new old
[–] OminousOrange@lemmy.ca 2 points 6 days ago

Could you edit your post to include the solution for anyone else with the same issue coming across this post in the future?

[–] limelight79@lemmy.world 1 points 6 days ago

This is interesting. I updated my laptop and had a network issue as well, but mine was different - it wanted to use dnsmasq, which I don't need (being an end-point, not a server), and dnsmasq wasn't picking up the dns from dhcp.

Solution turned out to be to disable dnsmasq using systemctl and reboot.

[–] krotos@lemmy.world 15 points 1 week ago (2 children)

Case sensitivity may be the problem. Try systemctl status NetworkManager

[–] arsus5478@lemmy.ml 3 points 1 week ago

Sorry, corrected it. Results didnt change

[–] FauxLiving@lemmy.world 2 points 1 week ago (1 children)

Almost certainly this.

Type nmcli, if it does anything but complain that it can't find that command, you have NetworkManager installed

[–] arsus5478@lemmy.ml 2 points 1 week ago* (last edited 1 week ago)

nmcli returns command not found

sudo systemctl status NetworkManager.service returns: unit NetworkManager.service could not be found.

Seems I dont have that one either

[–] InnerScientist@lemmy.world 6 points 1 week ago* (last edited 1 week ago) (1 children)

Connect a lan cable and:

ip a (shows network interfaces and ips

ip a a 192.168.<subnet>.<unused ip>/24 dev <interface> (get the subnet from your router or phone WiFi settings, interface is the interface starting with "en" from the first command, for unused ip just try your phone IP +1)

ip r a default via <router IP> (router IP can be seen in your phones WiFi settings under gateway)

Also checkout /etc/resolv.conf, replace its content with "nameserver 8.8.8.8"

[–] FauxLiving@lemmy.world 5 points 1 week ago (1 children)

For reference, those letters are just short for, respectively

address
address add
route add
[–] arsus5478@lemmy.ml 3 points 1 week ago

Thanks for that

[–] frongt@lemmy.zip 3 points 1 week ago

Bring up networking manually?

Or just back up your files and reinstall.

[–] stuner@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

That sounds pretty bad and probably means other things are broken too. The easiest option would probably be a reinstall at this point, but if you want to learn something you can also try to salvage your install.

To recover, it's probably easiest to manually configure your Ethernet connection as described by InnerScientist and then re-install the network-manager package.

First, you can check the status of the network-manager package using dpgk. It should look like this (ii at the start, but it sounds like it's not installed in your case):

$ dpkg -l | grep -i network-manager
ii  network-manager                         1.52.1-1                        amd64        network management framework (daemon and userspace tools)
ii  network-manager-l10n                    1.52.1-1                        all          network management framework (translation files)

You can also check /var/log/apt/history.log to see what went wrong and if there are other things you need to fix.

I performed the upgrade in two steps apt upgrade --without-new-pkgs and apt full-upgrade (based on the release notes). I can see the following on the line Upgrade: for the command apt full-upgrade:

network-manager:amd64 (1.42.4-1+deb12u1, 1.52.1-1)

On the Remove: line you can see the packages that were removed. Unfortunately, the names of many libraries were changed in this release (e.g., libreadline8:amd64 to libreadline8t64:amd64), so there's a lot of noise in there. Maybe you can look at that line and ignore everything that starts with lib to see if any other important packages were removed.

[–] k_rol@lemmy.ca 2 points 1 week ago (1 children)

but what worked was what IHave69XiBucks proposed.

Why do I not see his comment?

[–] mouse@midwest.social 5 points 1 week ago (1 children)

Your Lemmy instance blocks the lemmygrad instance where IHave69XiBucks resides. My instance does too.

[–] k_rol@lemmy.ca 1 points 6 days ago

Ah, that explains. Thanks.