Your message dated Fri, 6 Mar 2026 02:38:55 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#1122088: [ sudo
NetworkManager --no-daemon ] Segmentation fault
has caused the Debian Bug report #1122088,
regarding [ sudo NetworkManager --no-daemon ] Segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1122088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122088
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.52.1-1
Severity: grave
Dear maintainers,
I am trying to run Network-manager on a Debian Trixie 13.2 installation
on one amd64 target (MacBook Pro 2011 13-inch).
My configuration is ...
ansible@hn-macbookpro-440:~$ uname -a
Linux hn-macbookpro-440 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linux
ansible@hn-macbookpro-440:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 13 (trixie)
Release: 13
Codename: trixie
ansible@hn-macbookpro-440:~$
ansible@hn-macbookpro-440:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-============================================-
ansible@hn-macbookpro-440:~$
ansible@hn-macbookpro-440:~$ apt policy network-manager
network-manager:
Installed: 1.52.1-1
Candidate: 1.52.1-1
Version table:
1.54.1-1 80
80 http://ftp.de.debian.org/debian forky/main amd64 Packages
*** 1.52.1-1 500
500 http://ftp.de.debian.org/debian trixie/main amd64 Packages
100 /var/lib/dpkg/status
1.42.4-1+deb12u1 90
90 http://ftp.de.debian.org/debian bookworm/main amd64 Packages
ansible@hn-macbookpro-440:~$
My target has one physical Ethernet on RJ45 (if-lan) with dedicated
VLANs in respect of my network infrastructure.
All logical network interfaces connected to the physical if-lan
interface are managed by ifup/fdown, so only the roadwarrior interface
(if-sta0) is used to manage the external connection when this laptop is
out of the office.
As a result, Network-manager is configure as follow :
ansible@hn-macbookpro-440:~$ cat /etc/NetworkManager/NetworkManager.conf
|grep -v "#" |grep -v ^$
[main]
plugins=ifupdown,keyfile
dhcp=dhclient
no-auto-default=if-lan
no-auto-default=if-lan.6
no-auto-default=if-service
no-auto-default=if-lan.7
no-auto-default=if-lan.9
no-auto-default=if-admin
no-auto-default=if-lan.8
no-auto-default=if-user
no-auto-default=if-pixel-8
no-auto-default=if-lan
wifi-wext-only=false
[ifupdown]
managed=false
[logging]
level=DEBUG
domains=ETHER,WIFI,DHCP4,WIFI_SCAN,IP4
I hope this will ensure that Network-manager always ignores the state of
this physical interface (if-lan), but i a m not sure (?)
Before launching NM, i make some tests....
ansible@hn-macbookpro-440:~$ sudo NetworkManager --no-daemon
--print-config
# NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf,
/usr/lib/NetworkManager/conf.d/{20-connectivity-debian.conf,no-mac-addr-change.conf}
[main]
# rc-manager=auto
# migrate-ifcfg-rh=false
# auth-polkit=true
# iwd-config-path=
plugins=ifupdown,keyfile
dhcp=dhclient
no-auto-default=if-lan
wifi-wext-only=true
configure-and-quit=no
[connectivity]
uri=http://network-test.debian.org/nm
[ifupdown]
managed=true
[logging]
# backend=journal
# audit=true
level=DEBUG
domains=ETHER,WIFI,DHCP4,WIFI_SCAN,IP4
[device]
# wifi.backend=wpa_supplicant
[device-31-mac-addr-change]
match-device=driver:eagle_sdio,driver:wl
wifi.scan-rand-mac-address=no
# no-auto-default file "/var/lib/NetworkManager/no-auto-default.state"
# WARNING: unknown key 'wifi-wext-only' in section [main] of file
'/etc/NetworkManager/NetworkManager.conf'
ansible@hn-macbookpro-440:~$
My first question is about warning on wifi-wext-only ??. This keys is
defined into man, why this warning ?
My second question is more boring....
ansible@hn-macbookpro-440:~$ time sudo NetworkManager --no-daemon
Segmentation fault
real 0m0.059s
user 0m0.010s
sys 0m0.008s
Best regards.
--
-- Jean-Marc LACROIX () --
-- mailto : [email protected] --
--- End Message ---
--- Begin Message ---
On Sat, 13 Dec 2025 02:31:15 +0100 Michael Biebl <[email protected]> wrote:
Control: tags -1 + moreinfo, unreproducible
Am 06.12.25 um 22:09 schrieb Jean-Marc LACROIX:
> My first question is about warning on wifi-wext-only ??. This keys is
> defined into man, why this warning ?
In which man page exactly?
I see no such key in the network-manager sources.
>
> My second question is more boring....
>
> ansible@hn-macbookpro-440:~$ time sudo NetworkManager --no-daemon
> Segmentation fault
Please install dbgsym packages and provide a backtrace of the crash.
https://wiki.debian.org/HowToGetABacktrace
Please also attach the output of
reportbug --template network-manager
No further updates, thus closing the bug report.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
