Bug 693446 - [abrt] NetworkManager-gnome-1:0.8.997-4.git20110325.fc15: __libc_message: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] NetworkManager-gnome-1:0.8.997-4.git20110325.fc15: __libc_message: Pro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fc21b402e3ff20eb31351d46443...
: 691989 692043 692611 692682 693197 693463 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 17:31 UTC by drewskiwooskie
Modified: 2011-04-11 15:32 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-0.8.998-2.git20110406.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-11 15:32:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (24.75 KB, text/plain)
2011-04-04 17:31 UTC, drewskiwooskie
no flags Details

Description drewskiwooskie 2011-04-04 17:31:46 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 25339 bytes
cmdline: nm-applet
component: NetworkManager
Attached file: coredump, 77971456 bytes
crash_function: __libc_message
executable: /usr/bin/nm-applet
kernel: 2.6.38.2-9.fc15.x86_64
package: NetworkManager-gnome-1:0.8.997-4.git20110325.fc15
rating: 4
reason: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1301938273
uid: 500

How to reproduce
-----
1.I was not doing anything that I know of that would cause this. I opened a file in vim and this popped up
2.
3.

Comment 1 drewskiwooskie 2011-04-04 17:31:48 UTC
Created attachment 489818 [details]
File: backtrace

Comment 2 Dan Williams 2011-04-06 15:24:41 UTC
*** Bug 691989 has been marked as a duplicate of this bug. ***

Comment 3 Dan Williams 2011-04-06 15:25:07 UTC
*** Bug 692611 has been marked as a duplicate of this bug. ***

Comment 4 Dan Williams 2011-04-06 15:31:21 UTC
*** Bug 693197 has been marked as a duplicate of this bug. ***

Comment 5 Dan Williams 2011-04-06 15:34:38 UTC
*** Bug 693463 has been marked as a duplicate of this bug. ***

Comment 6 Dan Williams 2011-04-06 15:39:16 UTC
*** Bug 692043 has been marked as a duplicate of this bug. ***

Comment 7 Dan Williams 2011-04-06 15:39:54 UTC
*** Bug 692682 has been marked as a duplicate of this bug. ***

Comment 8 Dan Williams 2011-04-06 16:17:11 UTC
This bug is fixed by the following updates:

F15: https://admin.fedoraproject.org/updates/NetworkManager-0.8.998-1.fc15

F14 update will follow.

Comment 9 drewskiwooskie 2011-04-06 16:55:03 UTC
has not happened again since updating to that version:
rpm -q NetworkManager
NetworkManager-0.8.998-1.fc15.x86_64

Comment 10 Fedora Update System 2011-04-06 19:07:11 UTC
NetworkManager-0.8.998-2.git20110406.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/NetworkManager-0.8.998-2.git20110406.fc15

Comment 11 Fedora Update System 2011-04-07 02:19:47 UTC
Package NetworkManager-0.8.998-2.git20110406.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.8.998-2.git20110406.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/NetworkManager-0.8.998-2.git20110406.fc15
then log in and leave karma (feedback).

Comment 12 niels 2011-04-07 08:46:18 UTC
Package: NetworkManager-gnome-1:0.8.3.998-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. coldboot
2.
3.

Comment 13 Fedora Update System 2011-04-11 15:32:26 UTC
NetworkManager-0.8.998-2.git20110406.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.