| Summary: | [Update Request] - emesene with Qt frontend fails to log into msn [mga 2] | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Tolhildan Karker <tolhildan_123> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | alejandrocobo, mageia, stormi-mageia, sysadmin-bugs, tmb, wassi |
| Version: | 2 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.mageia.org/show_bug.cgi?id=6371 | ||
| Whiteboard: | MGA2-32-OK mga2-64-OK | ||
| Source RPM: | emesene-2.12.5-1.3.mga2 | CVE: | |
| Status comment: | |||
| Bug Depends on: | 2317 | ||
| Bug Blocks: | |||
|
Description
Tolhildan Karker
2012-06-13 11:11:26 CEST
Manuel Hiebel
2012-06-17 16:17:52 CEST
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=6371 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 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 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. 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 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. 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 Very happy, Damien. Thanks for your work. (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 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. (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 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. Ok, thank you Alejandro, let me check. I'll be back! :-) 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 Now it works great. Thanks! Thanks for the latest update. Now things works. 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 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 ---------------------------------------- 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 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 (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. Wait, I made a typo...
It should be Obsoletes: %{name}-qt4 <= 2.12.5-1
Submiting a new package thanks to Claire. O:-)
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 lol thanks Tested emesene-2.12.5-1.3.mga2 on 32. gtk2 works great. 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 (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) Oops... Better if I had slept yesterday... Sorry Claire and thank you Thomas! I made a typo while fixing the typo... /me runs That's better, thanks Thomas. I thought it was strange. Testing complete mga2 64 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? 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 Packages linked and update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0128 Status:
ASSIGNED =>
RESOLVED |