Package: pyicqt
Version: 0.8.1.5-3
Severity: important
*** MY Repost ***
Right after entering only my local hostnames pyicqt does not start and instead
prints the following:
Starting ICQ transport for Jabber: pyicqtCRITICAL: Traceback in debug.observer2
- tuple index out of range
CRITICAL: Traceback in debug.observer2 - tuple index out of range
failed!
Running the original upstream package from code.google.com (pyicqt-0.8.1.5)
works fine with the same exact config file.
<thank you for reading>
have a nice day
-- System Information:
Debian Release: 6.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pyicqt depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii python 2.6.6-3+squeeze5 interactive high-level object-orie
ii python-crypto 2.1.0-2 cryptographic algorithms and proto
ii python-openssl 0.10-1 Python wrapper around the OpenSSL
ii python-support 1.0.10 automated rebuilding support for P
ii python-twisted 10.1.0-3 Event-based framework for internet
ii python-twisted-web 10.1.0-1 An HTTP protocol implementation to
ii python-twisted-words 10.1.0-1 Chat and Instant Messaging
Versions of packages pyicqt recommends:
ii python-imaging 1.1.7-2 Python Imaging Library
ii python-mysqldb 1.2.2-10+b1 A Python interface to MySQL
ii python-nevow 0.10.0-2 Web application templating system
Versions of packages pyicqt suggests:
ii ejabberd 2.1.5-3 distributed, fault-tolerant Jabber
pn munin-node <none> (no description available)
-- Configuration Files:
/etc/pyicqt.conf.xml changed:
<pyicqt>
<!-- The JabberID of the transport. -->
<jid>icq.hoodie.de</jid>
<!-- The component JID of the transport. Unless you're doing
clustering, leave this alone -->
<!-- <compjid>icq1</compjid> -->
<!-- The IP address of the main Jabberd server -->
<mainServer>127.0.0.1</mainServer>
<!-- The JID of the main Jabber server -->
<mainServerJID>localhost</mainServerJID>
<!-- The website of the Jabber service -->
<website>http://hoodie.de/</website>
<!-- The website of the transport service -->
<!-- <transportWebsite></transportWebsite> -->
<!-- The support room on your server -->
<!-- <supportRoom></supportRoom> -->
<!-- The JID of a service admin or helpdesk -->
<!-- <supportJid></supportJid> -->
<!-- The TCP port to connect to the Jabber server on -->
<!-- (this is the default for Jabberd2) -->
<port>5347</port>
<!-- The TCP port that the web admin interface will answer on -->
<!-- (uncomment to enable) -->
<!-- <webport>12345</webport> -->
<!-- The authentication token to use when connecting to the Jabber
server -->
<secret>supersecret</secret>
<!-- The default language to use (for error/status messages) -->
<lang>en</lang>
<!-- Default one-byte message encoding to use -->
<encoding>iso-8859-1</encoding>
<!-- The hostname of the ICQ server you wish to connect to -->
<icqServer>login.icq.com</icqServer>
<!-- The port of the ICQ server you wish to connect to -->
<icqPort>5190</icqPort>
<!-- Enable it if you want md5 authentication -->
<usemd5auth/>
<!-- The name of Socks Proxy if connecting thru a proxy -->
<!-- <socksProxyServer>im-proxy2</socksProxyServer> -->
<!-- The Socks Proxy port to use when connecting thru a proxy -->
<!-- <socksProxyPort>1080</socksProxyPort> -->
<!-- Send greeting on login (enter text to be sent to users here) -->
<!-- <sessionGreeting>enter message here</sessionGreeting> -->
<!-- Send message to user on transport stop/restart -->
<enableShutdownMessage/>
<!-- Custom shutdown message -->
<!-- <customShutdownMessage></customShutdownMessage> -->
<!-- Send message on successful registration -->
<!-- <registerMessage>You have successfully registered with
PyICQt</registerMessage> -->
<!-- Allow users of ICQ gateway to chat with AIM users -->
<!-- (uncomment to enable) -->
<!-- <crossChat/> -->
<!-- Disable registration with the transport -->
<!-- (uncomment to disable) -->
<!-- <disableRegister/> -->
<!-- Enable automatic invitation to reconnect on restart -->
<!-- (uncomment to enable) -->
<!-- <enableAutoInvite/> -->
<!-- Disable xhtml support (messages with fonts and colors) -->
<!-- (uncomment to disable) -->
<!-- <disableXHTML/> -->
<!-- Disable mail notifications -->
<!-- (uncomment to disable) -->
<!-- <disableMailNotifications/> -->
<!-- Disable use of default avatar if none is specified -->
<!-- (uncomment to disable) -->
<!-- <disableDefaultAvatar/> -->
<!-- Disable use of iq-based avatars (JEP-0008) -->
<!-- (uncomment to disable) -->
<!-- <disableIQAvatars/> -->
<!-- Disable use of vcard-based avatars (JEP-0153) -->
<!-- (uncomment to disable) -->
<!-- <disableVCardAvatars/> -->
<!-- Disable use of PEP-based avatars (JEP-0084) -->
<!-- (uncomment to disable) -->
<!-- NOT IMPLEMENTED YET -->
<!-- <disablePEPAvatars/> -->
<!-- Support for x-statuses -->
<!-- <xstatusessupport/> -->
<!-- Try detect Unicode:
0 - never
1 - in offline messages
2 - and in nicknames
Attention: this solution can be slowly on high-load servers
-->
<detectunicode>1</detectunicode>
<!-- You can choose which users you wish to have as administrators.
These users can perform some tasks with Ad-Hoc commands that others cannot -->
<admins>
<jid>[email protected]</jid>
</admins>
<!-- You can select which event loop PyICQt will use. It's probably
safe to leave this as the default -->
<!-- Use epoll for high-load Linux servers running kernel 2.6 or above
-->
<!--<reactor>epoll</reactor>-->
<!-- Use kqueue for high-load FreeBSD servers -->
<!--<reactor>kqueue</reactor>-->
<!-- Use poll for high-load Unix servers -->
<!--<reactor>poll</reactor>-->
<!-- You can select which spool storage method you wish to use -->
<!-- Available methods are: -->
<!-- xmlfiles: single xml files in the spool directory in hashed dirs
(default)-->
<!-- legacyaimtransport: compatible with c-based aim transport, less
functionality -->
<!-- legacyjittransport: compatible with JIT transport, less
functionality -->
<!-- mysql: registration information stored in a MySQL database -->
<!--<xdbDriver>xmlfiles</xdbDriver>-->
<!-- For MySQL -->
<!--<xdbDriver>mysql</xdbDriver>-->
<!--<xdbDriver_mysql>-->
<!--<username>pyicqt</username>-->
<!--<password>pyicqt</password>-->
<!--<database>pyicqt</database>-->
<!--<server>localhost</server>-->
<!--<format>encrypted</format>--> <!-- Enable encryption of passwords
-->
<!--</xdbDriver_mysql>-->
<!-- For XMLFiles -->
<!--<xdbDriver>xmlfiles</xdbDriver>-->
<!--<xdbDriver_xmlfiles>-->
<!--<format>encrypted</format>--> <!-- Enable encryption of passwords
-->
<!--</xdbDriver_xmlfiles>-->
<!-- Only grab avatars when a chat is initiated. -->
<!-- <avatarsOnlyOnChat/> -->
<!-- Disable all avatar functionality. Might be necessary if you -->
<!-- do not have PIL installed. -->
<disableAvatars/>
<!-- Enable web presence indicator. This can increase ICQ spam. -->
<!-- <enableWebPresence/> -->
<!-- Disable automatic send (via im) of away message when away set. -->
<!-- Note that away messages are -in addition to- the away status -->
<!-- message. -->
<!-- <disableAwayMessage/> -->
<!-- Use Jabber.com's XCP component protocol extensions. -->
<!-- <useXCP/> -->
<!-- SASL username used to bind to Jabber server. -->
<!-- secret, above, is used for sasl password -->
<!-- <saslUsername>username</saslUsername> -->
<!-- Use external component binding. -->
<!-- This dodges the need to manually configure all jids that talk to
this transport. -->
<!-- Jabberd2 requires saslUsername and useRouteWrap for this to work.
-->
<!-- Wildfire as of 2.6.0 requires just this. -->
<!-- <useComponentBinding/> -->
<!-- Wrap stanzas in <route> stanza. -->
<!-- Jabberd2 requires this for useComponentBinding. -->
<!-- <useRouteWrap/> -->
<!-- JID of message archive service -->
<!-- <messageArchiveJID>datasink.example.org</messageArchiveJID> -->
<!-- If registration authentication is used, enter the method -->
<!-- Auth configs often require additional options to be specified. -->
<!-- See associated config entries per authRegister example. -->
<!-- NOTE: limited to LDAP for now -->
<!-- THIS IS UNTESTED AS OF YET -->
<!-- <authRegister>LDAP</authRegister> -->
<!-- For LDAP auth, make sure to uncomment <authRegister_LDAP> -->
<!-- and </authRegister_LDAP> and fill out the options in between. -->
<!-- <authRegister_LDAP> -->
<!-- The fqdn or ip address of the LDAP server -->
<!-- <server>ldap.example.org</server> -->
<!-- The Root DN to be used to perform LDAP searches -->
<!-- <rootDN>CN=Administrator,CN=Users,DC=example,DC=org</rootDN> -->
<!-- The password for the Root DN -->
<!-- <password>SECRET</password> -->
<!-- The Base DN to search for users -->
<!-- <baseDN>DC=example,DC=org</baseDN> -->
<!-- The attribute to search for the user ID. -->
<!-- 'samAccountname' in Windows, 'uid' on most other systems -->
<!-- <uidAttr>samAccountname</uidAttr> -->
<!-- </authRegister_LDAP> -->
<!-- Default Ad-Hoc settings -->
<adhocDefaults>
<user> <!-- ... for new users - they can change these settings later
-->
<xstatus_receiving_mode>0</xstatus_receiving_mode> <!-- 0 - disable
x-status receiving, 1 - receive as ICQ 5.1, 2 - as ICQ 6, 3 - combined -->
<xstatus_sending_mode>0</xstatus_sending_mode> <!-- 0 - disable
x-status sending, 1 - send as ICQ 5.1, 2 - as ICQ 6, 3 - combined -->
<xstatus_saving_enabled>1</xstatus_saving_enabled> <!-- 1 - restore
latest x-status after login, 0 - do not restore -->
<xstatus_option_smooth>1</xstatus_option_smooth> <!-- 1 - allow
partial interconnect between ICQ 5.1 and ICQ 6 x-statuses -->
<xstatus_display_icon_as_PEP>1</xstatus_display_icon_as_PEP> <!-- 1
- display x-status icon as User Mood/Activity/Tune -->
<xstatus_display_text_as_PEP>1</xstatus_display_text_as_PEP> <!-- 1
- Try interpret x-status text as User Mood/Activity/Tune -->
<xstatus_icon_for_transport>0</xstatus_icon_for_transport> <!-- 1 -
show self x-status icon as User Mood/Activity/Tune for transport (works for
Gajim when transport displayed in roster) -->
<away_messages_receiving>1</away_messages_receiving> <!-- 1 - ask
contacts for Away messages -->
<away_messages_sending>1</away_messages_sending> <!-- 1 - allow own
Away Message sending -->
<clist_show_phantombuddies>0</clist_show_phantombuddies> <!-- 1 -
show old deleted contacts without authorization in roster -->
<clist_deny_all_auth_requests>0</clist_deny_all_auth_requests> <!--
1 - auto send 'Deny' reply on any authorization request -->
<utf8_messages_sendmode>2</utf8_messages_sendmode> <!-- 0 - never
send messages in Unicode, 1 - only when contact sends messages in Unicode, 2 -
send always -->
<offline_messages_sendenc>2</offline_messages_sendenc> <!-- 0 -
send offline messages in Unicode, 1 - in default message encoding (see above),
2 - auto detect -->
<msgconfirm_sendmode>2</msgconfirm_sendmode> <!-- 0 - never send
message confirmations, 1 - send for Unicode messages, 2 - for all messages -->
<msgconfirm_recvmode>1</msgconfirm_recvmode> <!-- 1 - receive
message confirmations -->
<user_mood_receiving>1</user_mood_receiving> <!-- 1 - transport
should send User Mood/Activity/Tune events to connected user -->
<user_activity_receiving>1</user_activity_receiving> <!--
(requirted for x-status as icon displaying) -->
<user_mood_receiving>1</user_mood_receiving> <!-- set options if
most of users has client with support of these PEP events -->
<autoanswer_enable>0</autoanswer_enable> <!-- enable auto answer as
reply on any incoming message -->
<autoanswer_hide_dialog>0</autoanswer_hide_dialog> <!-- hide
incoming messages when autoanswer enabled -->
</user>
</adhocDefaults>
</pyicqt>
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
