Bug 912346

Summary: [abrt] blueman-1.23-5.fc17: Functions.py:302:check_single_instance:OSError: [Errno 2] Arquivo ou diretório não encontrado: '/home/FabinhoBallack13/.cache/blueman-manager-1000'
Product: [Fedora] Fedora Reporter: fabioballack_13
Component: bluemanAssignee: Juan Manuel Rodriguez <nushio>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: nushio
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:24a7c332ac68c66b92ecbce7bc9b6bc21fa99908
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 06:06:06 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: environ
none
File: executable
none
File: smolt_data
none
File: core_backtrace none

Description fabioballack_13 2013-02-18 13:39:43 UTC
Description of problem:
It happens after someone has tried to pair with my notebook's bluetooth.

Version-Release number of selected component:
blueman-1.23-5.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        /usr/bin/python /usr/bin/blueman-manager
kernel:         3.7.6-102.fc17.i686

backtrace:
:Functions.py:302:check_single_instance:OSError: [Errno 2] Arquivo ou diretório não encontrado: '/home/FabinhoBallack13/.cache/blueman-manager-1000'
:
:Traceback (most recent call last):
:  File "/usr/bin/blueman-manager", line 301, in <module>
:    Blueman()
:  File "/usr/bin/blueman-manager", line 75, in __init__
:    check_single_instance("blueman-manager", do_present)
:  File "/usr/lib/python2.7/site-packages/blueman/Functions.py", line 302, in check_single_instance
:    os.remove(lockfile)
:OSError: [Errno 2] Arquivo ou diretório não encontrado: '/home/FabinhoBallack13/.cache/blueman-manager-1000'
:
:Local variables in innermost frame:
:isrunning: False
:event_time: 3180717
:f: <closed file '/home/FabinhoBallack13/.cache/blueman-manager-1000', mode 'r' at 0x9666758>
:pid: 2994
:id: 'blueman-manager'
:handler: <function handler at 0x9681bc4>
:lockfile: '/home/FabinhoBallack13/.cache/blueman-manager-1000'
:unhide_func: <function do_present at 0x966da3c>

Comment 1 fabioballack_13 2013-02-18 13:39:46 UTC
Created attachment 698880 [details]
File: environ

Comment 2 fabioballack_13 2013-02-18 13:39:49 UTC
Created attachment 698881 [details]
File: executable

Comment 3 fabioballack_13 2013-02-18 13:39:52 UTC
Created attachment 698882 [details]
File: smolt_data

Comment 4 fabioballack_13 2013-02-18 13:39:57 UTC
Created attachment 698883 [details]
File: core_backtrace

Comment 5 Fedora End Of Life 2013-07-04 01:32:25 UTC
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.

Comment 6 Fedora End Of Life 2013-08-01 06:06:09 UTC
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.