registry team mailing list archive

[Bug Watch Updater <576673@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 2 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=28006.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-05-06T15:30:58+00:00 Cristian Aravena Romero wrote:

Open bug in Launchpad
https://bugs.launchpad.net/bugs/576673

"See .xsession.errors:

ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: signal_handler() takes exactly 1 argument (2 given)
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: signal_handler() takes exactly 1 argument (2 given)
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: signal_handler() takes exactly 1 argument (2 given)
** (update-notifier:2007): DEBUG: Skipping reboot required"


.xsession-errors: http://launchpadlibrarian.net/47964319/.xsession-errors

Reply at: https://bugs.launchpad.net/dbus/+bug/576673/comments/0

------------------------------------------------------------------------
On 2010-05-07T03:18:56+00:00 Simon McVittie wrote:

Someone has defined a function signal_handler() that takes one argument,
and connected it to some signal, but that signal was then received with
two arguments. Whatever module defines signal_handler() is probably out
of sync with the D-Bus API of whatever module emits the signal.

What else could dbus-python do about this, other than logging a warning
and carrying on?

(There's a genuine dbus-python bug here too, which is that it doesn't
know the process name, so it can't log it.)

Reply at: https://bugs.launchpad.net/dbus/+bug/576673/comments/3


** Changed in: dbus
       Status: Unknown => Confirmed

** Changed in: dbus
   Importance: Unknown => Medium

-- 
Message in .xsession-errors - ERROR:dbus.connection:Exception in handler for D-Bus signal
https://bugs.launchpad.net/bugs/576673
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for D-Bus.