Your message dated Sat, 11 May 2013 17:23:55 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#707177: network-manager:
Segfault when enabling wireless or wired connection
has caused the Debian Bug report #707177,
regarding network-manager: Segfault when enabling wireless or wired connection
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.)
--
707177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707177
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.8.0-4
Severity: important
Dear Maintainer,
* What led up to the situation?
My network connection worked (both wired and
wireless) were tested, in an office setting (the wireless was known
to work where I was staying). At this office, I upgraded
network-manager and firmware-realtek, and still had no problems
connecting. When I got to where I was staying the night, as soon as
I brought my laptop out of suspend, NetworkManager tried to connect
and then the systray icon disappeared. I tried starting it again,
and it connected to the BLANCHER-Guest network, rather than the
BLANCHER network. When I changed it to BLANCHER, the animation
seemed to indicate that it was almost connected, then the icon would
disappear. My clue that it was a segfault came from dmesg:
[ 7814.774882] NetworkManager[17068]: segfault at 8 ip
0000000000484b39
sp 00007fffa6232da0 error 4 in NetworkManager[400000+fb000]
This message appears every time I try to start NetworkManager, and it
crashes every time.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried rebooting, but the segfault message in dmesg did not
give
me hope that it would work. I also upgraded my kernel from
linux-image-3.2.0-1-amd64 to linux-image-3.2.0-4-amd64,
thinking
there might be an incompatibility in the non-free firmware.
* What was the outcome of this action?
Neither of these things worked. To workaround the problem (and
restore my Internet connection), I manually configured a wired
connection, and installed and loaded wicd and wicd-gtk. I then
removed the manual /etc/network/interfaces connection I had
made
for eth0.
* What outcome did you expect instead?
I expected NetworkManager to bring up my wireless connection,
and
not crash.
I installed network-manager-dbg hopefully to make it easier to
debug
I am attaching a set of strace output run against NetworkManager
(run as root). When NetworkManager segfaulted, strace did not
return, so I had to SIGKILL it. Let me know if there's a
better way
to capture this info. I'm also including a syslog excerpt which
shows NetworkManager, wpa_supplicant, and dhclient messages in
case
they are useful.
Since wicd works, I'm not inclined to believe it's the wireless
or
wired drivers, or wpa_supplicant, or any other piece of software
than network-manager.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.6.8-1
ii dpkg 1.16.10
ii isc-dhcp-client 4.2.4-6
ii libc6 2.17-1
ii libdbus-1-3 1.6.8-1
ii libdbus-glib-1-2 0.100.2-1
ii libgcrypt11 1.5.0-5
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libgnutls26 2.12.20-6
ii libgudev-1.0-0 175-7.2
ii libnl-3-200 3.2.7-4
ii libnl-genl-3-200 3.2.7-4
ii libnl-route-3-200 3.2.7-4
ii libnm-glib4 0.9.8.0-4
ii libnm-util2 0.9.8.0-4
ii libpolkit-gobject-1-0 0.105-3
ii libuuid1 2.20.1-5.3
ii lsb-base 4.1+Debian9
ii udev 175-7.2
ii wpasupplicant 1.0-3+b2
Versions of packages network-manager recommends:
ii crda 1.1.2-1
ii dnsmasq-base 2.66-1
ii iptables 1.4.18-1
ii modemmanager 0.5.2.0-2
ii policykit-1 0.105-3
ii ppp 2.4.5-5.1+b1
Versions of packages network-manager suggests:
ii avahi-autoipd 0.6.31-2
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=E8:9A:8F:F3:5B:D3,
[ifupdown]
managed=false
/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla
[Errno 13] Permission denied:
u'/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla'
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 0.9.8.0-5
Am 11.05.2013 12:56, schrieb Trey Blancher:
> Package: network-manager
> Followup-For: Bug #707177
>
> Dear Maintainer,
>
> I updated my kernel to the version below, and at least one
> network-manager-related package (e.g., network-manager-iodine), and the
> problem is no longer apparent. I can change the wireless network, and
> network-manager no longer disappears or segfaults.
>
> If the problem returns I'll post here again.
It was most likely the /etc/machine-id related problem, which was fixed
in 0.9.8.0-5
So let's mark this bug as fixed.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
