Bug 539756
| Summary: | [abrt] crash detected in blueman-1.21-2.fc12 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | meme23 | ||||||
| Component: | blueman | Assignee: | Juan Manuel Rodriguez <nushio> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 19 | CC: | affix, aselene, bugzillarh, cpanceac, cupp, djo2, em3epling, fhthagn, forthommel, froggle29631, hanzhin.stas, helloarif7, ironmiky, jschilen, kbsingh, keijo.hautala, mauro_inter, mishunika, morten, mtk, nushio, redhat-bugzilla, samy21, skaturn, snhemanthm, stajem, tcallawa, vinnitrash, virum | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:97506e65 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-12-09 23:09:21 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
meme23
2009-11-20 23:53:36 UTC
Created attachment 372643 [details]
File: backtrace
To fix, just remove /tmp/blueman* with blueman-applet disabled. After that, all sould work correctly. I actually didn't have any such folders or files under /tmp but oddly it's working right now(I had switched over to another manager until this could be worked out so I didn't know until I just checked) Removing the /tmp/blueman* did fix the problem for me. I no longer have any problems with Blueman crashing. Still think this is a bug though....... mainly because it requires a workaround to fix the problem. How to reproduce ----- 1. this problem occure during system booting 2. 3. How to reproduce ----- 1. Boot laptop without BT dongle 2. Login 3. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Happens at gnome startup. 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. 2. 3. Comment ----- Updated from F11 to F12 and I start getting this crash when starting computer. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- Started as applet by Session Manager Comment ----- blueman-applet was started by gnome-session-manager Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- This happens everytime I boot my machine. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Login to Gnome via GDM 2. 3. Comment ----- This machine is running F14/Alpha, then yum updated every few days. This specific crash happens after all updates for 2010-09-21 are applied. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I login to my gnome desktop 2. I do anithing 3. Two Bluetooth manager is installed on my Fedora (Blueman, default bluetooth manager) This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I deleted /tmp/blueman-applet-500 file and I have no problem. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Happens on login 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Logging in, happens every time 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Happens on login Comment ----- I created a simple patch that stops the error from occuring blueman-applet wil load after using this patch Created attachment 470601 [details]
Patch file to work around the error.
This patch is caused by the Process ID of blueman-applet using try: to handle the error stops the bug. This also makes error handling alot cleaner and will not show up a python error and crash. Using this patch does not affect the way blueman-applet functions.
Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start program 2. Start typing 3. Program crashes Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Lors du démarrage du portable. 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Démarrage 2. 3. Package: blueman-1.21-6.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. 2. 3. immediately after login Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Happens frequently after reboot on Thinkpad T510. I do not use Bluetooth or blueman-applet at all, but the machine has a Bluetooth radio and thus blueman-applet starts automatically before failing. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up the computer. 2. 3. Comment ----- Booted up the computer. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up the computer. 2. 3. Comment ----- Booted up the computer. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Comment ----- Booted the computer. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Comment ----- Booted the computer. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. booted computer 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Comment ----- This computer does not even have a Bluetooth adaptor. I did not specifically install Blueman -- it came with the distro. I'm surprised it cannot detect the absence of a Bluetooth adaptor and merely exit gracefully. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Boot the computer 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted the computer. 2. 3. Comment ----- Blueman crashes on boot up. When I report the failure using ABRT, the completed report remains listed in ABRT ... and Blueman does not crash. This time, I left the report in ABRT for three days and through numerous boot up sequences Blueman did not crash. As soon as I clear the completed crash report from ABRT, then Blueman crashes on the next boot up. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Boot the computer. 2. 3. Comment ----- As long as the last-submitted report remains in ABRT, everything is fine. When I delete the completed (submitted) report, Blueman crashes on the next system boot up. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start fedora 2.log in 3. Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. mm100 headset disconnects (?) 2. try to pair/connect 3. boom This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 Hi. I'm closing this bug as Blueman has been retired from Fedora. If you wish to file a bug against upstream, a new Blueman fork has been created in this github repository. [1] I apologize for the inconvenience. [1] https://github.com/cschramm/blueman |