Bug 910828 - [abrt] NetworkManager-0.9.6.4-3.fc17: handle_ip_config_timeout: Process /usr/sbin/NetworkManager was killed by signal 6 (SIGABRT)
Summary: [abrt] NetworkManager-0.9.6.4-3.fc17: handle_ip_config_timeout: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 854073
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9105387b145ded493f46c77981b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-13 16:30 UTC by bp2626
Modified: 2013-06-07 15:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-07 15:42:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: environ (137 bytes, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: var_log_messages (10.53 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: backtrace (15.98 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: limits (1.29 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: cgroup (174 bytes, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: smolt_data (2.81 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: executable (24 bytes, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: maps (9.64 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: dso_list (3.17 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: build_ids (1.48 KB, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: proc_pid_status (748 bytes, text/plain)
2013-02-13 16:30 UTC, bp2626
no flags Details
File: open_fds (741 bytes, text/plain)
2013-02-13 16:31 UTC, bp2626
no flags Details

Description bp2626 2013-02-13 16:30:30 UTC
Version-Release number of selected component:
NetworkManager-0.9.6.4-3.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: handle_ip_config_timeout
kernel:         3.7.3-101.fc17.i686

truncated backtrace:
:Thread no. 1 (3 frames)
: #5 handle_ip_config_timeout at nm-device-wifi.c:3015
: #6 real_act_stage4_ip6_config_timeout at nm-device-wifi.c:3086
: #7 nm_device_activate_ip6_config_timeout at nm-device.c:2620

Potential duplicate bug: 854073

Comment 1 bp2626 2013-02-13 16:30:33 UTC
Created attachment 696894 [details]
File: environ

Comment 2 bp2626 2013-02-13 16:30:35 UTC
Created attachment 696895 [details]
File: var_log_messages

Comment 3 bp2626 2013-02-13 16:30:37 UTC
Created attachment 696896 [details]
File: backtrace

Comment 4 bp2626 2013-02-13 16:30:42 UTC
Created attachment 696897 [details]
File: limits

Comment 5 bp2626 2013-02-13 16:30:44 UTC
Created attachment 696898 [details]
File: cgroup

Comment 6 bp2626 2013-02-13 16:30:46 UTC
Created attachment 696899 [details]
File: smolt_data

Comment 7 bp2626 2013-02-13 16:30:47 UTC
Created attachment 696900 [details]
File: executable

Comment 8 bp2626 2013-02-13 16:30:50 UTC
Created attachment 696901 [details]
File: maps

Comment 9 bp2626 2013-02-13 16:30:52 UTC
Created attachment 696902 [details]
File: dso_list

Comment 10 bp2626 2013-02-13 16:30:54 UTC
Created attachment 696903 [details]
File: build_ids

Comment 11 bp2626 2013-02-13 16:30:57 UTC
Created attachment 696904 [details]
File: proc_pid_status

Comment 12 bp2626 2013-02-13 16:31:03 UTC
Created attachment 696905 [details]
File: open_fds

Comment 13 Joshua Kordani 2013-03-11 10:56:01 UTC
updated the password to a wpa2 network, connected, worked for a few seconds, then crash, everything came back up fine i think.

backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
core_backtrace: 
crash_function: handle_ip_config_timeout
executable:     /usr/sbin/NetworkManager
kernel:         3.8.2-105.fc17.i686
package:        NetworkManager-0.9.6.4-3.fc17
reason:         Process /usr/sbin/NetworkManager was killed by signal 6 (SIGABRT)
uid:            0

Comment 14 Dan Williams 2013-06-07 15:42:37 UTC

*** This bug has been marked as a duplicate of bug 854073 ***


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