Bug 6442 - [Update Request] - emesene with Qt frontend fails to log into msn [mga 2]
Summary: [Update Request] - emesene with Qt frontend fails to log into msn [mga 2]
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA2-32-OK mga2-64-OK
Keywords: validated_update
Depends on: 2317
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-13 11:11 CEST by Tolhildan Karker
Modified: 2012-07-21 13:58 CEST (History)
6 users (show)

See Also:
Source RPM: emesene-2.12.5-1.3.mga2
CVE:
Status comment:


Attachments

Description Tolhildan Karker 2012-06-13 11:11:26 CEST
I know there is request for newer version of emesene that is out. I hope we will have it soon. Maybe that will solve this problem. I am unable to use msn with emesene. Here is the output I get when running emesene from terminal/commandline:
emesene

** (process:4265): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:4265): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:4265): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
Cannot import gtkui: cannot import name gtkui
Errors occurred while importing jabber backend: No module named xmpp
[11:07:35 WARNING e3.common.Config] couldn't load config: /home/hem/.config/emesene2/messenger.hotmail.com/mymail@hotmail.com/config (no file)
[11:07:35 ERROR e3.common.Signal] Method called on dead object: on_login_succeed.on_login_succeed
Traceback (most recent call last):
  File "/usr/share/emesene/e3/common/Signal.py", line 65, in emit
    if callback(*args, **kwargs) == False:
  File "/usr/share/emesene/e3/common/Signal.py", line 112, in __call__
    self.f(self.c(), *arg)
  File "/usr/share/emesene/emesene.py", line 602, in on_login_succeed
    self.draw_main_screen()
  File "/usr/share/emesene/emesene.py", line 514, in draw_main_screen
    self.tray_icon.quit_on_close)
TypeError: go_main() takes at least 5 arguments (4 given)
[11:07:35 ERROR e3.common.Signal] Signal handler (on_contact_list_ready.on_contact_list_ready) error: 'ConnectingPage' object has no attribute 'contact_list'
Traceback (most recent call last):
  File "/usr/share/emesene/e3/common/Signal.py", line 65, in emit
    if callback(*args, **kwargs) == False:
  File "/usr/share/emesene/e3/common/Signal.py", line 112, in __call__
    self.f(self.c(), *arg)
  File "/usr/share/emesene/emesene.py", line 698, in on_contact_list_ready
    self.window.content.contact_list.fill()
AttributeError: 'ConnectingPage' object has no attribute 'contact_list'
[11:07:38 ERROR papyon.gnet.HTTP] Received error code 404 (Not Found) from byfiles.storage.msn.com:80
[11:07:39 ERROR papyon.gnet.HTTP] Received error code 404 (Not Found) from byfiles.storage.msn.com:80
[11:07:39 ERROR papyon.service.content_roaming] Content Roaming service got error: HTTP Error (404): Not Found
Manuel Hiebel 2012-06-17 16:17:52 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=6371
Assignee: bugsquad => mageia
Source RPM: (none) => emesene

Comment 1 Damien Lallement 2012-06-18 19:14:21 CEST
Can you provide:
$ rpm -q gstreamer0.10-plugins-base
plus
$ rpm -q python-papyon
and
$ rpm -qa | grep emesene

Thanks.
No update to 2.12.5 for now. See on other bug report.

Status: NEW => ASSIGNED

Comment 2 Tolhildan Karker 2012-06-19 09:49:20 CEST
rpm -q gstreamer0.10-plugins-base
gstreamer0.10-plugins-base-0.10.36-1.mga2

rpm -q python-papyon
python-papyon-0.5.6-2.mga2

