abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 20687 bytes cmdline: /usr/bin/nm-connection-editor component: NetworkManager Attached file: coredump, 15974400 bytes crash_function: __libc_message executable: /usr/bin/nm-connection-editor kernel: 2.6.35.11-83.fc14.x86_64 package: NetworkManager-gnome-1:0.8.3.998-2.fc14 rating: 4 reason: Process /usr/bin/nm-connection-editor was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1301533607 uid: 500 How to reproduce ----- 1. Created New Wireless Network 2. Edited Wireless Security settings 3. Changed to WPA/Personal
Created attachment 488962 [details] File: backtrace
*** Bug 691576 has been marked as a duplicate of this bug. ***
The "Automatic Bug Reporting Tool" did not mark this as a duplicate to any other bug - it stated the bug as new when I was submitting.
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Resume from suspend 2. Connecting to different network (prev home, now work) 3. nm-applet crashes 4. /etc/resolv.conf doesn't refresh for new network
*** Bug 694319 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > The "Automatic Bug Reporting Tool" did not mark this as a duplicate to any > other bug - it stated the bug as new when I was submitting. Yeah, even so it doesn't always get it right. This bug is something I've seen before and the stack from yours are virtually identical to the duped bug.
*** Bug 694722 has been marked as a duplicate of this bug. ***
*** Bug 694717 has been marked as a duplicate of this bug. ***
*** Bug 683056 has been marked as a duplicate of this bug. ***
*** Bug 682142 has been marked as a duplicate of this bug. ***
*** Bug 682320 has been marked as a duplicate of this bug. ***
*** Bug 688081 has been marked as a duplicate of this bug. ***
What appears to be going on here is that something is double-freeing the NMSetting object's priv->name field. That name is used in a few places, but should never be freed except by the NMSetting's finalize() function. Perhaps we're inadvertently freeing it somewhere in the code...
Something interesting is that it's always an NMSettingWireless that gets its name double-freed, which might indicate that the applet's wifi code is doing something odd.
I can't seem to reproduce this easily, at least valgrinding nm-applet and changing the connection in GConf using nm-connection-editor...
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- crashed somtimes when trying to connect to wlanX network. usb wl device Bus 001 Device 004: ID 0846:9030 NetGear, Inc. using ath9k_htc driver with firmware htc_9271.fw
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I used the computer as normal. 2. The WIFI kernel module crashed (see other report) 3. I was editiing one of the same-named network profiles while the applet crashed. Comment ----- Had problems to connect to WLAN and the WIFI driver crashed. Reported that with this Automatic But Reporting Tool earlier.
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Connected to my WLAN after I refreshed the WLAN Routers Config (because w/o I could not successfully connect) 2. Connect did work, I started to do some work. 3. Crash Comment ----- I have the feeling that this is related to my yesterdays crash. I recently booted the machine.
It looks like that I can trigger the crash somehow. Second day in follow. Is there anything that I can run in the background when trying to crash the applet again?
What would really help is if you can come with a reliable reproducer ;) One thing you can try is to run nm-applet in gdb and possible also set MALLOC_CHECK_=3 for aborting when memory problem occurs: $ gdb /usr/bin/nm-applet ... (gdb) set env MALLOC_CHECK_=3 (gdb) r
Created attachment 493251 [details] First run with gdb while trying to find a reproduce pattern. I could now crash it by using the applet (connecting to a profile, disconnecting , manually connecting, cancelling the password window) and the network settings in parallel (editing and renaming the profile currently connecting to). That crashed it after some actions. Sorry for the still imprecise description.
*** Bug 696450 has been marked as a duplicate of this bug. ***
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Click on NetworkManager icon 2. add a new hidden wireless SSID network 3. activate it Comment ----- All I was doing was adding another hidden wireless SSID into NetworkManager.
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.rmmod wl 2.modprobe wl 3.
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- Connected to WLAN over AP, established an sftp connection on a client and played a video in mplayer on the client.
Created attachment 494375 [details] new backtrace
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. After wireless drop-out & re-establish (happens frequesntly) 2. 3. Comment ----- nothing
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. some internet connection problems 2. connection to the router was ok but in one moment nm creashed and ping to router was ok 3. only reboot was ok
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just conect to wlan 2.then crash 3.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping