设置-网络：
Oops something has gone wrong. Please contact your software vendor.
NetworkManager needs to be running.
~$ NetworkManager
NetworkManager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4: undefined symbol: gnutls_srp_allocate_client_credentials, version GNUTLS_3_4
sudo 服务网络管理器重新启动
~$ sudo service network-manager restart
Job for NetworkManager.service failed because the control process exited with error code.
See "systemctl status NetworkManager.service" and "journalctl -xe" for details.
systemctl status NetworkManager.service
~$ systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-06-18 16:49:27 MSK; 21min ago
Docs: man:NetworkManager(8)
Process: 5827 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=127)
Main PID: 5827 (code=exited, status=127)
Jun 18 16:49:27 galls-Sys systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.
Jun 18 16:49:27 galls-Sys systemd[1]: Stopped Network Manager.
Jun 18 16:49:27 galls-Sys systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jun 18 16:49:27 galls-Sys systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
Jun 18 16:49:27 galls-Sys systemd[1]: Failed to start Network Manager.
journalctl-xe
~$ journalctl -xe
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit NetworkManager.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jun 18 17:19:43 galls-Sys systemd[1]: Stopped Network Manager.
-- Subject: A stop job for unit NetworkManager.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit NetworkManager.service has finished.
--
-- The job identifier is 6353 and the job result is done.
Jun 18 17:19:43 galls-Sys systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jun 18 17:19:43 galls-Sys systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit NetworkManager.service has entered the 'failed' state with result 'exit-code'.
Jun 18 17:19:43 galls-Sys systemd[1]: Failed to start Network Manager.
-- Subject: A start job for unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit NetworkManager.service has finished with a failure.
--
-- The job identifier is 6353 and the job result is failed.
Jun 18 17:19:48 galls-Sys sudo[8191]: galls : TTY=pts/0 ; PWD=/home/galls ; USER=root ; COMMAND=/usr/sbin/service network-manager restart
Jun 18 17:19:48 galls-Sys sudo[8191]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 18 17:19:48 galls-Sys systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jun 18 17:19:48 galls-Sys systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit NetworkManager.service has entered the 'failed' state with result 'exit-code'.
Jun 18 17:19:48 galls-Sys systemd[1]: Failed to start Network Manager.
-- Subject: A start job for unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit NetworkManager.service has finished with a failure.
--
-- The job identifier is 6440 and the job result is failed.
Jun 18 17:19:48 galls-Sys sudo[8191]: pam_unix(sudo:session): session closed for user root
Jun 18 17:19:54 galls-Sys /usr/lib/gdm3/gdm-x-session[2576]: (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-0ms), your system >
Jun 18 17:19:54 galls-Sys /usr/lib/gdm3/gdm-x-session[2576]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-13ms), your >
Jun 18 17:19:59 galls-Sys /usr/lib/gdm3/gdm-x-session[2576]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-12ms), your >
Jun 18 17:20:11 galls-Sys /usr/lib/gdm3/gdm-x-session[2576]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-11ms), your >
lines 3103-3151/3151 (END)
是否配置
~$ ifconfig
Traceback (most recent call last):
File "/usr/lib/command-not-found", line 28, in <module>
from CommandNotFound import CommandNotFound
File "/usr/lib/python3/dist-packages/CommandNotFound/CommandNotFound.py", line 19, in <module>
from CommandNotFound.db.db import SqliteDatabase
File "/usr/lib/python3/dist-packages/CommandNotFound/db/db.py", line 3, in <module>
import sqlite3
File "/usr/lib/python3.8/sqlite3/__init__.py", line 23, in <module>
from sqlite3.dbapi2 import *
File "/usr/lib/python3.8/sqlite3/dbapi2.py", line 27, in <module>
from _sqlite3 import *
ImportError: /usr/lib/python3.8/lib-dynload/_sqlite3.cpython-38-x86_64-linux-gnu.so: undefined symbol: sqlite3_enable_load_extension
没有网络连接可以修复吗？
答案1
我昨天也遇到了同样的问题。我的 Kubuntu 20.10 笔记本电脑 (Thinkpad T460) 处于空闲状态，并且启用了屏幕锁定，当我重新登录时，KDE 无法恢复，并且网络断开。
ifconfig 和 network-manager 都失败并显示相同的错误消息，并且我的系统日志中出现了令人讨厌的数字垃圾块。
在网上研究了几个小时之后，这个盒子又能正常工作了。
我强制进行 fsck 以便下次重启
sudo tune2fs -c 1 /dev/vgkubuntu/root
重启后，我删除了一些库，假设它们在事件中被损坏了
cd /usr/local/lib您的版本号可能会有所不同。
sudo rm libgnutls.so.30 libsqlite3.so.0
cd /lib/x86_64-linux-gnu/
sudo rm libcurl-gnutls.so.4.6.0
然后手动重新安装
cd /var/cache/apt/archives/
sudo dpkg -i libsqlite3-0_3.31.1-4ubuntu0.2_amd64.deb
sudo dpkg -i libgnutls30_3.6.13-2ubuntu1.3_amd64.deb
您的版本号可能有所不同，请使用最新版本。
这使我的网络管理器和其他工具能够重新启动。
但我现在必须通过调用 wpa_supplicant 和 dhclient 手动连接 wlan。
更新：我可以将其追溯到 Filezilla Client，因为我的 ubuntu 服务器在安装 FZ 后立即启动了相同的行为。我已在以下位置登录了工单
https://trac.filezilla-project.org/ticket/12426#ticket
Filezilla 的解决方案是，您永远不应该将 Filezilla 客户端安装在系统目录中，而应该安装在自己的空间中 - 例如/opt/Filezilla- 这对我来说很新颖。
答案2
您最近有没有使用过 aircrack？如果是，问题可能是无线网卡处于监控模式。
尝试使用sudo airmon-ng stop wlan0。它可能是 wlan0 或 wlan0mon，你可以使用ifconfig命令确认
完成后，运行service network-manager restart。