Bug 843668
| Summary: | [abrt] gnome-bluetooth-3.4.2-1.fc17: handle_method_call: Process /usr/bin/bluetooth-sendto was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | balamahendran | ||||||||
| Component: | gnome-bluetooth | Assignee: | Bastien Nocera <bnocera> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | barthes.benoit, bnocera, lexus11985, skkd.h4k1n9, stas.lysenko, thunderbirdtr, turquino | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:46ab4ff516fb3004fcd6a30b0a9572aad7a2400b | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-07-31 20:52:14 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
balamahendran
2012-07-27 01:14:09 UTC
Created attachment 600647 [details]
File: backtrace
Created attachment 600648 [details]
File: maps
Created attachment 600649 [details]
File: dso_list
I was trying to send file to my android-based smartphone. I have accidentally rejected file on my phone, so I clicked on "retry" on File Transfer dialog. backtrace_rating: 4 Package: gnome-bluetooth-3.4.2-1.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) I was try to send file to my phone (android model ) and when I get error and click the "Try Again" It will be crash and so on. backtrace_rating: 4 Package: gnome-bluetooth-3.6.0-1.fc18 Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow) After pairing my Eee PC 1000H with my Google Nexus 7, and sending the first file to the Nexus ... the transfer stopped - and this error message showed up backtrace_rating: 4 Package: gnome-bluetooth-3.6.1-2.fc18 OS Release: Fedora release 18 (Spherical Cow) I was lessening music via bluetooth (Rhythmbox), so at the same time I sent a .mp3 file to my Android (S3), after that the laptop can't reproduce any sound, the sound was died. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |