Bug 691736 - [abrt] control-center-2.91.93-1.fc15: nm_device_refresh_device_ui: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Summary: [abrt] control-center-2.91.93-1.fc15: nm_device_refresh_device_ui: Process /u...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:968d4d0c7444679af63b28d31ed...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 11:01 UTC by Aaron Sowry
Modified: 2012-02-02 09:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 09:33:12 UTC
Type: ---

Attachments (Terms of Use)
File: event_log (20.15 KB, text/plain)
2011-03-29 11:01 UTC, Aaron Sowry 		no flags Details
File: maps (72.32 KB, text/plain)
2011-03-29 11:01 UTC, Aaron Sowry 		no flags Details
File: dsos (56.67 KB, text/plain)
2011-03-29 11:01 UTC, Aaron Sowry 		no flags Details
File: backtrace (32.91 KB, text/plain)
2011-03-29 11:01 UTC, Aaron Sowry 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Aaron Sowry 2011-03-29 11:01:46 UTC 
abrt version: 2.0.0
executable: /usr/bin/gnome-control-center
cmdline: gnome-control-center network
component: control-center
crash_function: nm_device_refresh_device_ui
kernel: 2.6.38.2-8.fc15.x86_64
package: control-center-2.91.93-1.fc15
reason: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
uid: 500
architecture: x86_64
username: aaron
os_release: Fedora release 15 (Lovelock)
time: 1301395714
rating: 4

Text file: event_log, 20630 bytes
Binary file: smaps, 333223 bytes
Binary file: coredump, 28708864 bytes
Text file: maps, 74055 bytes
Text file: dsos, 58031 bytes
Text file: backtrace, 33695 bytes

comment
-----
1) Use bluetooth-wizard to attempt to connect to DUN on a mobile phone via bluetooth. In this case, NM could not complete the connection due to a restrictive selinux policy.

2) Open 'Network settings' from NM

3) Click on 'bluetooth'
Comment 1 Aaron Sowry 2011-03-29 11:01:49 UTC 
Created attachment 488410 [details]
File: event_log
Comment 2 Aaron Sowry 2011-03-29 11:01:51 UTC 
Created attachment 488411 [details]
File: maps
Comment 3 Aaron Sowry 2011-03-29 11:01:54 UTC 
Created attachment 488412 [details]
File: dsos
Comment 4 Aaron Sowry 2011-03-29 11:01:57 UTC 
Created attachment 488413 [details]
File: backtrace
Comment 5 Richard Hughes 2012-02-02 09:33:12 UTC 
Is this fixed on F16? It seems to work for me.
Comment 6 Aaron Sowry 2012-02-02 09:57:30 UTC 
I couldn't reproduce this on F16 just now.
Note You need to log in before you can comment on or make changes to this bug.