The output of the command you asked for is
$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2020-02-17 08:51:10 -03; 5h 33min ago
Docs: man:NetworkManager(8)
Main PID: 1206 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 22.7M
CGroup: /system.slice/NetworkManager.service
└─1206 /usr/sbin/NetworkManager --no-daemon
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9009] device
(p2p-dev-wlp3s0): supplicant management interface state: com
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9421] device
(wlp3s0): supplicant interface state: authenticating -> asso
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9422] device
(p2p-dev-wlp3s0): supplicant management interface state: aut
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9453] device
(wlp3s0): supplicant interface state: associating -> associa
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9453] device
(p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 08:51:54 adcamp NetworkManager[1206]: <info> [1581940314.0257] device
(wlp3s0): supplicant interface state: associated -> complete
fev 17 08:51:54 adcamp NetworkManager[1206]: <info> [1581940314.0274] device
(p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 08:55:57 adcamp NetworkManager[1206]: <info> [1581940557.0456]
agent-manager: req[0x5652c8d3ab10, :1.407/org.gnome.Shell.NetworkAg
fev 17 09:00:01 adcamp NetworkManager[1206]: <info> [1581940801.3983] dhcp4
(wlp3s0): state changed bound -> expire
fev 17 09:00:01 adcamp NetworkManager[1206]: <info> [1581940801.3985] device
(wlp3s0): DHCPv4: 480 seconds grace period started
As the other thread mentions, it seems that it has to do with the
NetworkManager. Since mine was already running (as I understood from
the output above), I restarted it with
$systemctl restart NetworkManager
and the settings are working again. But the outputs of the status seems
the same to me. See, after restart
$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2020-02-17 15:15:22 -03; 14s ago
Docs: man:NetworkManager(8)
Main PID: 9778 (NetworkManager)
Tasks: 4 (limit: 4915)
Memory: 7.7M
CGroup: /system.slice/NetworkManager.service
└─9778 /usr/sbin/NetworkManager --no-daemon
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8784] device
(p2p-dev-wlp3s0): supplicant management interface state: dis
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8802] device
(wlp3s0): supplicant interface state: authenticating -> asso
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8802] device
(p2p-dev-wlp3s0): supplicant management interface state: aut
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8924] device
(wlp3s0): supplicant interface state: associating -> associa
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8924] device
(p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 15:15:30 adcamp NetworkManager[9778]: <info> [1581963330.0012] device
(wlp3s0): supplicant interface state: associated -> complete
fev 17 15:15:30 adcamp NetworkManager[9778]: <info> [1581963330.0013] device
(wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure)
fev 17 15:15:30 adcamp NetworkManager[9778]: <info> [1581963330.0013] device
(p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 15:15:30 adcamp NetworkManager[9778]: <info> [1581963330.0015] device
(wlp3s0): state change: config -> ip-config (reason 'none',
fev 17 15:15:30 adcamp NetworkManager[9778]: <info> [1581963330.0020] dhcp4
(wlp3s0): activation: beginning transaction (timeout in 45 se
However, the settings open only once. After closing it, it gives the
same error. And if I restart the NetworkManager it opens again (once).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1862767
Title:
gnome-control-center crashes when try to open it
Status in gnome-control-center package in Ubuntu:
Incomplete
Bug description:
gnome-control center crashes when trying to open it. Tested as
following
$ gnome-control-center --verbose
**
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
assertion failed: (G_IS_OBJECT (object))
Bail out!
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
assertion failed: (G_IS_OBJECT (object))
Aborted (core dumped)
When trying to open it through the graphical interface it dies
silently. A message of error would help too.
Additional information:
$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
$ apt-cache policy gnome-control-center
gnome-control-center:
Installed: 1:3.34.1-1ubuntu2
Candidate: 1:3.34.1-1ubuntu2
Version table:
*** 1:3.34.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 09:24:49 2020
InstallationDate: Installed on 2018-05-07 (644 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
