Gajim depends on the nslookup program, part of bind-tools. Users will experience crashes or strange behavior from Gajim after loosing connection for the first time from a Jabber server. Gajims complains about not finding nslookup. Installing bind-tools seems to have fixed connection problems and strange behavior from the program. Reproducible: Sometimes Steps to Reproduce: 1. Run gajim 2. Physically disconnect from the network or loose connection in other ways 3. Continue to try and send messages 4. Reconnect the network 5. Wait for Gajim to re-log in. At this point it might crash. Actual Results: Gajim crashes unexpectedly. Before installing bind-tools gajim would spit a lot of errors from .py files. After installing bind-tools: $ gajim Session Management support not available (missing gnome.ui module) Network Manager support not available only. bind-tools should be a dependency of the gajim ebuild.
You should tell upstream to fix their README.html
Yes, but I'm not sure this is the real cause of the problem yet. Nonetheless, Gajim seems to need nslookup. I'm waiting maybe more people will report the same problem.
Oh, Gajim crashed again. :[
$ gajim Session Management support not available (missing gnome.ui module) Network Manager support not available Segmentation fault Happened when I wasn't expecting it. I don't recall what I was doing. I don't know if rebuilding Gajim with debug symbols would help. I'm not a great debugger. Any suggestions? Walk me through if you would like to fix this. Thanks.
Created attachment 144380 [details] gajim --verbose output redirected to a file I didn't do anything except run revdep-rebuild. That's the only thing coming into mind right now. Now Gajim segfaults soon after I start it and more precisely while it's trying to connect. Verbose output file attached.
(In reply to comment #5) > I didn't do anything except run revdep-rebuild. That's the only thing coming > into mind right now. Now Gajim segfaults soon after I start it Somewhat similar over here: Just installed gajim with a few dependencies. Gajim did run fine until the next restart of my computer and now it segfaults. Packages that got emerged on that day: Thu Mar 6 22:41:26 2008 >>> dev-db/sqlite-3.5.3 Thu Mar 6 22:41:42 2008 >>> dev-python/pyopenssl-0.6 Thu Mar 6 22:43:00 2008 >>> app-crypt/gpgme-1.1.5 Thu Mar 6 22:43:11 2008 >>> dev-python/pysqlite-2.3.5 Thu Mar 6 22:43:54 2008 >>> net-im/mcabber-0.9.5 Thu Mar 6 22:44:27 2008 >>> net-im/gajim-0.11.4 Console output from gajim -v: Auf diesem Computer fehlen die Python Bibliotheken für D-Bus Gajims D-BUS-Möglichkeiten können nicht genutzt werden Sitzungsmanagment-Unterstützung nicht verfügbar (Modul gnome.ui fehlt) 07 Mär 2008 09:43:04 Gajim: No trayicon module available Invalid debugflag given always Invalid debugflag given nodebuilder DEBUG: DEBUG: Debug created for /usr/share/gajim/src/common/xmpp/client_nb.py DEBUG: flags defined: always,nodebuilder DEBUG: socket start Plugging <common.xmpp.transports_nb.NonBlockingTcp instance at 0x2aab54adcd88> into <common.xmpp.client_nb.NonBlockingClient instance at 0x2aab54add3f8> Invalid debugflag given always Invalid debugflag given nodebuilder DEBUG: DEBUG: Debug created for /usr/share/gajim/src/common/xmpp/client_nb.py DEBUG: flags defined: always,nodebuilder DEBUG: socket start Plugging <common.xmpp.transports_nb.NonBlockingTcp instance at 0xfd73b0> into <common.xmpp.client_nb.NonBlockingClient instance at 0xfd78c0> DEBUG: nonblockingt start Plugging <common.xmpp.transports_nb.NonBlockingTLS instance at 0xfd77a0> into <common.xmpp.client_nb.NonBlockingClient instance at 0x2aab54add3f8> DEBUG: dispatcher start Plugging <common.xmpp.dispatcher_nb.Dispatcher instance at 0xfd74d0> into <common.xmpp.client_nb.NonBlockingClient instance at 0x2aab54add3f8> DEBUG: dispatcher info Registering namespace "unknown" DEBUG: dispatcher info Registering protocol "unknown" as <class 'common.xmpp.protocol.Protocol'>(unknown) DEBUG: dispatcher info Registering protocol "default" as <class 'common.xmpp.protocol.Protocol'>(unknown) DEBUG: dispatcher info Registering namespace "http://etherx.jabber.org/streams" DEBUG: dispatcher info Registering protocol "unknown" as <class 'common.xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams) DEBUG: dispatcher info Registering protocol "default" as <class 'common.xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams) DEBUG: dispatcher info Registering namespace "jabber:client" DEBUG: dispatcher info Registering protocol "unknown" as <class 'common.xmpp.protocol.Protocol'>(jabber:client) DEBUG: dispatcher info Registering protocol "default" as <class 'common.xmpp.protocol.Protocol'>(jabber:client) DEBUG: dispatcher info Registering protocol "iq" as <class 'common.xmpp.protocol.Iq'>(jabber:client) DEBUG: dispatcher info Registering protocol "presence" as <class 'common.xmpp.protocol.Presence'>(jabber:client) DEBUG: dispatcher info Registering protocol "message" as <class 'common.xmpp.protocol.Message'>(jabber:client) zsh: segmentation fault gajim -v
It got fixed for me. Seems like there were S2S problems with jaim.at that were causing Gajim to segfault when wanting to autojoin MUCs that I had bookmarked. Nonetheless I think upstream should be contacted... >.> ... <.<
