Bug 31564 - MGA8 to MGA9 Upgrade of Cinnamon Desktop - loops on failing package upgrades
Summary: MGA8 to MGA9 Upgrade of Cinnamon Desktop - loops on failing package upgrades
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-16 17:23 CET by Brian Rockwell
Modified: 2023-03-08 11:13 CET (History)
1 user (show)

See Also:
Source RPM: Cinnamon Upgrade - MGA8 to 9 -
CVE:
Status comment:


Attachments
Error1 - without using http mirror for updated packages (iso is from15-Feb) (139.54 KB, image/jpeg)
2023-02-16 17:24 CET, Brian Rockwell
Details
Error2 - aftering using mirror updates upgrade stuck (179.58 KB, image/jpeg)
2023-02-16 17:25 CET, Brian Rockwell
Details

Description Brian Rockwell 2023-02-16 17:23:03 CET
Description of problem:  Incurred errors during upgrade from MGA8 to MGA9 in updated Cinnamon MGA8 environment


Version-Release number of selected component (if applicable): Cauldron, using classic installer  Res6 of mageia9-beta-classic-x86_64.iso


How reproducible:  Cinnamon upgrade from MGA8 to MGA9 and using legacy Nvidia 390 hardware (going from 390 to Nouveau in MGA9).


Steps to Reproduce:
1.  Run installation - choose upgrade - runs for a  long time then get error - attach error1
2.  System tries again - so I chose http and mirror to pull in new updates, this got past first error and then system would not budge on second errors (attaching 2nd screen shot)
3.  Could not get past this in upgrade, so just rebooted.  System came up with MGA9.
Comment 1 Brian Rockwell 2023-02-16 17:24:03 CET
Created attachment 13702 [details]
Error1 - without using http mirror for updated packages (iso is from15-Feb)
Comment 2 Brian Rockwell 2023-02-16 17:25:31 CET
Created attachment 13703 [details]
Error2 - aftering using mirror updates upgrade stuck

these look related to nvidia 390 driver not supported in MGA9.  So may be an errata.
Comment 3 Lewis Smith 2023-02-16 21:09:04 CET
Unsure about your reference to nVidia390. 340 *is* dropped, but 390 looks very present for M9:
 $ urpmq -y nvidia390
bumblebee-nvidia390
dkms-nvidia390
lib64primus-nvidia390
nvidia390-cuda-opencl
nvidia390-devel
nvidia390-doc-html
nvidia390-lib32
nvidia390-utils
primus-nvidia390
x11-driver-video-nvidia390

Re comment 1, the errors were for:
* /usr/share/metainfo/org.gnome.Terminal.Nautilus.metainfo.xml conflicts between new gnome-terminal-nautilus & old gnome-terminal
* new pidgin needs pidgin-i18n
* new gcc needs newer binutils
* new plocate needs liburing.so.2

Re comment 2, there are many different errors. But they are so basic that they suggest an update media problem.

If you have a bootable M9 (it looks like it), please (as root) compress and attach the file:
 /root/drakx/report.bug
[If you see also /root/drakx/report.bug.xz, this might apply to the original installation, not the upgrade. If the date/timestamp indicates it is for the upgrade, attach that directly].

And if the upgraded system works, does it update OK?

CC: (none) => lewyssmith
Status: NEW => NEEDINFO

Comment 4 Brian Rockwell 2023-02-17 16:02:52 CET
Hi Lewis,
report.bug doesn't exist in that folder, just the old report.bug.xz from 2022

What is new:
auto_inst.cfg.pl
ddebug.log

yes the system is up and running and updates are working.


-- a couple of other notes that may be important ... thinking about it now

1.  The /home is luks encrypted  (I was never prompted to unlock it)
2.  390 has never worked on M9 for my card 730GT.  It does work on MGA8.  My understanding is 390 is out of support by Nvidia, but the installer should have handled this situation and sent me to nouveau - which ultimately did happen on my forced restart.

The big issue to me is the installer looped out by consistently throwing the same error, trying again, again, again and not giving me a way out of that loop except to power down.
Comment 5 Pierre Opter 2023-02-17 17:15:50 CET
Hello to all

I hesitate to open a bug as this one seems to be close to the problem I have. Besides, I am not a developer nor a computer scientist and I am not very comfortable with the command line.

Two days ago I did the updates of my Cauldron via urpmi --auto-update on my test PC. It had been a long time since I had touched it. As a result, about 380 packages of updates are coming. 

