Bug 694886

Summary: [abrt] blueman-1.21-8.fc14: Functions.py:281:check_single_instance:OSError: [Errno 2] No such file or directory: '/tmp/blueman-applet-500'
Product: [Fedora] Fedora Reporter: Mark T. Kennedy <mtk>
Component: bluemanAssignee: Juan Manuel Rodriguez <nushio>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bugzilla.redhat, javadieh.msd, nushio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d1702c7c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:54:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Mark T. Kennedy 2011-04-08 18:27:04 UTC
abrt version: 1.1.17
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/blueman-applet
component: blueman
executable: /usr/bin/blueman-applet
kernel: 2.6.35.12-88.fc14.x86_64
package: blueman-1.21-8.fc14
reason: Functions.py:281:check_single_instance:OSError: [Errno 2] No such file or directory: '/tmp/blueman-applet-500'
release: Fedora release 14 (Laughlin)
time: 1302286678
uid: 500

backtrace
-----
Functions.py:281:check_single_instance:OSError: [Errno 2] No such file or directory: '/tmp/blueman-applet-500'

Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 364, in <module>
    BluemanApplet()
  File "/usr/bin/blueman-applet", line 297, in __init__
    check_single_instance("blueman-applet")
  File "/usr/lib/python2.7/site-packages/blueman/Functions.py", line 281, in check_single_instance
    os.remove(lockfile)
OSError: [Errno 2] No such file or directory: '/tmp/blueman-applet-500'

Local variables in innermost frame:
isrunning: False
event_time: 0
f: <closed file '/tmp/blueman-applet-500', mode 'r' at 0x24adc00>
pid: 3508
id: 'blueman-applet'
handler: <function handler at 0x2560b90>
lockfile: '/tmp/blueman-applet-500'
unhide_func: None

How to reproduce
-----
1. fresh boot
2. turned on mm100 headset
3. entered pairing password
4. it connected headset + audio
5. disconnected both
6. reconnected audio

Comment 1 Mark T. Kennedy 2011-04-08 18:27:06 UTC
Created attachment 490851 [details]
File: backtrace

Comment 2 Matt 2011-04-25 21:58:26 UTC
Package: blueman-1.21-8.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
Fresh install of Fedora 12 upgraded to 15

Comment 3 masoudjavadieh 2011-06-16 18:07:39 UTC
Package: blueman-1.21-8.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.trying to use evdev instead kbd & mouse driver in Xorg.conf and making AutoAddDivce off in one seat of two
2.
3.

Comment 4 Fedora End Of Life 2012-08-16 14:54:56 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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