Bug 591477 - [abrt] crash in gnome-bluetooth-2.30.0-1.fc13: raise: Process /usr/bin/bluetooth-wizard was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-bluetooth-2.30.0-1.fc13: raise: Process /usr/bin/blueto...
Status: CLOSED DUPLICATE of bug 590666
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth   
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:25e9419fdeec3003fd02771b2ba...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 11:11 UTC by Bostjan
Modified: 2010-05-12 12:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-12 12:51:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (10.79 KB, text/plain)
2010-05-12 11:11 UTC, Bostjan 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Bostjan 2010-05-12 11:11:39 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: bluetooth-wizard
component: gnome-bluetooth
crash_function: raise
executable: /usr/bin/bluetooth-wizard
global_uuid: 25e9419fdeec3003fd02771b2ba8fe795461390c
kernel: 2.6.33.3-85.fc13.i686.PAE
package: gnome-bluetooth-2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/bluetooth-wizard was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Opened "Setup a new device" from bluetooth applet
2. Chose my mobile phone (Nokia 5800)
3. After entering the pin on the phone I checked "Access the internet using this device" and it crashed immediatelly
Comment 1 Bostjan 2010-05-12 11:11:42 UTC 
Created attachment 413396 [details]
File: backtrace
Comment 2 Bastien Nocera 2010-05-12 12:51:41 UTC 

*** This bug has been marked as a duplicate of bug 590666 ***
Note You need to log in before you can comment on or make changes to this bug.