abrt detected a crash. Attached file: backtrace cmdline: /usr/bin/python /usr/bin/blueman-applet component: python executable: /usr/bin/python kernel: 2.6.31.5-127.fc12.i686.PAE package: python-2.6.2-2.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 373491 [details] File: backtrace
Thank you for reporting this bug. How reproducable is this problem? If you run the program from a terminal, is an error message printed? What version of blueman do you have installed? Looking at the backtrace, it looks like the problem occurred in the program's single thread in Py_DecRef Reassigning component from "python" to "blueman"
Dear Dave, here is the short summary about the same problem: 1. the versions: rpm -qa blue* bluez-gstreamer-4.58-1.fc12.i686 bluecurve-cursor-theme-8.0.2-5.fc12.noarch bluez-compat-4.58-1.fc12.i686 bluez-hcidump-1.42-4.fc12.i686 bluez-alsa-4.58-1.fc12.i686 blueman-1.21-2.fc12.i686 bluez-libs-4.58-1.fc12.i686 bluez-cups-4.58-1.fc12.i686 bluez-4.58-1.fc12.i686 2. if I run blueman from terminal, it works without any error: blueman-applet Loading configuration plugins Using gconf config backend Using gconf config backend _________ Load (/usr/bin/blueman-applet:117) ['PowerManager', 'Indicator', 'DiscvManager', 'NMIntegration', 'NetUsage', 'KillSwitch', 'NMDUNSupport', 'Menu', 'PulseAudio', 'PPPSupport', 'StatusIcon', 'NMMonitor', 'AuthAgent', 'Headset', 'TransferService', 'NMPANSupport', 'DBusService', 'DhcpClient', 'StandardItems', 'SerialManager', 'Networking', 'RecentConns'] _________ ..... 3. the problem appears at the beginning of the GNOME session, when the applet starts automatically.
Lev: thanks for the information; looks like another duplicate of bug 536786, but that should have been fixed in blueman-1.21-2, which comment #3 suggests you already have.
Hello Dave, I have blueman-1.21-2 but I still see the same crash of python+blueman at the beginning of the session. I have posted the latest crash trace with abrt to here: https://bugzilla.redhat.com/show_bug.cgi?id=542995
*** Bug 546489 has been marked as a duplicate of this bug. ***
*** Bug 553191 has been marked as a duplicate of this bug. ***
*** Bug 577588 has been marked as a duplicate of this bug. ***
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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.