Bug 30780

Summary:	The entire Qt toolchain is broken on Mageia Cauldron after updating glibc and Qt libraries
Product:	Mageia	Reporter:	Lewis Goeroech <grclajos>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	critical
Priority:	release_blocker	CC:	fri, grclajos
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Lewis Goeroech 2022-08-27 22:07:33 CEST

Description of problem:
After updating glibc and Qt library files, I logged out of my Plasma session to switch to Cinnamon.

When came back to KDE, I noticed that only the Mageia Welcome screen and Steam were loaded, the screen behind them was completely black and there were no UI elements present on the screen.

When I went back to my login manager and switched tp GNOME, I also noticed that Qt-based applications like qBittorrent, CMake, Protonup-Qt (the locally compiled version, not the Flatpak), Dolphin, Okular, Gwenview, Spectacle, KCalc and many other programs also stopped working.

I also tried out LXQt, no success there, too.

As previously said, GNOME and Cinnamon still work fine and GTK-based applications also continued working flawlessly after the update, it is just that everything Qt-based stopped working.

How reproducible:

Every time you enable the Testing repositories and update glibc and the Qt toolchain.

Steps to Reproduce:
1. Enable the Testing repositories with your preferred method (RPMDrake, DNFDragora or CLI)
2.Check for updates and install them
3.Log out of your DE and log back in

Lewis Goeroech 2022-08-27 22:09:02 CEST

Priority: Normal => release_blocker
CC: (none) => grclajos

Comment 1 Thomas Backlund 2022-08-27 22:16:58 CEST

(In reply to Lewis Goeroech from comment #0)
>

> 
> Every time you enable the Testing repositories and update glibc and the Qt
> toolchain.


Here is your bug.

you have enabled testing and pulled in a half-built qt stack... so obviously stuff will break...

the whole reason for building it in testing is to avoid dev systems to break mid-upgrade of qt / kde / plasma stacks...

Just wait for it to land in release and you will have less breakages...

Comment 2 Lewis Goeroech 2022-08-27 22:31:09 CEST

(In reply to Thomas Backlund from comment #1)
> (In reply to Lewis Goeroech from comment #0)
> >
> 
> > 
> > Every time you enable the Testing repositories and update glibc and the Qt
> > toolchain.
> 
> 
> Here is your bug.
> 
> you have enabled testing and pulled in a half-built qt stack... so obviously
> stuff will break...
> 
> the whole reason for building it in testing is to avoid dev systems to break
> mid-upgrade of qt / kde / plasma stacks...
> 
> Just wait for it to land in release and you will have less breakages...

I know how to disable the repositories, but because the Mageia Wiki says that DNF and URPMI can't be used interchangably, and because I used URPMI and the RPMDrake front-end to install packages, how can I downgrade packages with URPMI?

Comment 3 Lewis Goeroech 2022-08-27 22:33:01 CEST

At least now the developers know there is an issue with Qt in the testing repositories.

It was worth a try.

Comment 4 Morgan Leijström 2022-08-27 23:09:26 CEST

$ sudo urpmi --test --downgrade --search-media 'Core Release' package1 package2 etc

no need to state version

Try to be lazy: it may just state a few key packages, and rest will be included by dependencies.

The "--test" makes it just resolve, show and download, not install.
Remove "--test" when you think it do the right thing.

CC: (none) => fri
Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 5 Lewis Smith 2022-08-28 09:22:31 CEST

> Every time you enable the Testing repositories
This looked to me a curious thing to do with a Cauldron system, and asking for trouble. Cauldron itself is essentially a testbed. tmb's comment 1 was very pertinent.