Bug 613735 - [abrt] crash in blueman-1.21-2.fc12: connection.py:584:msg_reply_handler:TypeError: sighandler() takes no arguments (2 given)
Summary: [abrt] crash in blueman-1.21-2.fc12: connection.py:584:msg_reply_handler:Type...
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Juan Manuel Rodriguez
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2323e1c6
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-12 18:00 UTC by Jonathan Pritchard
Modified: 2011-06-29 13:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 13:38:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (812 bytes, text/plain)
2010-07-12 18:00 UTC, Jonathan Pritchard
no flags Details

Description Jonathan Pritchard 2010-07-12 18:00:18 UTC
abrt 1.1.1 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/bin/blueman-manager
component: blueman
executable: /usr/bin/blueman-manager
package: blueman-1.21-2.fc12
reason: connection.py:584:msg_reply_handler:TypeError: sighandler() takes no arguments (2 given)
release: Fedora release 13 (Goddard)

connection.py:584:msg_reply_handler:TypeError: sighandler() takes no arguments (2 given)

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 584, in msg_reply_handler
    def msg_reply_handler(message):
TypeError: sighandler() takes no arguments (2 given)

Local variables in innermost frame:
reply_handler: <bound method ProxyObject._introspect_reply_handler of <ProxyObject wrapping <dbus._dbus.SessionBus (session) at 0x8b3f6bc> org.blueman.Applet / at 0x8b42dcc>>
message: <dbus.lowlevel.ErrorMessage object at 0x8897a90>
get_args_opts: {'byte_arrays': False, 'utf8_strings': True}
error_handler: <bound method ProxyObject._introspect_error_handler of <ProxyObject wrapping <dbus._dbus.SessionBus (session) at 0x8b3f6bc> org.blueman.Applet / at 0x8b42dcc>>

Comment 1 Jonathan Pritchard 2010-07-12 18:00:21 UTC
Created attachment 431228 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-01 14:08:13 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 3 Bug Zapper 2011-06-29 13:38:57 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Note You need to log in before you can comment on or make changes to this bug.