[SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

Lowra · 2012-03-21 13:32:02

Hello,
Yesterday, I used emesene, it was working perfectly well, and today it isn't anymore: It's very laggy, I can't talk to anyone because the GUI is just a grey box which doesn't show conversations windows, of the list of contacts anymore.

This morning I did a pacman -Syu, but emesene wasn't upgraded, python neither:

[2012-03-20 13:52] Running 'pacman -Syu'
[2012-03-20 13:52] synchronizing package lists
[2012-03-20 13:52] starting full system upgrade
[2012-03-20 13:57] upgraded libtasn1 (2.9-2 -> 2.12-1)
[2012-03-20 13:57] upgraded vlc (2.0.0-8 -> 2.0.1-1)
[2012-03-21 13:49] Running 'pacman -Syu'
[2012-03-21 13:49] synchronizing package lists
[2012-03-21 13:49] starting full system upgrade
[2012-03-21 13:50] upgraded bash (4.2.024-1 -> 4.2.024-2)
[2012-03-21 13:50] upgraded device-mapper (2.02.90-1 -> 2.02.95-1)
[2012-03-21 13:50] upgraded iproute2 (3.2.0-2 -> 3.2.0-3)
[2012-03-21 13:50] upgraded libdrm (2.4.31-1 -> 2.4.32-1)
[2012-03-21 13:50] upgraded lvm2 (2.02.90-1 -> 2.02.95-1)
[2012-03-21 13:50] upgraded neon (0.29.6-3 -> 0.29.6-4)
[2012-03-21 13:50] upgraded openssl (1.0.0.h-1 -> 1.0.1-1)
[2012-03-21 13:50] upgraded psmisc (22.15-1 -> 22.16-1)

Does anyone is having the same issue ?
Thanks !

Last edited by Lowra (2012-03-31 19:02:51)

pfdm · 2012-03-22 04:58:49

yes i have the same issue, actually emesene takes 100% cpu ! It's look like an upgrade issue but i don have time to dig into it right now.

ilusi0n · 2012-03-22 07:59:47

Actually kmess is crashing as well 20 seconds after I login after I did the same updates. Seems to be related to this problem

Application version: 2.0.6.2Application version: 2.0.6.2
Compiled at: KDE 4.8.1 (4.8.1), Qt 4.8.0
Running at:  KDE 4.8.1 (4.8.1), Qt 4.8.0
" 
73.713> No backtrace could be generated, gdb timed out. 
73.717> KDE backtrace: "[
0: /usr/lib/libkdecore.so.5(kRealBacktrace(int)+0x35) [0x7fda20d565e5]
1: kmess() [0x561eca]
2: /lib/libc.so.6(+0x349f0) [0x7fda1b4949f0]
3: kmess() [0x4b3850]
4: kmess() [0x4b3861]
5: kmess() [0x4b3861]
6: kmess() [0x4b3861]
7: kmess() [0x4af4b5]
8: kmess() [0x4d4eb8]
9: kmess() [0x4d5cc7]
10: kmess() [0x4d73e0]
11: /usr/lib/libQtCore.so.4(QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2b1) [0x7fda1d071f11]
12: kmess() [0x52c431]
13: kmess() [0x52c483]
14: kmess() [0x52fabd]
15: /usr/lib/libQtCore.so.4(QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2b1) [0x7fda1d071f11]
16: /usr/lib/libQtCore.so.4(QObject::event(QEvent*)+0x99) [0x7fda1d076e09]
17: /usr/lib/libQtGui.so.4(QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xb4) [0x7fda1c1cd8c4]
18: /usr/lib/libQtGui.so.4(QApplication::notify(QObject*, QEvent*)+0x113) [0x7fda1c1d2743]
19: /usr/lib/libkdeui.so.5(KApplication::notify(QObject*, QEvent*)+0x36) [0x7fda20806556]
20: /usr/lib/libQtCore.so.4(QCoreApplication::notifyInternal(QObject*, QEvent*)+0x8c) [0x7fda1d05e06c]
21: /usr/lib/libQtCore.so.4(+0x1a9ef2) [0x7fda1d08eef2]
22: /usr/lib/libQtCore.so.4(+0x1a789d) [0x7fda1d08c89d]
23: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1dd) [0x7fda162c08bd]
24: /usr/lib/libglib-2.0.so.0(+0x450b8) [0x7fda162c10b8]
25: /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x69) [0x7fda162c1289]
26: /usr/lib/libQtCore.so.4(QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x6f) [0x7fda1d08d0bf]
27: /usr/lib/libQtGui.so.4(+0x26cf8e) [0x7fda1c270f8e]
28: /usr/lib/libQtCore.so.4(QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x32) [0x7fda1d05ce52]
29: /usr/lib/libQtCore.so.4(QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0xf7) [0x7fda1d05d0a7]
30: /usr/lib/libQtCore.so.4(QCoreApplication::exec()+0x85) [0x7fda1d061c05]
31: kmess() [0x43b6a0]
32: /lib/libc.so.6(__libc_start_main+0xed) [0x7fda1b48138d]
33: kmess() [0x43b731]
]
" 
KCrash: Application 'kmess' crashing...
KCrash: Attempting to start  from kdeinit
sock_file=/home/ilusi0n/.kde4/socket-ArchBl0w/kdeinit4__0
KCrash: Attempting to start  directly
KCrash failed to exec(), errno = 2

