Bug 573397

Summary: [abrt] crash in gnome-bluetooth-2.28.6-2.fc12: Process /usr/bin/bluetooth-sendto was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Chance Brohm <chancebrohm>
Component: gnome-bluetoothAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:df00784511e0b6be082e12e7bb7b5467590fa4f7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 08:52:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Chance Brohm 2010-03-14 16:26:02 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: bluetooth-sendto
comment: from the context menu for Bluetooth in the Notification Area, I chose "send files to device..." then selected 2 .zip files from ~/Downloads, clicked Open...then chose a Win7.x86_64/BroadcomBT target. That system indicated a brief connection, so brief that it could not recognize (al least did not report) the profile/purpose for the Fedora system's connection request - abrt's red alam light appeared almost immediately after I clicked send
component: gnome-bluetooth
executable: /usr/bin/bluetooth-sendto
kernel: 2.6.32.9-70.fc12.x86_64
package: gnome-bluetooth-2.28.6-2.fc12
rating: 4
reason: Process /usr/bin/bluetooth-sendto was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Chance Brohm 2010-03-14 16:26:04 UTC 
Created attachment 400005 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:52:00 UTC 

*** This bug has been marked as a duplicate of bug 556953 ***
Comment 3 Karel Klíč 2010-05-25 08:52:00 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #556953.

Sorry for the inconvenience.