Opened 10 years ago

Closed 10 years ago

#1365 closed defect (duplicate)

dbus notification TB

Reported by: kaalh@… Owned by: asterix
Priority: high Milestone:
Component: None Version: hg
Severity: major Keywords:
Cc: Blocked By:
Blocking: OS:

Description

TB occurs on the first notification, and then gajim doesn't display new messages, but still store them in history.
gajim revision 5065 + ubuntu dapper

Traceback (most recent call last):
  File "gajim.py", line 1227, in process_connections
    gajim.mutex_events_for_ui.lock(self.exec_event, account)
  File "/usr/lib/python2.4/mutex.py", line 41, in lock
    function(argument)
  File "gajim.py", line 1212, in exec_event
    self.handlers[ev[0]](account, ev[1])
  File "gajim.py", line 358, in handle_event_notify
    notify.notify(_('Contact Signed In'), jid, account)
  File "/home/kaalh/gajim/gajim/src/notify.py", line 56, in notify
    DesktopNotification(event_type, jid, account, msg_type, file_props)
  File "/home/kaalh/gajim/gajim/src/notify.py", line 218, in __init__
    [dbus.String(path)], {'default': 0}, [''], True, dbus.UInt32(timeout))
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 67, in __call__
    iter.append_strict(arg, sig)
  File "dbus_bindings.pyx", line 1012, in dbus_bindings.MessageIter.append_strict
  File "dbus_bindings.pyx", line 1179, in dbus_bindings.MessageIter.append_string
AttributeError: 'Byte' object has no attribute 'encode'

Change History (1)

comment:1 Changed 10 years ago by nk

  • Resolution set to duplicate
  • Status changed from new to closed

c #1347, apparently they broke their API!!!!!!

Note: See TracTickets for help on using tickets.