Last edited by ilusi0n (2012-03-22 08:00:56)

Unia · 2012-03-22 12:30:07

I can confirm this issue as well. When I first launch it, it looks oke but my CPU goes up. When I then switch tag (I'm on DWM) and go back to emesene, it remains a grey box and CPU rises even more. I also think this is update-related but as neither emesene nor python got an update, I am not sure what is causing this and because of school, I do not have time to look into it. (might be good that emesene is not working atm though, otherwise I would be distracted )

lauchazombie · 2012-03-23 04:26:46

I think this is protocol related, amsn doesn't connect now, and pidgin has some problems managing the msn contact list.

Unia · 2012-03-23 13:32:18

lauchazombie wrote:

and pidgin has some problems managing the msn contact list.

I don't know if you mean what I encountered, but I opened a topic on that earlier (before emesene stopped working - I switched to emesene cause of the Pidgin issue)

https://bbs.archlinux.org/viewtopic.php?id=135035

Lowra · 2012-03-23 18:47:49

On my side: emesene isn't working at all, pidgin is working fine (although I've been disconnected a few times, while my internet connexion was perfectly fine

lauchazombie · 2012-03-23 19:09:17

Unia wrote:

lauchazombie wrote:
and pidgin has some problems managing the msn contact list.
I don't know if you mean what I encountered, but I opened a topic on that earlier (before emesene stopped working - I switched to emesene cause of the Pidgin issue)

https://bbs.archlinux.org/viewtopic.php?id=135035

Yes that's what i meant, i gues we can only wait for an update from the devs, i'm currently using pidgin since it's the only usable client for me at least...

Unia · 2012-03-23 19:27:02

lauchazombie wrote:

Unia wrote:
lauchazombie wrote:
and pidgin has some problems managing the msn contact list.
I don't know if you mean what I encountered, but I opened a topic on that earlier (before emesene stopped working - I switched to emesene cause of the Pidgin issue)

https://bbs.archlinux.org/viewtopic.php?id=135035
Yes that's what i meant, i gues we can only wait for an update from the devs, i'm currently using pidgin since it's the only usable client for me at least...

Perhaps you could reply to the bug report as well? That might give it some more attention. For now, I am using the weblogin...

jonnybel · 2012-03-25 23:58:58

I'm having the same problem here... Switched to Pidgin but the list of online users doesn't update unless I logout and log back in.

Haven't found any solution yet.

Last edited by jonnybel (2012-03-25 23:59:29)

Lowra · 2012-03-26 16:50:11

jonnybel wrote:

I'm having the same problem here... Switched to Pidgin but the list of online users doesn't update unless I logout and log back in.
Haven't found any solution yet.

I switched to pidgin too, and noticed exactly the same issue. I can't really know what I could try, help would be appreciated

Unia · 2012-03-26 16:59:34

Please everyone who has this issue, report it at my bugreport: http://developer.pidgin.im/ticket/14930

It's supposed to be fixed in 2.10.3, but it's not for me. The more people report at the bugreport, the likelier it get fixed soon!

On the other hand, has there been any news on Emesene yet?

PReP · 2012-03-26 19:19:04

I think this might be poiting towards the emesene2 issue;

** Message: pygobject_register_sinkfunc is deprecated (GstObject)

Which is what i get since a few days when trying to use emesene2.

After login into emesene, this, naturally, leads into:

/usr/share/emesene2/gui/gtkui/__init__.py:89: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed

Might be a python issue, since the deprecated function-thing,
or a gtk-binding for python.

Last edited by PReP (2012-03-26 19:22:00)

Unia · 2012-03-26 19:21:54

Perhaps someone can create a bugreport here: https://github.com/emesene/emesene/issues

I don't have time atm, got my exams this week...

danielausparis · 2012-03-27 05:26:25

Just FYI, I had my aMSN not connecting any more (somebody mentioned aMSN affected as well) and it was related to the last openssl upgrade. Downgrading openssl to previous version cured the problem.

Unia · 2012-03-27 10:39:55

danielausparis wrote:

Just FYI, I had my aMSN not connecting any more (somebody mentioned aMSN affected as well) and it was related to the last openssl upgrade. Downgrading openssl to previous version cured the problem.

That does indeed seem to work! Thank you for the tip!

I'll open a bugreport for this when I got time (already spent this "break" *cough* at downgrading openssl), but if someone else wants to and has time to, please, do it!

PReP · 2012-03-27 13:43:38

openssl then?

Good to know, i am not a fan of downgrading - but i'll look into bug-reporting, and await an up-grade instead

This is timely anyways, since i am trying to move over to skype

(though - that is probably leaving one sinking ship for another - the problem is that all the casual pirates refuses to board the better vessels (i.e not skype nor msn )

Unia · 2012-03-27 13:44:48

^ I hear you...

hit · 2012-03-27 15:50:44

Yes, pacman -U http://schlunix.org/archlinux/core/os/x … pkg.tar.xz worked.

capoeira · 2012-03-27 17:18:10

downgrading openssl solved it for me, too

report: https://groups.google.com/group/emesene … 251ed601cf

Jeffska · 2012-03-28 04:44:54

I found a possible workaround without needing to downgrading OpenSSL. Details are in the emesene issue here: https://github.com/emesene/emesene/issu … nt-4747267

Looks like OpenSSL 1.0.1 changed some of the SSL/TLS negotiation which may not play nice with some servers.

Unia · 2012-03-28 11:13:49

Jeffska wrote:

I found a possible workaround without needing to downgrading OpenSSL. Details are in the emesene issue here: https://github.com/emesene/emesene/issu … nt-4747267
Looks like OpenSSL 1.0.1 changed some of the SSL/TLS negotiation which may not play nice with some servers.

just tried that, it indeed does seem to work. I'll reply to your bugreport as well

PReP · 2012-03-28 14:22:00

Yes :

Editing /usr/share/emesene2/e3/papylib/papyon/papyon/gnet/io/ssl_socket.py,

fixing the line around 51 (was 50 for me), to use OpenSSL.SSLv3.Method,

thus forcing it to use SSL3, works here aswell as a workaround

hit · 2012-03-28 16:29:46

Fix released by emesene. Try git.

capoeira · 2012-03-28 16:49:07

hit wrote:

Fix released by emesene. Try git.

yep, i confirm

http://aur.archlinux.org/packages.php?ID=28048

Arch Linux

#1 2012-03-21 13:32:02

[SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#2 2012-03-22 04:58:49

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#3 2012-03-22 07:59:47

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#4 2012-03-22 12:30:07

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#5 2012-03-23 04:26:46

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#6 2012-03-23 13:32:18

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#7 2012-03-23 18:47:49

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#8 2012-03-23 19:09:17

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#9 2012-03-23 19:27:02

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#10 2012-03-25 23:58:58

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#11 2012-03-26 16:50:11

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#12 2012-03-26 16:59:34

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#13 2012-03-26 19:19:04

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#14 2012-03-26 19:21:54

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#15 2012-03-27 05:26:25

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#16 2012-03-27 10:39:55

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#17 2012-03-27 13:43:38

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#18 2012-03-27 13:44:48

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#19 2012-03-27 15:50:44

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#20 2012-03-27 17:18:10

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#21 2012-03-28 04:44:54

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#22 2012-03-28 11:13:49

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#23 2012-03-28 14:22:00

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#24 2012-03-28 16:29:46

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

#25 2012-03-28 16:49:07

Re: [SOLVED] Emesene isn't working as expected anymore (upgrade related ?)

Board footer