Bug 697299 - [abrt] NetworkManager-gnome-1:0.8.3.999-2.git20110414.fc14: magazine_chain_pop_head: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] NetworkManager-gnome-1:0.8.3.999-2.git20110414.fc14: magazine_chain_po...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fcc86644f70ba77502d034a8f58...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 15:38 UTC by Mads Kiilerich
Modified: 2012-10-15 10:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:01:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (36.00 KB, text/plain)
2011-04-17 15:38 UTC, Mads Kiilerich
no flags Details
abrt screenshot (195.38 KB, image/png)
2012-10-10 02:41 UTC, Mikhail
no flags Details

Description Mads Kiilerich 2011-04-17 15:38:11 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 36859 bytes
cmdline: nm-applet --sm-disable
component: NetworkManager
Attached file: coredump, 12369920 bytes
crash_function: magazine_chain_pop_head
executable: /usr/bin/nm-applet
kernel: 2.6.35.12-88.fc14.i686.PAE
package: NetworkManager-gnome-1:0.8.3.999-2.git20110414.fc14
rating: 3
reason: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I had problems connecting to wireless network after suspend/resume, restarted NetworkManager, and then ...
time: 1303049078
uid: 500

Comment 1 Mads Kiilerich 2011-04-17 15:38:14 UTC
Created attachment 492719 [details]
File: backtrace

Comment 2 Milos Jakubicek 2011-04-20 17:13:39 UTC
Package: NetworkManager-gnome-1:0.8.3.999-2.git20110414.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
on suspend to ram

Comment 3 Milos Jakubicek 2011-04-21 05:04:00 UTC
Package: NetworkManager-gnome-1:0.8.3.999-2.git20110414.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
on suspend to ram

Comment 4 Igor Katalnikov 2011-04-23 09:23:17 UTC
Package: NetworkManager-gnome-0.8.998-3.git20110419.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Tryong create permanent wireless connection

Comment 5 Chunnayya Munnayya 2011-05-07 01:21:44 UTC
Package: NetworkManager-gnome-1:0.8.4-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Attempted to connect to Mobile AP (WiFi)
2. Crash
3.

Comment 6 John 'Warthog9' Hawley 2011-05-22 04:24:02 UTC
Package: NetworkManager-gnome-1:0.8.4-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Attempt to connect to wap
2. nothing comes up
3. restart NetworkManager
4. applet crashes

Comment 7 kxra 2011-06-05 15:30:52 UTC
Package: NetworkManager-gnome-1:0.8.4-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Unknown

Comment 8 Jirka Klimes 2011-06-06 08:00:25 UTC
Please install debuginfo package, so we can get better backtrace:
# debuginfo-install NetworkManager

Is anybody able to reproduce that at will?

Comment 9 abrt-bot 2012-03-30 15:30:52 UTC
Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 instead of component NetworkManager. You might want to inspect the backtrace from the bug listed below to find out the correct component.

Bug #658086 from component empathy was found to be similar to this bug.

This comment is automatically generated.

Comment 10 Fedora End Of Life 2012-08-16 13:01:13 UTC
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

Comment 11 Mikhail 2012-10-07 17:25:59 UTC
Also occurs in Fedora 18

Comment 12 Mikhail 2012-10-10 02:41:14 UTC
Created attachment 624451 [details]
abrt screenshot

Comment 13 piio 2012-10-15 10:10:17 UTC
I have this same problem, after installing 0.9.7.0-4.git20121004.fc18 - NetworkManager keeps crashing and restarting.


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