Opened 8 years ago

Closed 7 years ago

#4946 closed defect (fixed)

"IndexError: list index out of range" on connecting

Reported by: minder Owned by:
Priority: normal Milestone: 0.13
Component: None Version:
Severity: blocker Keywords:
Cc: Blocked By:
Blocking: OS: Unix


This error jumped out of nowhere. Gajim started normally until today, when I got this error:

Traceback (most recent call last):
  File "/usr/share/gajim/src/common/xmpp/", line 476, in _process_events
    return IdleQueue._process_events(self, fd, flags)
  File "/usr/share/gajim/src/common/xmpp/", line 346, in _process_events
  File "/usr/share/gajim/src/common/xmpp/", line 369, in pollin
  File "/usr/share/gajim/src/common/xmpp/", line 547, in _do_receive
  File "/usr/share/gajim/src/common/xmpp/", line 559, in _on_receive
  File "/usr/share/gajim/src/common/xmpp/", line 193, in ProcessNonBlocking
  File "/usr/share/gajim/src/common/xmpp/", line 416, in endtag
    self.streamError = self._mini_dom.getChildren()[0].getName()
IndexError: list index out of range

I don't know why this happened. After some time roster appears but new windows with this error keep popping up every ~30 seconds.

Tried updating to newest revision but without luck.

Attachments (1)

bug4946-01.txt (4.7 KB) - added by minder 8 years ago.
If this is not informative, I'll paste more.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 8 years ago by minder

Correction: Gajim first connects, gets roster, even some messages can come in, and then the error appears and Gajim gets disconnected.

comment:2 Changed 8 years ago by minder

It appears I had Gajim running on my other machine. I thought that there is possibility for two clients to use the same account.

comment:3 Changed 8 years ago by asterix

could you run gajim -v and give me what happens before the traceback?

Changed 8 years ago by minder

If this is not informative, I'll paste more.

comment:4 Changed 7 years ago by asterix

  • Milestone set to 0.13
  • Resolution set to fixed
  • Status changed from new to closed

(In [2b1f59a16fce4761e532d7ca3403915298e88c7a]) prevent traceback when identifying stream error. Fixes #4946

Note: See TracTickets for help on using tickets.