rpm -qa | grep emesene
emesene-2.12.3-1.mga2
emesene-qt4-2.12.3-1.mga2
Comment 3 Damien Lallement 2012-06-25 17:54:36 CEST
If we look at: https://github.com/emesene/emesene/issues/1152#issuecomment-5239757
It seems, Qt frontend is broken for a while (see 2.12.5 changelog)... :-/
Trying to ask emesene dev for help.
Comment 4 Alejandro Cobo 2012-06-28 09:39:57 CEST
QT frontend is not working in those emesene versions. You can try with GTK. Thats works for me and oxygen-gtk translates all visual items.

CC: (none) => alejandrocobo

Comment 5 Damien Lallement 2012-07-09 17:29:54 CEST
Qt is entirely broken. I asked upstream, they told me: "we think to remove it, please use gtk".
So, I'm working on a new package without providing Qt4 frontend.
Stay tuned.
Comment 6 Damien Lallement 2012-07-09 19:16:07 CEST
I removed Qt frontend on emesene-2.12.5-1.1.mga2 and I updated to 2.12.5 as protocol were updated and a lot of bug were fixed in this release.

As Qt was already broken, I did the update to new release. Alejandro will be happy! :-)

Advisory:
-------------
This update of emesene updates it to 2.12.5 as it's a bug fix release and it's recommended as it take in part the new MSN/gtalk/FB protocols.
This update also remove the Qt front-end of emesene as it's entirelly broken and as upstream recommends not to use it.

Packages:
-------------
emesene-2.12.5-1.1.mga2.src.rpm

New Suggests:
-------------
python-gupnp-idg
python-gobject
python-gst0.10

How to test:
-------------
- Install 'emesene' with 'Qt' front-end
- Launch it and see, that it's not working
- Install 'emesene' from 'update_testing' and check it obsoletes 'emesene-qt' and install 'emesene-gtk'
- Launch it and see that it's working

Assignee: mageia => qa-bugs
Summary: emesene 2.12.3-1.mga2 fails to log in to msn => [Update Request] - emesene with Qt frontend fails to log into msn [mga 2]
Source RPM: emesene => emesene-2.12.5-1.1.mga2

Comment 7 Alejandro Cobo 2012-07-09 22:36:04 CEST
Very happy, Damien. Thanks for your work.
Comment 8 Samuel Verschelde 2012-07-09 22:44:15 CEST
(In reply to comment #7)
> Very happy, Damien. Thanks for your work.

To thank him, please test the new update candidate from core/updates_testing and report if all works ok :)

CC: (none) => stormi

