Ubuntu
telepathy-python package

A programming error has been detected

Bug #61945 reported by Gustaf
18
Affects Status Importance Assigned to Milestone
telepathy-python (Ubuntu)
Fix Released
Medium
Telepathy

Bug Description

A programming error has been detected
It probably isn't fatal, but should be reported to the developers nonetheless. The program may behave erratically from now on.

Traceback (most recent call last):
  File "/usr/lib/cohoba/cohoba-applet", line 204, in ?
    run(do_trace, houston())
  File "/usr/lib/cohoba/cohoba-applet", line 116, in houston
    h = Houston()
  File "/usr/lib/python2.4/site-packages/cohoba/common/Utils.py", line 189, in getinstance
    instances[cls] = cls()
  File "/usr/lib/python2.4/site-packages/cohoba/houston/Houston.py", line 58, in __init__
    self.accounts.load()
  File "/usr/lib/python2.4/site-packages/cohoba/houston/AccountList.py", line 50, in load
    accounts = AccountStore.load_all_accounts()
  File "/usr/lib/python2.4/site-packages/cohoba/houston/AccountStore.py", line 51, in load_all_accounts
    return [GConfAccount(account_name) for account_name in get_account_names()]
  File "/usr/lib/python2.4/site-packages/cohoba/houston/AccountStore.py", line 58, in __init__
    Account.__init__(self, name)
  File "/usr/lib/python2.4/site-packages/cohoba/houston/Account.py", line 53, in __init__
    self.load()
  File "/usr/lib/python2.4/site-packages/cohoba/houston/AccountStore.py", line 80, in load
    self.unserialize(dict([(basename(entry.key), py_value_for_gconf_value(entry.value)) for entry in GCONF.all_entries(path)]))
  File "/usr/lib/python2.4/site-packages/cohoba/houston/AccountStore.py", line 107, in unserialize
    self.profile = ProfileList().find(manager, protocol)
  File "/usr/lib/python2.4/site-packages/cohoba/common/Utils.py", line 189, in getinstance
    instances[cls] = cls()
  File "/usr/lib/python2.4/site-packages/cohoba/common/ProfileList.py", line 33, in __init__
    reg.LoadManagers()
  File "/usr/lib/python2.4/site-packages/telepathy/client/managerregistry.py", line 126, in LoadManagers
    self.LoadManager(os.path.join(path, name))
  File "/usr/lib/python2.4/site-packages/telepathy/client/managerregistry.py", line 92, in LoadManager
    raise ConfigParser.NoOptionError("name", "ConnectionManager")
NoOptionError: No option 'name' in section: 'ConnectionManager'

Revision history for this message
PaulSchulz (paulschulz) wrote :

- Searched mailing list for a similar bugs.
  http://lists.freedesktop.org/archives/telepathy/
  None found
- Checked for duplicates on 'bugs.freedesktop.org'
  http://bugs.freedesktop.org
  No bugs listed.
- Raised issue with #telepathy
  (ptlo)
   It appears to be configuration problem. the config file
  describing the manager is missing a required keyword

  Maybe it's an indication of faulty installation of gabble
  (or some other connection manager; is any other packed
  in edgy?), or the user changed something in one of their
  local ~/.telepathy/*.manager files

Revision history for this message
PaulSchulz (paulschulz) wrote :

Information sent to developers mailing list
http://lists.freedesktop.org/archives/telepathy/

Revision history for this message
Gustaf (opera) wrote :

Well, I haven't edited a config file manually, just by the gui, now, cohoba doesn't work whatsoever (can't connect to any jabber server), so it's not a big thing. I'll just remove the applet.

Riccardo Setti (giskard)
Changed in cohoba:
status: Unconfirmed → Confirmed
Revision history for this message
Raphael Slinckx (kikidonk) wrote :

This happens because the .manager file format has been slightly changed.
As a workaround add
Name=gabble in the [ConnectionManager] section.

The new package of cohoba will fix this.

Revision history for this message
Riccardo Setti (giskard) wrote :

yeah :)

(remember to don't check at all [ConnectionManager] section)

btw, universe will freeze do 28/9 do you think you will provide a new cohoba version in time or it's better if i write a ( trivial ;) ) patch for telepathy-gabble.

Revision history for this message
Raphael Slinckx (kikidonk) wrote :

Hopefully I'll provide new releases just before the freeze. I must polish some things up.

Revision history for this message
Raphael Slinckx (kikidonk) wrote :

Actually i Fixed the issues in our repositories. The issue is in telepathy-python not in cohoba itself.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Raphaël: could you tell us which fix that was, so we can dig it out or tell us, if you planned a new release already?

Changed in cohoba:
assignee: nobody → telepathy
importance: Untriaged → Medium
status: Confirmed → Fix Committed
Revision history for this message
Raphael Slinckx (kikidonk) wrote :

The patch name is:

Sun Sep 24 20:24:21 CEST 2006 <email address hidden>
  * Change the Manager Registry to use the ew .manager format (ignoring the [ConnectionManager] stanza, and interpreting the filename for the bus path and bus name arguments.

You can get the unified diff with:
darcs diff -u -p 'Change the Manager Registry'

Hope this helps

Revision history for this message
Daniel Holbach (dholbach) wrote :

Raphaël: you rock!

 telepathy-python (0.13.2-0ubuntu4) edgy; urgency=low
 .
   * debian/patches/01-from-darcs_update-to-new-manager-format.patch:
     - change to new ew .manager format ignoring the [ConnectionManager]
       stanza, and interpreting the filename for the bus path and bus name
       arguments -- thanks Raphaël Slinckx for fixing and pointing to the fix
       (Malone: #61945)
   * debian/control:
     - arch any -> all, changed python-all-dev to be in Build-Depends.

Changed in telepathy-python:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.