Emesene 2.12.1 Error

131 vues
Accéder directement au premier message non lu

Victor

non lue,
27 mars 2012, 09:15:0127/03/2012
à emesene
Hi, I have a problem with emesene, without log in my msn account, it
works perfectly, but when I log in, i cant see nothing, I can't click
in my contacts, and I have this error msg in console:

[victor@victorpc ~]$ emesene
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
Errors occurred while importing jabber backend: No module named xmpp
/usr/share/emesene/gui/gtkui/__init__.py:89: Warning:
g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed
gtk.main()
[14:11:39 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
[14:12:07 WARNING papyon.msnp2p.transport] TLPv1 Parse Error: empty
chunk for non-empty blob
00 00 00 00 83 6d b2 7a 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00
dd 0f 97 05 ce a8 0a 7f b5 02 00 00 00 00 00 00
[14:12:09 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
[14:12:10 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
/usr/share/emesene/gui/gtkui/Dialog.py:592: Warning:
g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed
about.run()
[14:12:38 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
[14:12:38 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
[14:13:09 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data
[14:14:08 WARNING papyon.msnp2p.transport] TLPv1 Parse Error: empty
chunk for non-empty blob
9c 26 8b 30 82 6d b2 7a 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00
fc cc 1b 29 00 00 00 00 00 00 00 00 00 00 00 00
[14:14:11 WARNING papyon.msnp2p.session_manager] Received initial blob
with SessionID=0 and non INVITE SLP data

Can you help me? It works perfectly before my last Arch Linux
update :S Thanks

Fabio

non lue,
27 mars 2012, 12:37:5727/03/2012
à emesene
I'm on Arch, too and emesene is broken since last update, too.
after login the gui gets incredible slow, unusable.

I get no related error message, though:

[studio@myhost ~]$ emesene

Fabio

non lue,
27 mars 2012, 13:06:4627/03/2012
à emesene
So it seams all Arch users have this kind of issue:
https://bbs.archlinux.org/viewtopic.php?id=138074

Fabio

non lue,
27 mars 2012, 13:17:1427/03/2012
à emesene
it seams the problem is openssl 1.0.1-1 related. downgrading to
openssl-1.0.0.h-1 solves this.
could devs have a look at this?

Jeffska

non lue,
28 mars 2012, 00:37:4128/03/2012
à emesene
I found a possible workaround without needing to downgrade OpenSSL.
Details in the emesene issue here: https://github.com/emesene/emesene/issues/1099#issuecomment-4747267
Répondre à tous
Répondre à l'auteur
Transférer
0 nouveau message