Comment 9 Alejandro Cobo 2012-07-10 00:07:17 CEST
I installed it in Mageia 2 KDE i586 updated under VirtualBox. There is no direct access icon in Internet section of KDE application menu. However I can run it from Konsole and it works fine. I didn't test FB and GTalk networks, only WLM.
Comment 10 Damien Lallement 2012-07-10 00:59:11 CEST
(In reply to comment #9)
> I installed it in Mageia 2 KDE i586 updated under VirtualBox. There is no
> direct access icon in Internet section of KDE application menu. However I can
> run it from Konsole and it works fine. I didn't test FB and GTalk networks,
> only WLM.

Do you have the default KDE menu?
It should have an icon...

CC: (none) => mageia

Comment 11 Alejandro Cobo 2012-07-10 01:46:57 CEST
I reproduced the same issue on my netbook. I use the default Mageia KDE configuration. When I install emesene 2.12.3 (the previous version), the icon appears in Internet>More but it dessapears when I update to 2.12.5.
Comment 12 Damien Lallement 2012-07-10 01:50:27 CEST
Ok, thank you Alejandro, let me check.
I'll be back! :-)
Comment 13 Damien Lallement 2012-07-10 15:15:55 CEST
Fixed, thanks.
Please test emesene-2.12.5-1.2.mga2

Source RPM: emesene-2.12.5-1.1.mga2 => emesene-2.12.5-1.2.mga2

Comment 14 Alejandro Cobo 2012-07-10 17:40:24 CEST
Now it works great.

Thanks!
Comment 15 Tolhildan Karker 2012-07-10 20:29:11 CEST
Thanks for the latest update. Now things works.
Comment 16 user7 2012-07-11 20:57:31 CEST
Alejandro: could you follow the procedure described here: https://wiki.mageia.org/en/QA_process_for_validating_updates ? Please do so, then add the whiteboard tag (MGA2-32-OK in your case) and the SRPM version you tested. This way, everybody else will get the update faster. Thanks in advance! If you need help, pop by on #mageia-qa IRC channel.
If you can't do it for whatever reason, please answer and say so. I'll do it instead then. Thanks.

CC: (none) => wassi

Alejandro Cobo 2012-07-12 14:10:05 CEST

Whiteboard: (none) => MGA2-32-OK

Alejandro Cobo 2012-07-12 16:05:28 CEST

Whiteboard: MGA2-32-OK => MGA2-32-OK emesene-2.12.5-1.2.mga2.noarch.rpm

Comment 17 claire robinson 2012-07-12 17:03:27 CEST
Damien is there any way to avoid this?

The following package has to be removed for others to be upgraded:
emesene-qt4-2.12.3-1.mga2.noarch
 (due to unsatisfied emesene == 2.12.3-1.mga2)
claire robinson 2012-07-12 17:03:38 CEST

Whiteboard: MGA2-32-OK emesene-2.12.5-1.2.mga2.noarch.rpm => MGA2-32-OK

Comment 18 claire robinson 2012-07-12 17:06:05 CEST
----------------------------------------
Running checks for "emesene" using media
"Core Release" and "Core Updates Testing".
----------------------------------------
Mageia release 2 (Official) for x86_64
Latest version found in "Core Release" is emesene-2.12.3-1.mga2
Latest version found in "Core Updates Testing" is emesene-2.12.5-1.2.mga2
----------------------------------------
The following packages will require linking:

gobject-introspection-1.32.1-1.mga2 (Core 32bit Release)
gobject-introspection-1.32.1-1.mga2 (Core Release)
lib64cairo-gir1.0-1.32.1-1.mga2 (Core Release)
lib64dbusmenu-gir0.4-0.5.1-1.mga2 (Core Release)
lib64dbusmenu-glib4-0.5.1-1.mga2 (Core Release)
lib64fontconfig-gir2.0-1.32.1-1.mga2 (Core Release)
lib64freetype-gir2.0-1.32.1-1.mga2 (Core Release)
lib64gdk_pixbuf-gir2.0-2.26.1-1.mga2 (Core Release)
lib64girepository1.0_1-1.32.1-1.mga2 (Core Release)
lib64gtk-gir2.0-2.24.10-4.mga2 (Core Release)
lib64gtk-gir3.0-3.4.1-2.mga2 (Core Release)
lib64indicate5-0.6.1-3.mga2 (Core Release)
lib64indicate-gir0.6-0.6.1-3.mga2 (Core Release)
lib64notify-gir0.7-0.7.5-1.mga2 (Core Release)
lib64pango-gir1.0-1.30.0-1.mga2 (Core Release)
lib64pyglib-gi2.0_0-3.2.0-3.mga2 (Core Release)
lib64xft-gir2.0-1.32.1-1.mga2 (Core Release)
lib64xlib-gir2.0-1.32.1-1.mga2 (Core Release)
python-gi-3.2.0-3.mga2 (Core 32bit Release)
python-gi-3.2.0-3.mga2 (Core Release)
----------------------------------------
Done.

Depends on: (none) => 2317

Comment 19 claire robinson 2012-07-12 17:14:21 CEST
Tested Ok mga2 64.

If there is no way to avoid seeing the message about removing emesene-qt4 then this can be validated.

It needs the links in comment 18 for bug 2317 /o\

Whiteboard: MGA2-32-OK => MGA2-32-OK mga2-64-OK

Comment 20 Damien Lallement 2012-07-12 17:34:52 CEST
(In reply to comment #17)
> Damien is there any way to avoid this?
> 
> The following package has to be removed for others to be upgraded:
> emesene-qt4-2.12.3-1.mga2.noarch
>  (due to unsatisfied emesene == 2.12.3-1.mga2)

It's because of the "Obsoletes:      %{name}-qt <= 2.12.5-1" in the specfile.
It's the way it works, I can't do anything else for this warning.
Comment 21 Damien Lallement 2012-07-12 17:41:14 CEST
Wait, I made a typo...
It should be Obsoletes:      %{name}-qt4 <= 2.12.5-1
Submiting a new package thanks to Claire. O:-)
Comment 22 Damien Lallement 2012-07-12 17:45:07 CEST
Please test emesene-2.12.5-1.3.mga2

Source RPM: emesene-2.12.5-1.2.mga2 => emesene-2.12.5-1.3.mga2

Comment 23 claire robinson 2012-07-12 17:46:06 CEST
lol thanks
Comment 24 Tolhildan Karker 2012-07-13 19:22:00 CEST
Tested emesene-2.12.5-1.3.mga2 on 32. gtk2 works great.
Comment 25 claire robinson 2012-07-13 19:44:56 CEST
Seems ok x86_64 but still get the message 

The following package has to be removed for others to be upgraded:
emesene-qt4-2.12.3-1.mga2.noarch
 (due to unsatisfied emesene == 2.12.3-1.mga2) (y/N) y

I guess we'll have to live with it :)

Validating

Advisory:
-------------
This update of emesene updates it to 2.12.5 as it's a bug fix release and it's
recommended as it take in part the new MSN/gtalk/FB protocols.
This update also remove the Qt front-end of emesene as it's entirelly broken
and as upstream recommends not to use it.

SRPM: emesene-2.12.5-1.3.mga2

----------------------------------------
Running checks for "emesene" using media
"Core Release" and "Core Updates Testing".
----------------------------------------
Mageia release 2 (Official) for x86_64
Latest version found in "Core Release" is emesene-2.12.3-1.mga2
Latest version found in "Core Updates Testing" is emesene-2.12.5-1.3.mga2
----------------------------------------
The following packages will require linking:

gobject-introspection-1.32.1-1.mga2 (Core 32bit Release)
gobject-introspection-1.32.1-1.mga2 (Core Release)
lib64cairo-gir1.0-1.32.1-1.mga2 (Core Release)
lib64dbusmenu-gir0.4-0.5.1-1.mga2 (Core Release)
lib64dbusmenu-glib4-0.5.1-1.mga2 (Core Release)
lib64fontconfig-gir2.0-1.32.1-1.mga2 (Core Release)
lib64freetype-gir2.0-1.32.1-1.mga2 (Core Release)
lib64gdk_pixbuf-gir2.0-2.26.1-1.mga2 (Core Release)
lib64girepository1.0_1-1.32.1-1.mga2 (Core Release)
lib64gtk-gir2.0-2.24.10-4.mga2 (Core Release)
lib64gtk-gir3.0-3.4.1-2.mga2 (Core Release)
lib64indicate5-0.6.1-3.mga2 (Core Release)
lib64indicate-gir0.6-0.6.1-3.mga2 (Core Release)
lib64notify-gir0.7-0.7.5-1.mga2 (Core Release)
lib64pango-gir1.0-1.30.0-1.mga2 (Core Release)
lib64pyglib-gi2.0_0-3.2.0-3.mga2 (Core Release)
lib64xft-gir2.0-1.32.1-1.mga2 (Core Release)
lib64xlib-gir2.0-1.32.1-1.mga2 (Core Release)
python-gi-3.2.0-3.mga2 (Core 32bit Release)
python-gi-3.2.0-3.mga2 (Core Release)
----------------------------------------
Done.

Could sysadmin please push from core/updates_testing to core/updates and do the required linking.

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 26 Thomas Backlund 2012-07-13 21:48:10 CEST
(In reply to comment #25)
> Seems ok x86_64 but still get the message 
> 
> The following package has to be removed for others to be upgraded:
> emesene-qt4-2.12.3-1.mga2.noarch
>  (due to unsatisfied emesene == 2.12.3-1.mga2) (y/N) y
> 
> I guess we'll have to live with it :)
> 

Nope.

_nothing_ coming through updates should stop and ask for user intervention


There was a typo in the obsoletes, so it didn't match (-qt2 vs -qt4)

Fixed in emesene-2.12.5-1.4.mga2

Keywords: validated_update => (none)
CC: (none) => tmb

Comment 27 Damien Lallement 2012-07-13 22:36:04 CEST
Oops... Better if I had slept yesterday...
Sorry Claire and thank you Thomas! I made a typo while fixing the typo... /me runs
Comment 28 claire robinson 2012-07-13 22:52:48 CEST
That's better, thanks Thomas. I thought it was strange.

Testing complete mga2 64
Comment 29 Tolhildan Karker 2012-07-19 12:31:29 CEST
Testing completed in mga2 32 bits. After core update testing was enabled and updating it, it removed qt and install gtk without any issue. Move to core update now?
Comment 30 claire robinson 2012-07-19 12:33:59 CEST
Validating

Advisory:
-------------
This update of emesene updates it to 2.12.5 as it's a bug fix release and it's
recommended as it take in part the new MSN/gtalk/FB protocols.
This update also remove the Qt front-end of emesene as it's entirelly broken
and as upstream recommends not to use it.

SRPM: emesene-2.12.5-1.4.mga2

----------------------------------------
Running checks for "emesene" using media
"Core Release" and "Core Updates Testing".
----------------------------------------
Mageia release 2 (Official) for x86_64
Latest version found in "Core Release" is emesene-2.12.3-1.mga2
Latest version found in "Core Updates Testing" is emesene-2.12.5-1.3.mga2
----------------------------------------
The following packages will require linking:

gobject-introspection-1.32.1-1.mga2 (Core 32bit Release)
gobject-introspection-1.32.1-1.mga2 (Core Release)
lib64cairo-gir1.0-1.32.1-1.mga2 (Core Release)
lib64dbusmenu-gir0.4-0.5.1-1.mga2 (Core Release)
lib64dbusmenu-glib4-0.5.1-1.mga2 (Core Release)
lib64fontconfig-gir2.0-1.32.1-1.mga2 (Core Release)
lib64freetype-gir2.0-1.32.1-1.mga2 (Core Release)
lib64gdk_pixbuf-gir2.0-2.26.1-1.mga2 (Core Release)
lib64girepository1.0_1-1.32.1-1.mga2 (Core Release)
lib64gtk-gir2.0-2.24.10-4.mga2 (Core Release)
lib64gtk-gir3.0-3.4.1-2.mga2 (Core Release)
lib64indicate5-0.6.1-3.mga2 (Core Release)
lib64indicate-gir0.6-0.6.1-3.mga2 (Core Release)
lib64notify-gir0.7-0.7.5-1.mga2 (Core Release)
lib64pango-gir1.0-1.30.0-1.mga2 (Core Release)
lib64pyglib-gi2.0_0-3.2.0-3.mga2 (Core Release)
lib64xft-gir2.0-1.32.1-1.mga2 (Core Release)
lib64xlib-gir2.0-1.32.1-1.mga2 (Core Release)
python-gi-3.2.0-3.mga2 (Core 32bit Release)
python-gi-3.2.0-3.mga2 (Core Release)
----------------------------------------
Done.

Could sysadmin please push from core/updates_testing to core/updates and do the
required linking.

Thanks!

Keywords: (none) => validated_update

Comment 31 Thomas Backlund 2012-07-21 13:58:30 CEST
Packages linked and update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0128

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.