[Karmic] Gajim fails to work with indicator applet

I've changed
/usr/share/gajim/src/notify.py:355 : indicator = indicate.IndicatorMessage() -> indicator = indicate.Indicator()
Error message no longer appears, a popup arises, but the applet still doesn't indicate anything.

Got this too after updating to latest karmic.

I have exactly the same error message.

I can confirm this error too

I can confirm this error too (gajim 0.12.5-0ubuntu1)

It has been fixed upstream already, see the bug URL I've just linked.
Could anybody ensure this fix will be integrated for the Karmic final release?

BTW, since this bug was because of an API change in the python-indicate package, developers ask for a way to get a module version number (from inside Python, of course).

Gajim does not put its icon into the notification area (and when the roster is closed, gajim quits) - is is the same bug or another one?

Sergey V. Udaltsov, I doubt it. And I cannot reproduce your issue. Try fixing /usr/share/gajim/src/notify.py (see above) and if it doesn't solve problem open a new bug.

Actually it seems it has nothing to do with indication. Probably will open another bug

There is a patch available upstream, I've prepared updated packages for it, I will upload them if nobody has objections

This bug was fixed in the package gajim - 0.12.5-0ubuntu3

---------------
gajim (0.12.5-0ubuntu3) lucid; urgency=low

  * Fix indicate support (LP: #433495)
  * Bump Standards-Version to 3.8.3
 -- Laurent Bigonville <email address hidden> Thu, 05 Nov 2009 14:17:31 +0100

Is there a debdiff against karmic-proposed MOTU-SRU should review?

Looks good; ACK from motu-sru!

I built -0ubuntu3 for Karmic from source and confirm that this fixes the problem and I found no regressions.

Accepted gajim into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I can confirm, that the new packages solves the problem.

This bug was fixed in the package gajim - 0.12.5-0ubuntu2.1

---------------
gajim (0.12.5-0ubuntu2.1) karmic-proposed; urgency=low

  * Fix indicate support (LP: #433495)
 -- Laurent Bigonville <email address hidden> Sat, 07 Nov 2009 19:55:20 +0100

not fixed, no gajim update in proposed, gajim hg works without compilation, launch.sh is for start it

Does installing 0.13 from Lucid onto Karmic fix this problem?

pavolzetor: Do you enabled the indicator? Do you really get this Python error message? The fixed version can be installed via karmic-updates.

yes, I have indicator applet
Traceback (most recent call last):
  File "gajim.py", line 485, in _process_events
    return self.process_events(fd, flags)
  File "/usr/share/gajim/src/common/xmpp/idlequeue.py", line 150, in process_events
    obj.pollin()
  File "/usr/share/gajim/src/common/xmpp/transports_nb.py", line 360, in pollin
    self._do_receive()
  File "/usr/share/gajim/src/common/xmpp/transports_nb.py", line 516, in _do_receive
    self.on_receive(received)
  File "/usr/share/gajim/src/common/xmpp/dispatcher_nb.py", line 359, in dispatch
    handler['func'](session,stanza)
  File "/usr/share/gajim/src/common/connection_handlers.py", line 1879, in _messageCB
    session.received(frm, msgtxt, tim, encrypted, msg)
  File "/usr/share/gajim/src/session.py", line 121, in received
    msgtxt, tim=tim, subject=subject)
  File "/usr/share/gajim/src/common/logger.py", line 473, in write
    return self.commit_to_db(values, write_unread)
  File "/usr/share/gajim/src/common/logger.py", line 350, in commit_to_db
    self.insert_unread_events(message_id, values[0])
  File "/usr/share/gajim/src/common/logger.py", line 356, in insert_unread_events
    self.simple_commit(sql)
  File "/usr/share/gajim/src/common/logger.py", line 147, in simple_commit
    self.cur.execute(sql_to_commit)
OperationalError: table unread_messages has 3 columns but 2 values were supplied

The fixed version is Lucid package

@pavolzetor This traceback is _not_ related to the indicator applet support problem.

It's about a wrong number of columns in an SQL instruction while writing in the log database.

I suppose that may be because of a log database structure change and a problem with database migration (or no migration at all).

You should open an other bug about this one (please first check if there is already one about SQL error or log database).