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
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.)
In the absence of further information I'm closing this as WORKSFORME. Please reopen, or open a new bug, if there are further problems.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.