Created attachment 9544 [details]
mgaonline dialog in vbox after visual glitch

Created attachment 9545 [details]
mgaonline dialog in vbox a bit later, showing working progress bars

Created attachment 9546 [details]
mgaonline dialog in vbox, congratulations window with broken buttons

If more debugging info is needed, please advise a good way to debug further; I can easily reproduce the issue again by restore my Mageia 5 VM and reattempting the upgrade, it just takes ~30 min before the issue shows up.

Maybe we need to push a statically linked mgaonline to mga5 for that to work, as:

http://svnweb.mageia.org/packages?view=revision&revision=838257
- upstream removed pango modules support


wich means pango-modules gets nuked during upgrade and *boom*

CC: (none) => tmb

if thats whats causing the issue that is...

Actually, I guess simply removing this:
Obsoletes:      %{lib_name}-modules < 1.37.0

could help fix it (no I haven't checked the deps if it will help the modules stay during upgrade)

Created attachment 9552 [details]
Upgrade log with pango-1.40.6-1.1.mga6 without the Obsoletes

(In reply to Thomas Backlund from comment #7)
> Actually, I guess simply removing this:
> Obsoletes:      %{lib_name}-modules < 1.37.0

I've pushed a tentative fix with this (pango-1.40.6-1.1.mga6), and I've tweaked mgaapplet-upgrade-checker locally so that it lets me use testing repos, but I'm hitting an issue. urpmi still tries to install the -1.mga6 package because the Obsoletes is too "strong" in its logic (see attached log):


auto-select: adding lib64pango-gir1.0-1.40.6-1.1.mga6.x86_64 replacing lib64pango-gir1.0-1.36.8-3.mga5.x86_64
auto-select: adding pango-doc-1.40.6-1.1.mga6.noarch replacing pango-doc-1.36.8-3.mga5.noarch
auto-select: adding lib64pango1.0-devel-1.40.6-1.1.mga6.x86_64 replacing lib64pango1.0-devel-1.36.8-3.mga5.x86_64
auto-select: adding pango-1.40.6-1.1.mga6.x86_64 replacing pango-1.36.8-3.mga5.x86_64
auto-select: adding lib64pango1.0_0-1.40.6-1.1.mga6.x86_64 replacing lib64pango1.0_0-1.36.8-3.mga5.x86_64
// all good so far
auto-select: adding lib64pango1.0_0-1.40.6-1.mga6.x86_64 replacing lib64pango1.0_0-modules-1.36.8-3.mga5.x86_64
// oops!

And then of course, conflict:

Certains paquetages demandés ne peuvent pas être installés :
lib64pango1.0_0-1.40.6-1.mga6.x86_64 (en raison de conflit avec lib64pango1.0_0-1.40.6-1.1.mga6.x86_64)


Thierry, Thomas, Neal: Would you know a way to force lib64pango1.0_0-1.40.6-1.1.mga6.x86_64 to override lib64pango1.0_0-1.40.6-1.mga6.x86_64 so that the Obsoletes is not taken into account?

I thought of adding either:
Obsoletes: %{lib_name} = 1.40.6-1
or
Conflicts: %{lib_name} = 1.40.6-1

But I'm not sure if it would be enough/efficient or if it would trigger ugly solver loops.

BTW, I wouldn't have much time to test further myself this week, so here are some instructions to reproduce and test a potential fix:

- Install a VM with KDE4
- Add Mageia 6 repos, enable testing repos as update media via `drakrpm-editmedia --expert`
- Hack mgaapplet-upgrade-helper so that it does not remove the existing repos (see https://hastebin.com/awofaceyiz )
- Attempt the upgrade with `mgaapplet-upgrade-helper --new_distro_version=6 --testing`

i think that we have to force install of new pango before anything.

I don't know if this is doable or if this is the good solution

CC: (none) => mageia

(In reply to Nicolas Lécureuil from comment #10)
> i think that we have to force install of new pango before anything.
> 
> I don't know if this is doable or if this is the good solution

I tried it, installing the update candidate pango on mga5 before attempting the upgrade, but it's then incompatible with perl:
/usr/bin/perl: symbol lookup error: /lib64/libpangoft2-1.0.so.0: undefined symbol: FcWeightFromOpenType

But with a good understanding of the way rpm deps are solved, I think we'll find a way to fix this properly. I think my Obsoletes or Conflicts proposals might do the trick, but I'd like a confirmation before attempting it.

(In reply to Rémi Verschelde from comment #8)
> 
> Thierry, Thomas, Neal: Would you know a way to force
> lib64pango1.0_0-1.40.6-1.1.mga6.x86_64 to override
> lib64pango1.0_0-1.40.6-1.mga6.x86_64 so that the Obsoletes is not taken into
> account?
> 
> I thought of adding either:
> Obsoletes: %{lib_name} = 1.40.6-1
> or
> Conflicts: %{lib_name} = 1.40.6-1
> 
> But I'm not sure if it would be enough/efficient or if it would trigger ugly
> solver loops.

Wouldn't "Conflicts: %{lib_name} < 1.40.6-1.1" work? It would force it to be considered the highest upgrade candidate as long as the update repo is enabled along with the regular one.

You can't use equals because it would force a full match for all specified fields, and that'll just fail because we append the %dist value (through %mkrel).

(In reply to Rémi Verschelde from comment #11)
> I tried it, installing the update candidate pango on mga5 before attempting
> the upgrade, but it's then incompatible with perl:
> /usr/bin/perl: symbol lookup error: /lib64/libpangoft2-1.0.so.0: undefined
> symbol: FcWeightFromOpenType

Have you tried updating perl-Pango too?

Source RPM: mgaonline-3.15-1.mga5, pango? => mgaonline-3.15-1.mga5, pango?, gtk+3.0
CC: (none) => olav, thierry.vignaud

Created attachment 9556 [details]
gurpmi: update perl-Pango first too (mga#21425)

This makes gurpmi to update perl-Pango first too

Created attachment 9557 [details]
rpmdrake: update perl-Pango first too (mga#21425)

This makes rpmdrake to update perl-Pango first too (for consistency)

Please test the first patch (the second is for consistency if one would do the live upgrade through rpmdrake but that needs more manual steps so it's not as urgent)

Keywords: (none) => PATCH
Source RPM: mgaonline-3.15-1.mga5, pango?, gtk+3.0 => mgaonline-3.15-1.mga5, pango?

commit 8a4ba9ec63e926703b24197c2c20023c7ebb5352
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Wed Aug 2 17:00:24 2017 +0200

    gurpmi: update perl-Pango first too (mga#21425)
---
 Commit Link:
   http://gitweb.mageia.org/software/rpm/urpmi/commit/?id=8a4ba9ec63e926703b24197c2c20023c7ebb5352

As nobody else seems to want to, I've tested Thierry's first patch. It doesn't help, because adding perl-Pango to the priority updates doesn't cause pango to be updated at the same time. Adding pango to the priority updates does work, but this just moves the problem - the text rendering in the installation progress bar is broken.

I see three ways to fix this problem:

1) Force mgaapplet-upgrade-helper to restart after installing priority updates (like rpmdrake does). This would take quite a bit of work.

2) Remove the "obsoletes %{lib_name}-modules" from the mga6 libpango1.0_0 package. This has the disadvantage that it leaves an unwanted mga5 package installed.

3) Configure the mga5 libpango1.0_0 package with --with-included-modules=yes and eliminate but don't obsolete the mga5 libpango1.0_0-modules package. Providing the user has updated before upgrading, mgaapplet-upgrade-helper will be using the built-in pango modules, so the mga6 libpango1.0_0 can then obsolete libpango1.0_0-modules without causing problems.

CC: (none) => mageia

I've tested option 3 above (in a clean install of Xfce in VirtualBox), and it does fix the missing text in the "Congratulations" window. You can in fact obsolete the libpango1.0_0-modules package straight away without issues, although you also need to remove the files in /etc/pango to avoid spurious error messages.

The switch to a black background is a different bug. It is caused by the removal of the oxygen-gtk package. It can be avoided by switching to a different GTK theme (e.g. Adwaita) before running mgaapplet-upgrade-helper.

The bad news is my upgraded system won't boot with the 4.14.13-1.mga6 kernel.

(In reply to Martin Whitaker from comment #19)
> The bad news is my upgraded system won't boot with the 4.14.13-1.mga6 kernel.

But that seems to be the bug with more than one CPU enabled in VirtualBox that others are reporting.

(In reply to Martin Whitaker from comment #19)
> I've tested option 3 above (in a clean install of Xfce in VirtualBox), and
> it does fix the missing text in the "Congratulations" window. You can in
> fact obsolete the libpango1.0_0-modules package straight away without
> issues, although you also need to remove the files in /etc/pango to avoid
> spurious error messages.

More extensive testing shows that removing the libpango1.0_0-modules package straight away can cause problems (until you reboot) - although this is strangely intermittent. So I think my original plan of leaving the old package in place and letting the upgrade to mga6 remove it is the way forward.

I have found that adding

  BEGIN { $ENV{GTK_THEME} = 'Adwaita' }

at the very start of /usr/libexec/mgaapplet-upgrade-helper fixes the switch to a black background. Adwaita is provided by the gtk+3.0 package in both mga5 and mga6, so should be a safe choice.

commit 9c7cafa99410cc7cba5541f444d66279da8583b3
Author: Martin Whitaker <mageia@...>
Date:   Mon Jan 22 22:23:25 2018 +0000

    mgaapplet-upgrade-helper: force use of Adwaita theme (mga#21425)
    
    Prevents display issues if current theme (e.g. oxygen-gtk) is obsoleted.
---
 Commit Link:
   http://gitweb.mageia.org/software/mgaonline/commit/?id=9c7cafa99410cc7cba5541f444d66279da8583b3

commit 9e8b9f04dd1af454644f9f2e255c25c2d3d3a30a
Author: Martin Whitaker <mageia@...>
Date:   Mon Jan 22 22:23:25 2018 +0000

    mgaapplet-upgrade-helper: force use of Adwaita theme (mga#21425)
    
    Prevents display issues if current theme (e.g. oxygen-gtk) is obsoleted.
    
    (cherry picked from commit 9c7cafa99410cc7cba5541f444d66279da8583b3)
---
 Commit Link:
   http://gitweb.mageia.org/software/mgaonline/commit/?id=9e8b9f04dd1af454644f9f2e255c25c2d3d3a30a

I have uploaded patched/updated packages for Mageia 5.

You can test them as follows:

1. Start with a fully updated Mageia 5 test system that you don't mind being upgraded.
2. Have at least one GTK-based application running (e.g. MCC).
3. Enable the core/updates_testing media and install the updated packages.
4. Check there are no new problems with text rendering in any running applications or (if using a GTK based DE) in the DE menus.
5. Restart the DE (or to be completely sure, reboot) to make sure it is using the updated libraries, and check again that there are no new issues with text rendering in the DE or in freshly started GTK-based applications.
6. Disable the core/updates_testing media.
7. Kill the mgaapplet process if it is running.
8. Restart mgaapplet from the command line by 'mgaapplet --testing'.
9. Accept the offer to upgrade to Mageia 6.
10. Observe whether the progress bar remains legible right to the end of the upgrade, and that the final dialogue is legible.

Suggested advisory:
===================

Updated pango and mgaonline packages fix display issues during online distribution upgrade.

On performing an online upgrade from Mageia 5 to Mageia 6, it was found that at some (variable) point during the upgrade the progress dialogue goes dark with most text invisible, and also that at the end of the upgrade, the final dialogue is very dark and does not have properly rendered text. These updates fix these issues.

References:
https://bugs.mageia.org/show_bug.cgi?id=21425
===================

Updated packages in core/updates_testing
========================================
mgaonline-3.15.1-1.mga5
pango-1.36.8-4.mga5
pango-doc-1.36.8-4.mga5
pango-tests-1.36.8-4.mga5
lib(64)pango1.0_0-1.36.8-4.mga5
lib(64)pango-devel-1.36.8-4.mga5
lib(64)pango-gir1.0_0-1.36.8-4.mga5

Source RPMs:
mgaonline-3.15.1-1.mga5.src.rpm
pango-1.36.8-4.mga5.src.rpm

Assignee: mageiatools => qa-bugs

P.S. I should perhaps have said that the pango updates can be tested on their own on any Mageia 5 system, even if you aren't prepared to upgrade it. In that case, just look for any regressions - it should work exactly as before. pango is a core component of GTK-based applications, so the more testing it gets, the better.

*** Bug 20761 has been marked as a duplicate of this bug. ***

CC: (none) => westel

*** Bug 20762 has been marked as a duplicate of this bug. ***

Mageia 5 :: x86_64

I discovered that my sources were not properly configured.
Updated the packages, except for lib64pango-devel (could not find it).

After that the upgrade ran normally and finished in 30 minutes.  The terminal is left hanging and the reboot button does not respond except to close the applet.  Rebooted and noted the nvidia kmod being rebuilt but the desktop came up under vesa.  Ran drakx11 and rebooted to Plasma under nvidia.  Noted that 11 instances of firefox were launched.  Had to kill ten of them.

But apart from these hitches, it works.

CC: (none) => tarazed25

(In reply to Len Lawrence from comment #28)
> Mageia 5 :: x86_64
> 
> I discovered that my sources were not properly configured.
> Updated the packages, except for lib64pango-devel (could not find it).
> 


libpango-devel-1.36.8-4.mga5
should be 
libpango1.0-devel-1.36.8-4.mga5

adjust as required for x86_64

for me also brought in

libdatrie-devel-0.2.8-3.mga5    
libthai-devel-0.1.21-3.mga5

Thanks Ben.

(In reply to Len Lawrence from comment #28)
> After that the upgrade ran normally and finished in 30 minutes.  The
> terminal is left hanging and the reboot button does not respond except to
> close the applet.  Rebooted and noted the nvidia kmod being rebuilt but the
> desktop came up under vesa.  Ran drakx11 and rebooted to Plasma under
> nvidia.  Noted that 11 instances of firefox were launched.  Had to kill ten
> of them.
> 
> But apart from these hitches, it works.

Reboot is disabled by --testing - so there's no way to test it! Not sure why this is, as --testing doesn't stop you doing the upgrade.

Mga 5.1 i586 upgrade

Celeron M-530, intel-810 or later, Broadcom BCM4311.
multiple desktops, but no extra applications(i.e vbox)

from KDE start upgrade via terminal with

$ killall mgaapplet
$ mgaapplet --testing 

Preparing...                     
      1/2: pango                 
      2/2: mgaonline             
      1/2: removing pango-1.36.8-3.mga5.i586
      2/2: removing mgaonline-3.15-1.mga5.noarch

To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release (distrib1)")
  libdatrie-devel                0.2.8        3.mga5        i586    
  libthai-devel                  0.1.21       3.mga5        i586 
 
 
Preparing...                     
      1/7: libdatrie-devel       
      2/7: libthai-devel         
      3/7: pango-doc             
      4/7: libpango1.0_0         
      5/7: libpango-gir1.0       
      6/7: libpango1.0-devel    
      7/7: pango-tests 

left open a gtk application (network_monitor)
left system to upgrade.

at completion, network monitor has "black on black"
"Congratulations" box has text buttons
pressing "reboot" closes the "Congratulations" box
Menu "reboot" does nothing, as noted by Len 

from the existing terminal tab no entry is accepted, a new tab required
as user "shutdown" is a permission denied, as is "reboot"
as root "shutdown" is a permission denied,   
as root "reboot" works.

during the reboot, when the broadcom driver is being built and installed, the animated cauldron is white on a black background.

after login wifi not working

need to reset encryption made (open-WEP needed to be changed to WPA/WPA2 Pre-Shared Key)

Firefox very slow to start, I opened 3 extra instances before the window open in Mageia5 presented.

will redo install, but use theme "adwaita" before starting the upgrade

@Ben, did you do the DE restart/reboot (step 5) between installing the updates and starting the upgrade?

no, will try that this time

if a reboot before trying to update, you can add a:

Provides:	should-restart = system

to mgaonline, so it will inform the user about the need to reboot before updating...

Tried the upgrade on another x86_64 machine, an Aorus X5 twin-nvidia laptop, plugged in to the router.

Installed KDE by itself to a spare partition and updated it to current levels then updated the mgaonline packages and followed the reboot procedure outlined by Martin.
Started the upgrade from a konsole.  That ran smoothly and at no point were the progress messages invisible; blue progress bars, black text on a white background.  The upgrade completed successfully and reboot worked under user, from the konsole.  I had forgotten to detach the network cable so had to re-enable wifi - it connected immediately and the rest of the Plasma desktop appeared to be functioning.  Firefox was OK but it came up with a query - something about "This is embarrassing...." which happens anyway on every single boot on any machine.  It presented the tabs which had been in use before the upgrade.

I am satisfied that mgaonline is fit for use.  Leaving Ben to investigate the effects of theme changes.  Good man.

VirtualBox VM instance on AMD equipment

VM was MGA 5.1 - KDE - 64bit.  All patches applied and system rebooted.

The following 6 packages are going to be installed:

- lib64pango-gir1.0-1.36.8-4.mga5.x86_64
- lib64pango1.0_0-1.36.8-4.mga5.x86_64
- mgaonline-3.15.1-1.mga5.noarch
- pango-1.36.8-4.mga5.x86_64
- pango-doc-1.36.8-4.mga5.noarch
- pango-tests-1.36.8-4.mga5.x86_64

-----

I followed Ben's instructions

$ killall mgaapplet
$ mgaapplet --testing

---

Started the updates.  Ate lunch, went to the library, worked on my mid-term exam came back it had completed.

---

Followed reboot.

---

Second reboot because of video changes

---

Libreoffice, Firefox, VLC, Gwenview and various other apps are working as designed.

CC: (none) => brtians1

(In reply to Thomas Backlund from comment #35)
> if a reboot before trying to update, you can add a:
> 
> Provides:	should-restart = system
> 
> to mgaonline, so it will inform the user about the need to reboot before
> updating...

Thanks Thomas. I think that's worth adding. It's the lib(64)pango1.0_0 library that's the important one, so I've added the should-restart to that. So the revised list of packages to test is

Updated packages in core/updates_testing
========================================
mgaonline-3.15.1-1.mga5
pango-1.36.8-5.mga5
pango-doc-1.36.8-5.mga5
pango-tests-1.36.8-5.mga5
lib(64)pango1.0_0-1.36.8-5.mga5
lib(64)pango-devel1.0-1.36.8-5.mga5
lib(64)pango-gir1.0_0-1.36.8-5.mga5

Source RPMs:
mgaonline-3.15.1-1.mga5.src.rpm
pango-1.36.8-5.mga5.src.rpm

with the only difference being that installing lib(64)pango1.0_0 should prompt you to restart the system. The mgaonline package is unchanged.

upgrade of Mageia 5.1 x86_64 with above new packages

Celeron M-53- intel-810 or later Broadcom BCM4311
Multiple desktops but no extra applications installed (i.e. vbox)
  
again open application (Firefox and network monitor) have "black on black"
(additional comments box is black when entering text into this bug report) 

this is only partway through the upgrade.
will run both i586 and x86_64 again tomorrow with any newer packages

Thanks for your tests Ben.

(In reply to ben mcmonagle from comment #39)
> again open application (Firefox and network monitor) have "black on black"
> (additional comments box is black when entering text into this bug report) 

I don't think this is a problem - we do instruct the user to close all running applications before starting the upgrade. In case I didn't make it clear, my instruction to have a GTK application running was only meant to last while you were installing the mga5 updates, not for the subsequent upgrade to mga6. That was just meant to check we don't break a mga5 system by releasing this update.

About to test M5/64 real EFI hardware with Radeon video; XFCE desktop. Gtk?
Procedure from Comment 24.
Question (if it matters): how do you know whether Adwaita theme is being used, or if not, how to get it used.

1. Start with a fully updated Mageia 5 test system that you don't mind being upgraded.
2. Have at least one GTK-based application running (e.g. MCC).
3. Enable the core/updates_testing media and install the updated packages.

Updates about to be done (via MCC-Update System) to the running M5 system:
- lib64datrie-devel-0.2.8-3.mga5.x86_64
- lib64pango-gir1.0-1.36.8-5.mga5.x86_64
- lib64pango1.0-devel-1.36.8-5.mga5.x86_64
- lib64pango1.0_0-1.36.8-5.mga5.x86_64
- lib64thai-devel-0.1.21-3.mga5.x86_64
- mgaonline-3.15.1-1.mga5.noarch
- pango-1.36.8-5.mga5.x86_64
- pango-doc-1.36.8-5.mga5.noarch

which said I should re-start the computer for Pango. Note that OK.
Before that:
4. Check there are no new problems with text rendering in any running applications or (if using a GTK based DE) in the DE menus.
Started Gimp, which is Gtk demanding. fonts OK. Also using IceApe browser: is this GtK? If so, fonts still OK. To re-check after re-boot. Back soon.

CC: (none) => lewyssmith

M5/64 real EFI h/w with Radeon video, XFCE, continued.

5. Restart the DE (or to be completely sure, reboot) to make sure it is using the updated libraries, [Re-booted]
 pango-doc-1.36.8-5.mga5
 pango-1.36.8-5.mga5
 lib64pango-gir1.0-1.36.8-5.mga5
 lib64pango1.0_0-1.36.8-5.mga5
 lib64pango1.0-devel-1.36.8-5.mga5
 mgaonline-3.15.1-1.mga5
and check again that there are no new issues with text rendering in the DE or in freshly started GTK-based applications.
None seen on XFCE desktop, Gimp, Claws-mail, MCC (the last 3 at least Gtk), IceApe.

6. Disable the core/updates_testing media.
I live normally like that!

7. Kill the mgaapplet process if it is running.
 $ ps -ax | grep mga
 3269 ?        Sl     0:03 /usr/bin/perl /usr/bin/mgaapplet
 $ kill 3269

8. Restart mgaapplet from the command line by 'mgaapplet --testing'.
 $ mgaapplet --testing
Ignore the following Glib::Object::Introspection & Gtk3 warnings
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Exception caught
Exception: [metalink_helper.cc:118] errorCode=20 Could not parse Metalink XML document.
error: Methodd 'aria2': gadael gyda 20
Ignore the following Glib::Object::Introspection & Gtk3 warnings
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
getting exclusive lock on urpmi
unlocking urpmi database
...
then a long list saying that all repos were up-to-date;
 using mirror http://magie.remi.lu/distrib/5/x86_64
followed by a long list of checking /synthesis.hdlist.cz files:
archwilio ffeil synthesis [/var/lib/urpmi/Core Release (distrib1)/synthesis.hdlist.cz]
...
archwilio ffeil synthesis [/var/lib/urpmi/Tainted 32bit Updates (distrib87)/synthesis.hdlist.cz]
except it STOPPED/stuck after the last. Left it 5m; try again tomorrow.

(In reply to Lewis Smith from comment #42)

> except it STOPPED/stuck after the last. Left it 5m; try again tomorrow.

should then put the blue down arrow in the system tray (where updates notifier usually is)

upgrade Mageia 5.1 i586

Celeron M530, Intel 810 or later, Broadcom BCM4311 wifi
Multiple desktops but no extra applications like Virtualbox.

upgrade run from KDE

To satisfy dependencies, the following packages are going to be installed:                                                                 
  Package                        Version      Release       Arch                                                                           
(medium "Core Release (distrib1)")                                                                                                         
  libdatrie-devel                0.2.8        3.mga5        i586    
  libthai-devel                  0.1.21       3.mga5        i586    
(medium "Core Updates Testing (distrib5)")
  libpango-gir1.0                1.36.8       5.mga5        i586    
  libpango1.0-devel              1.36.8       5.mga5        i586    
  libpango1.0_0                  1.36.8       5.mga5        i586    
  mgaonline                      3.15.1       1.mga5        noarch  
  pango                          1.36.8       5.mga5        i586    
  pango-doc                      1.36.8       5.mga5        noarch  
  pango-tests                    1.36.8       5.mga5        i586    
3.7MB of additional disk space will be used.
1MB of packages will be retrieved.
Proceed with the installation of the 9 packages? (Y/n) y

-----

You should restart your computer for libpango1.0_0

#reboot

check network monitor ok (this will go "black-on-black" during upgrade)
check firefox ok (this Bug#, additional comments box will go black during upgrade)

$ killall mgaapplet
$ mgaapplet --testing


at completion of upgrade the "you must reboot now" reboot button does not work. 
restart from the application menu does not work.   
reboot from a new konsole tab does work

reboot to working desktop

Mga5.1 x86_64 upgrade

Intel M530, Intel 810 or later, Broadcom BCM 4311 wifi

To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release (distrib1)")
  lib64datrie-devel              0.2.8        3.mga5        x86_64  
  lib64thai-devel                0.1.21       3.mga5        x86_64  
(medium "Core Updates Testing (distrib5)")
  lib64pango-gir1.0              1.36.8       5.mga5        x86_64  
  lib64pango1.0-devel            1.36.8       5.mga5        x86_64  
  lib64pango1.0_0                1.36.8       5.mga5        x86_64  
  mgaonline                      3.15.1       1.mga5        noarch  
  pango                          1.36.8       5.mga5        x86_64  
  pango-doc                      1.36.8       5.mga5        noarch  
  pango-tests                    1.36.8       5.mga5        x86_64  
1.1MB of additional disk space will be used.
1MB of packages will be retrieved.
Proceed with the installation of the 9 packages? (Y/n) y

...

You should restart your computer for lib64pango1.0_0

#reboot

login to various desktops and run: 
$ killall mgaapplet
$ mgaapplet --testing

lxde: upgrade notification and icon presented
mate: upgrade notification and icon presented
cinnamon: desktop icons text changes with desktop / application focus.
          upgrade notification and icon presented
xfce: upgrade notification and icon presented
gnome: upgrade notification but no icon presented
gnome (classical):upgrade notification and icon presented (in hidden taskbar at bottom)
kde: upgrade notification and icon presented
lxqt: upgrade notification and icon presented
e18: no upgrade notification and icon presented


kde upgrade continuing....

(In reply to Lewis Smith from comment #41)
> Question (if it matters): how do you know whether Adwaita theme is being
> used, or if not, how to get it used.

In Xfce, Main Menu->Settings->Appearance

But for testing these updates, select oxygen-gtk. The aim is that the upgrade applet should still work properly in this case.

> 8. Restart mgaapplet from the command line by 'mgaapplet --testing'.
>  $ mgaapplet --testing
> Ignore the following Glib::Object::Introspection & Gtk3 warnings
> Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm
> line 296.
> Exception caught
> Exception: [metalink_helper.cc:118] errorCode=20 Could not parse Metalink
> XML document.
> error: Methodd 'aria2': gadael gyda 20

There was a problem here. I get the message

  retrieved testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1

This is where it retrieves the list of available Mageia versions from https://releases.mageia.org. A temporary glitch with the server maybe?

(In reply to ben mcmonagle from comment #43)
> (In reply to Lewis Smith from comment #42)
> > except it STOPPED/stuck after the last.
> > archwilio ffeil synthesis [/var/lib/urpmi/Tainted 32bit Updates (distrib87)/> > synthesis.hdlist.cz]
> 
> should then put the blue down arrow in the system tray (where updates
> notifier usually is)
Is this what Mertin means by:
 9. Accept the offer to upgrade to Mageia 6.
I expected a prompt of some sort. Never mind.

I have re-run this twice more from different desktops (XFCE, LXDE) with the same result, even leaving it for >20m. I have 6 desktops, 3880 packages, piles of accumulated junk; I wondered whether it was working out what it had to do.
The terminal does not return to the prompt. No Systray upgrade arrow.

(In reply to Martin Whitaker from comment #46)
> (In reply to Lewis Smith from comment #41)
> In Xfce, Main Menu->Settings->Appearance
> But for testing these updates, select oxygen-gtk. The aim is that the
> upgrade applet should still work properly in this case.
Thanks. Will look into.

> >  $ mgaapplet --testing
> > error: Methodd 'aria2': gadael gyda 20
> 
> There was a problem here. I get the message
>   retrieved testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1
> This is where it retrieves the list of available Mageia versions from
> https://releases.mageia.org. A temporary glitch with the server maybe?
That might be it. I am still getting this error this morning.

Will re-try tonight from XFCE with oxygen.

(In reply to Lewis Smith from comment #47)

> No Systray upgrade arrow.

Items numbered "2." and "3." in this may be relevant:
 
https://wiki.mageia.org/en/Mageia_6_Release_Notes#Upgrading_online.2C_using_mgaonline_.28GUI.29

- but I expected that the "testing" option would override those settings.

CC: (none) => jim

(In reply to James Kerr from comment #48)
> - but I expected that the "testing" option would override those settings.

Yes, it does, and from Lewis's earlier comment, that is working.

@Lewis, if you are still having trouble tonight, check the system log. You should see a message like:

mgaapplet[pid]: trying distributions list from https://releases.mageia.org/api/b/testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1

If it was successful, the next line would be:

mgaapplet[pid]: new '6' distribution was released on 20170601

but if not, there should be an error message.

To debug further, run the command:

curl 'https://releases.mageia.org/api/b/testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1'

(keeping the quotation marks) and attach the output here.

@Martin

Same problem tonight, even after re-adding 'coffee' mirror (my usual). I seem to have loads of mirrors configured, and no means of removing any:
 error: Methodd 'aria2': gadael gyda 20

> check the system log.
I did just
 $ journalctl
whose last message is: 
 Ion 28 19:44:28 localhost.localdomain mgaapplet[4220]: Packages are up to date

Noting James' advice in C48, I enabled 'check for new Mageia release' and re-try.
No change, still the Aria 2 error.
Ah - I notice I did not change the XFCE theme to Oxygen; will do, but will only report back if things advance. In fact, oxygen-gtk was already highlighted.

(In reply to Lewis Smith from comment #50)
> > check the system log.
> I did just
>  $ journalctl
> whose last message is: 
>  Ion 28 19:44:28 localhost.localdomain mgaapplet[4220]: Packages are up to
> date

You may need to run journalctl as root to see all the messages. The one we're interested in will be before any messages about checking the repos are up to date.

Also try the curl command I suggested (that doesn't need to be run as root).

kde x86_64 upgrade completed without any new issues

reboot from "congratulations " window does not work
reboot or shutdown from application menu does not work

reboot from konsole works

I noticed this morning that at one attempt, the 'aria2' error also occured part-way through the media checking list, as well as its ususal place at the start:
 mae'r cyfrwng "Tainted 32bit Updates (distrib87)" yn gyfredol
 ...methwyd estyn: Methodd 'aria2': gadael gyda 2
 mae'r cyfrwng "Nonfree Updates (distrib103)" yn gyfredol
---------------------------------------------
(In reply to Martin Whitaker from comment #51)
> You may need to run journalctl as root to see all the messages. The one
> we're interested in will be before any messages about checking the repos are
> up to date.
As root was unhelpful: it showed the first page since the year dot, and nothing would make it advance from there.
This is the best I can offer ($ journalctl):

Ion 29 12:25:18 localhost.localdomain mgaapplet[3744]: ### Program is starting ###
Ion 29 12:25:21 localhost.localdomain mgaapplet[3744]: running: ionice -p 3744 -n7
Ion 29 12:25:22 localhost.localdomain mgaapplet[3744]: trying distributions list from https://releases.mageia.org/api/b/testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1
Ion 29 12:25:23 localhost.localdomain mgaapplet[3744]: empty distribution list
Ion 29 12:25:23 localhost.localdomain mgaapplet[3744]: Computing new updates...
Ion 29 12:25:23 localhost.localdomain mgaapplet[3744]: running: mgaapplet-update-checker
Ion 29 12:25:23 localhost.localdomain mgaapplet-update-checker[3758]: ### Program is starting ###
Ion 29 12:25:25 localhost.localdomain mgaapplet-update-checker[3758]: running: urpmi.update --update
Ion 29 12:25:25 localhost.localdomain pkexec[3768]: pam_tcb(polkit-1:session): Session opened for root by lewis(uid=1001)
Ion 29 12:25:40 localhost.localdomain mgaapplet-update-checker[3758]: updating inactive backport media Core Backports (distrib7), Nonfree Backports (distrib17), Tainted Backports (distrib27), Core 32bit Backports (distrib34), Nonfree 32bit Backports (distrib39), Tainted 32bit Backports (distrib44), Core Backports (distrib52), Nonfree Backports (distrib62), Tainted Backports (distrib72), Core 32bit Backports (distrib79), Nonfree 32bit Backports (distrib84), Tainted 32bit Backports (distrib89), Core Backports (distrib97), Nonfree Backports (distrib107), Tainted Backports (distrib117), Core 32bit Backports (distrib124), Nonfree 32bit Backports (distrib129), Tainted 32bit Backports (distrib134)
Ion 29 12:25:40 localhost.localdomain mgaapplet-update-checker[3758]: running: urpmi.update Core Backports (distrib7)
Ion 29 12:25:40 localhost.localdomain pkexec[3798]: pam_tcb(polkit-1:session): Session opened for root by lewis(uid=1001)
Ion 29 12:25:41 localhost.localdomain mgaapplet-update-checker[3758]: running: urpmi.update Nonfree Backports (distrib17)
Ion 29 12:25:41 localhost.localdomain pkexec[3802]: pam_tcb(polkit-1:session): Session opened for root by lewis(uid=1001)
... etc etc ...
Ion 29 12:26:11 localhost.localdomain mgaapplet-update-checker[3758]: running: urpmi.update Tainted 32bit Backports (distrib134)
> on terminal: using mirror http://magie.remi.lu/distrib/5/x86_64
> then the hdlist.cz list
Ion 29 12:26:11 localhost.localdomain pkexec[3888]: pam_tcb(polkit-1:session): Session opened for root by lewis(uid=1001)
Ion 29 12:26:32 localhost.localdomain mgaapplet[3744]: Packages are up to date
Ion 29 12:27:01 localhost.localdomain su[3965]: pam_tcb(su:auth): Authentication passed for root from lewis(uid=1001)
Ion 29 12:27:01 localhost.localdomain su[3965]: (to root) lewis on pts/1
Ion 29 12:27:01 localhost.localdomain su[3965]: pam_tcb(su:session): Session opened for root by lewis(uid=1001)
---------------------------------
> Also try the curl command I suggested (that doesn't need to be run as root).
(keeping the quotation marks) and attach the output here:

 $ curl 'https://releases.mageia.org/api/b/testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1'
version=6,release_date=20170601,name="Mageia 6",desktop-update-end=20181201,basic-update-end=20181201,url=https://wiki.mageia.org/en/Mageia_6_Release_Notes,needs_preparation=0
version=5,release_date=20150619,name="Mageia 5",desktop-update-end=20161219,basic-update-end=20161219,url=https://wiki.mageia.org/en/Mageia_5_Release_Notes,needs_preparation=0
version=4,release_date=20140201,name="Mageia 4",desktop-update-end=20150802,basic-update-end=20150802,url=https://wiki.mageia.org/en/Mageia_4_Release_Notes,needs_preparation=0
version=3,release_date=20130518,name="Mageia 3",desktop-update-end=20141119,basic-update-end=20141119,url=https://wiki.mageia.org/en/Mageia_3_Release_Notes,needs_preparation=1,obsoleted_by=3
version=2,release_date=20120522,name="Mageia 2",desktop-update-end=20131122,basic-update-end=20131122,url=https://wiki.mageia.org/en/Mageia_2_Release_Notes#Upgrading_from_Mageia_1,obsoleted_by=3
version=1,release_date=20110601,name="Mageia 1",desktop-update-end=20121231,basic-update-end=20121231,url=http://www.mageia.org/,obsoleted_by=2
version=2010.2,release_date=20101222,obsoleted_by=1
version=2010.1,release_date=20100708,obsoleted_by=1
version=2010.0,release_date=20091103,obsoleted_by=none

Hope this lot helps.

(In reply to Lewis Smith from comment #53)
> (In reply to Martin Whitaker from comment #51)
> > You may need to run journalctl as root to see all the messages. The one
> > we're interested in will be before any messages about checking the repos are
> > up to date.
> As root was unhelpful: it showed the first page since the year dot, and
> nothing would make it advance from there.

Not to worry, the output you got as a normal user contains the necessary information. But for future reference, 'journalctl -b' will show the log since the last boot (and '-b -1' the log for the boot before, etc.).

> This is the best I can offer ($ journalctl):
> 
> Ion 29 12:25:18 localhost.localdomain mgaapplet[3744]: ### Program is starting ###
> Ion 29 12:25:21 localhost.localdomain mgaapplet[3744]: running: ionice -p 3744 -n7
> Ion 29 12:25:22 localhost.localdomain mgaapplet[3744]: trying distributions list from https://releases.mageia.org/api/b/testing-x86_64?product=Default&version=5&mgaonline_version=3.15.1
> Ion 29 12:25:23 localhost.localdomain mgaapplet[3744]: empty distribution list

This shows it tried to download the release information, but got nothing back. But your subsequent test with the curl command shows you can get the information. I'm suspecting a timeout - looking in the source code I see aria2 is run with a connection timeout of 6s and a download timeout of 3s. Let's trying forcing it to use curl instead. In the MCC, go to "Configuring media sources...", on the top bar select "Options"->"Global options" and change "Download program to use" to "curl", then try 'mgaapplet --testing' again.

It looks like you're waiting for feedback from Lewis, who has said he'll be offline for a few weeks.  Can someone else test with aria2 to see if you can reproduce the issue, and if it's just an aria2 issue, hopefully we can address that some how.

(In reply to David Walser from comment #55)
> It looks like you're waiting for feedback from Lewis, who has said he'll be
> offline for a few weeks.  Can someone else test with aria2 to see if you can
> reproduce the issue, and if it's just an aria2 issue, hopefully we can
> address that some how.

aria2 is the default method unless you select something else. I strongly suspect that Lewis's problem was due to his internet connection, so won't be reproducible by anyone else.

Hopefully that's the case.  It sounds like this one is probably good to go then.

Advisory committed to svn. I'd like to do some more testing before validating,
hopefully by tomorrow.

Keywords: (none) => advisory
CC: (none) => davidwhodgins

HI QATeam

Caused by the SSL certifiate error, the mgaapplet --testing is not working, tested changing the date to febrary 5 and disabling the NTP sync and appears the MGA upgrade icon

After clicking in the icon I see in the bash a segment violation
Retrying the test

CC: (none) => neoser10

Created attachment 9963 [details]
MGA seg violation after installing updates_testing and rebooting

Hi again QA

Enabled the MGA5 updates testing repo, installed the updates
Restarted machine
Configure your computer interface (MCC) tested in the following options without visual glitches:

1. Configure media for update
2. Sound configuration
3. Configure the X server
4. Network center
5. Configure the bootloader

Executing the mgaapplet --testing I got stuck in the "synthesis" message
Remembering the Claire's message few minutes after the SSL error shown in Mozilla Firefox... I changed the date as noted in the past message

Executing mgaapplet --testing I see the upgrade your system message
Clicking it, I saw in the bash console the segment violation messahe attached here

All the testing is in VBox, with a fully updated mga5 and KDE

(In reply to Mauricio Andrés Bustamante Viveros from comment #60)
> All the testing is in VBox, with a fully updated mga5 and KDE

I've had trouble getting mga5/KDE to run stably in VBox on a mga6 host recently. The latest mga6 updates plus limiting the guest to 1 CPU seems to have helped. Having got it to run, I can't reproduce the fault you are seeing.

Please try

  urpmi --downgrade mgaonline pango libpango1.0_0

with updates_testing disabled to revert these updates, then retry 'mgaapplet --testing'.

Hi again QA Team

I did the procedure in the comment 24, as root from the MCC application
The mgaapplet fails to open with violation if is run from root account

The mgaapplet runs as user, runs smoothly, the progress bars are OK, the cancel and restart buttons appears correctly but, the restart command did not work
Reviewing the Konsole, the mgaapplet restarts and tries to review if new updates are available, no restarting the computer after upgrade

Rebooting manually is difficult because the restart command from KDE menu only grays the screen, if the end user clicks on the workspace, the gradient disappears
I had to reboot using tty2 and issuing the control alt delete key comb

This MGA5 after updating the X rpm during the core updates application, fails to start X.... my workaround after trying every resolution and virtualbox video driver provided by Xorg without response (drakx11 did not feedback the end user with the X error while testing configuration), was delete from /etc/X11 the xorg.conf, the xorg.conf.test and xorg.conf.old and restart the machine to gain X access

Cause this, maybe the glitches with the mouse movements (loss reaction) all viewable in the video attached to this comment after update
Other glitch source can be the kernel used to boot the MGA6... I used the mga5 lastest kernel because the vbox fails to boot with the mga6 newest kernel, this does not happen with the mga6 core kernel

I will restart this test and confirm if the same issues appears

The mouse cursor is not visible, every time that I put the pointer in the mozilla firefox icon, the lock screen message appears, if i click in the mozilla, clock or sound icon, the lock icon is activated

https://drive.google.com/drive/folders/1CWWrbKdKX2xR9snG8T-TVvov40LsrkCV?usp=sharing
In the drive folder I have snippings and the video

PD:
Hardware: Virtual Box VM 5.1.12r112440
RAM: 1024 Mb
Disk: SATA Vbox drive 20 Gb
Sound: Intel HD

Host: Windows 7 SP1 x86
RAM: 4096 Mb
DISK: 1024 Gb
Processor: Pentium Dual COre E5200 2.5 Ghz

General problems with the upgrade should really be reported in other bugs. The updates here only address the issues with mgaonline. Having said that...

1. The restart button in the upgrade applet is disabled by --testing (see comment 31).

2. The inability to reboot KDE after upgrade has been reported before on qa-discuss. I doubt there's much we can do about that; KDE -> Plasma is a highly disruptive change. This won't matter so much when the restart button can be used.

3. You are using quite an old version of VirtualBox, so some of your post-upgrade problems could be due to that. See bug 21553 for a possible reason why you can't use the latest mga6 kernel.

Tested under vb for both i586 and x86_64.

The upgrade completed ok. There are problems after the upgrade (X fails to
start) which I still need to look into, so we are not ready to re-enable
the display of the option to upgrade using mgaonline.

Those are not related to this update though, so I'm validating the update.

Whiteboard: (none) => MGA5-32-OK MGA5-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0029.html

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