Bug 893373

Summary: [abrt] blueman-1.23-5.fc17: ManagerDeviceList.py:357:level_setup_event:TypeError: sighandler() takes no arguments (2 given)
Product: [Fedora] Fedora Reporter: Dmitriy <dergachevdv90>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d030863ceaf87e3d463375a79acda015bec1c1ee
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 06:04:40 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: executable
none
File: environ
none
File: smolt_data
none
File: core_backtrace none

Description Dmitriy 2013-01-09 09:19:40 UTC 
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.6.11-1.fc17.x86_64

backtrace:
:ManagerDeviceList.py:357:level_setup_event:TypeError: sighandler() takes no arguments (2 given)
:
:Traceback (most recent call last):
:  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py", line 235, in update
:    self.level_setup_event(row_ref, device, cinfo)
:  File "/usr/lib/python2.7/site-packages/blueman/gui/manager/ManagerDeviceList.py", line 357, in level_setup_event
:    rssi = float(cinfo.get_rssi())
:TypeError: sighandler() takes no arguments (2 given)
:
:Local variables in innermost frame:
:self: <ManagerDeviceList object at 0x1f7a050 (blueman+gui+DeviceList+DeviceList at 0x20120d0)>
:cinfo: <_blueman.conn_info object at 0x1f96c10>
:iter: <GtkTreeIter at 0x202cb40>
:rnd: <function rnd at 0x1f9d758>
:row_ref: <GtkTreeRowReference at 0x2185c80>
:device: <Device object at 0x1fa4190 (blueman+main+Device+Device at 0x2024f20)>
Comment 1 Dmitriy 2013-01-09 09:19:44 UTC 
Created attachment 675341 [details]
File: executable
Comment 2 Dmitriy 2013-01-09 09:19:46 UTC 
Created attachment 675342 [details]
File: environ
Comment 3 Dmitriy 2013-01-09 09:19:49 UTC 
Created attachment 675343 [details]
File: smolt_data
Comment 4 Dmitriy 2013-01-09 09:19:53 UTC 
Created attachment 675344 [details]
File: core_backtrace
Comment 5 Fedora End Of Life 2013-07-04 01:31:56 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:04:44 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.