During this update, a lot of errors are scrolling with obviously a Gnome / Cinnamon conflict.

Indeed I installed the Nemo package (that I like) but that comes, unless I'm mistaken, with Cinnamon dependencies. When I rebooted my test PC I got "Oh dear, something went wrong" :-( And the PC became unusable.

Apparently, from what I could see, Gnome / Cinnamon are in conflict :-(

Using the rescue mode and drakdm I tried to reboot the pc by trying to start it via XDM and not GDM but without success.

In any case I always end up with "Oh something went wrong".

So my test machine is crashed. It's not too bad. But what worries me is that I supervise 3 PCs that are currently in mageia 8 (my wife, my sister and my sister-in-law!). I don't want the day when mageia 9 will be deployed that I will have to reinstall 3 machines completely!

If I have to open a separate bug : don't hesitate.
If I need to place special orders so that I can report them to you, don't hesitate either!

And forgive me for my poor english and thanks to Deepl for helping me with the writing :-)

Thanks a lot for your help


Translated with www.DeepL.com/Translator (free version)

CC: (none) => p.opter

Comment 6 Pierre Opter 2023-02-17 18:51:42 CET
To complete my post, this PC that i used for tests is a Clevo base machine bought around 7 or 8 years ago at LDLC. So it's a full intel machine (graphic card, processor, sound card ....)
Comment 7 Lewis Smith 2023-02-17 22:16:40 CET
Thank you Brian for your further explanations. The lack of an upgrade log matters, and the screenshots imply some very general problem like repositories.
1) If the installer/upgrader should have migrated you to Nouveau for the nVidia 730GT graphics, that matters.
2) I hear often that /home is not fiddled with, hence its password not being asked for.
3)
> the installer looped out by consistently throwing the same error,
> trying again, again, again and not giving me a way out of that loop
Was the exact error significant, or just another of the many varied ones illustrated? Looping on an error is certainly not good. To push.
If we are clear about these points 1 & 3, they warrant separate bugs - but with good descriptions. For the moment, leave this bug for the Cinnamon upgrade glitches, as for Pierre.

@Pierre
Your problems may have something to do with bug 31570, bug 31571. Those are recent issues.
Please say what desktops you have.
And if you can, install & use lightDM rather than GDM, which is currently unsure.
Comment 8 Brian Rockwell 2023-02-20 05:02:58 CET
Error2 (screenshot 2) were the errors I was seeing that it looped out in.  I suspect even the errors in Error1 (screenshot 1) were causing an issue.
Comment 9 Lewis Smith 2023-02-20 20:52:50 CET
Let us confine this bug to the looping on failing package upgrades, attachment 2 [details] https://bugs.mageia.org/attachment.cgi?id=13703 , which looks a generic issue.

Assigning to MageiaTools.

Assignee: bugsquad => mageiatools
Status: NEEDINFO => NEW
CC: lewyssmith => (none)
Summary: MGA8 to MGA9 Upgrade of Cinnamon Desktop - errors => MGA8 to MGA9 Upgrade of Cinnamon Desktop - loops on failing package upgrades

Comment 10 Pierre Opter 2023-03-08 11:13:14 CET
(In reply to Lewis Smith from comment #7)
> Thank you Brian for your further explanations. The lack of an upgrade log
> matters, and the screenshots imply some very general problem like
> repositories.
> 1) If the installer/upgrader should have migrated you to Nouveau for the
> nVidia 730GT graphics, that matters.
> 2) I hear often that /home is not fiddled with, hence its password not being
> asked for.
> 3)
> > the installer looped out by consistently throwing the same error,
> > trying again, again, again and not giving me a way out of that loop
> Was the exact error significant, or just another of the many varied ones
> illustrated? Looping on an error is certainly not good. To push.
> If we are clear about these points 1 & 3, they warrant separate bugs - but
> with good descriptions. For the moment, leave this bug for the Cinnamon
> upgrade glitches, as for Pierre.
> 
> @Pierre
> Your problems may have something to do with bug 31570, bug 31571. Those are
> recent issues.
> Please say what desktops you have.
> And if you can, install & use lightDM rather than GDM, which is currently
> unsure.

@ Lewis Smith : i found the solution in the bug 31571 bugzilla thread. Thanks a lot for your help. My computer is only Gnome but i think with Cinnamon packages for Nemo. I can now launch Gnome with GDM :-) This bug is now closed for me.

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