I found the following BZ ticket which explains this situation...
FreeCAD chose to use PySide over PyQt so this (and a couple of other
packages) are preventing me from switching it over to Qt5.
Is there anyone interested in getting PySide2 in Fedora and willing to
submit a Review Request? I'll volunteer to be the reviewer..
== Summary ==
Remove all the deprecated 389-console packages: 389-console,
389-ds-console, 389-admin-console, 389-dsgw, 389-admin, and
389-adminutil. These packages are for the old JAVA UI for 389
Directory Server. We have a new web UI that is replacing these java
== Owner ==
* Name: [[User:mreynolds| Mark Reynolds]]
* Email: mreynolds(a)redhat.com
== Detailed Description ==
The java packages have already been deprecated, and we'd like to
remove them in F31(rawhide)
== Benefit to Fedora ==
Cleaning out old deprecated packages
== Upgrade/compatibility impact ==
There are no manual changes that need to be done once this product is removed.
== How To Test ==
The package should no longer be available
== User Experience ==
Users will no longer be able to use the old java UI, and they must now
use the new cockpit UI plugin for managing the directory server.
== Dependencies ==
There are no dependencies as we are trygin to remove the entire
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change),
== Documentation ==
It has been announced upstream via mailing lists that the 389-console
package suite was being replaced by a cockpit plugin. But there was
no other type of announcement done yet.
Fedora Program Manager
I've got a 100% reproducible crash with Firefox on Wayland, but
I've run into a brick wall getting it properly reported.
Neither coredumpctl nor abrt even report a crash, so no coredump file
exists. I was advised in my bug report that abrt doesn't provide
useful information anyway , so I should collect it directly with
The problem I then encountered: the laptop becomes a hair dryer and
unresponsive for at least 60 minutes with zero crash information
written out, so I gave up. I've processed coredumps from other
applications before with gdb, it usually takes less than a minute.
Anyway, it seems like a problem if possibly the most popular
application on Fedora is this difficult to debug.