root@station:~# nmcli general logging level DEBUG domains all
root@station:~# nmcli general logging
LEVEL DOMAINS
DEBUG
PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,WIFI_SCAN,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,DBUS_PROPS,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD,VPN_PLUGIN:INFO,PROXY
I will contact you as soon as the outage occurs again to provide you with the
log.
Greetings.
----Message d'origine----
De : m...@dorfdsl.de
Date : 18/07/2024 - 21:34 (E)
À : pham...@bluewin.ch, 1074...@bugs.debian.org
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when
booting Debian
Am 18.07.2024 um 18:30:44 Uhr schrieb pham...@bluewin.ch:
> The command line you asked me to enter is invalid ?!?!
> sudo nmcli general logging level LEVEL domains ALL
LEVEL must be replaced by the level, e.g. INFO or DEBUG.
sudo nmcli general logging level DEBUG domains all
After that please check if the change has been applied:
sudo nmcli general logging
This must show DEBUG for all domains. If not, no debug logs will be
produced.
If that is the case, help can continue.
> On top of that you closed my previous bug for no reason and I had to
> reopen it.
This wasn't me.
> Forgive me for being blunt, but what's the problem? You
> don't have time to deal with it? If that's it, there are other
> maintainers who are most certainly ready to take over, don't you
> think?
I can understand that you are annoyed, but unless your system produces
DEBUG logs, nobody can further investigate that.
--
kind regards
Marco
_______________________________________________
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
