I opened up a couple of web pages, they worked fine

my simple personal playbook runs fine

@danniel, I'd be very interested to know how you made it work. Please share the details, thank you.

thanks, Zim now starts properly on F33 and seems to work OK

#1860616 and #1873029 are fixed, that's an improvement. #1878317 is not fixed, which makes abrt still completely broken. I believe we should push this stable so that at least some of the improvements get into F33. But this update is still not sufficient to make ABRT actually work, a further update is needed.

processes are displayed just fine

my system boots

sudo efibootmgr -v seems to print correct output, I haven't tested anything else

I'm able to unlock my encrypted partitions during boot

I was able to pair my bluetooth mouse

my autofs mounts are automounted and autounmounted just fine

I can't report a single crash due to #1873029 . I couldn't report any crash before, so this is not making it worse, I'm not giving negative karma. But ABRT is still completely broken.

system stats seem to be printed fine

No issues in my personal small playbook, but please see @mhael's comment

mangohud vkcube and mangohud glxgears looks fine, the overlay is there

I tested mediainfo command with multiple video formats and image formats, output seems valid

I can run my flatpak apps even from the command line

I see images and descriptions in gnome-software

I can't report a single bug through ABRT because of:

Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' with curl: Could not resolve host: retrace.fedoraproject.org
Error: curl_easy_perform: Couldn't resolve host name
('report_uReport' exited with 1)

The problem is that it doesn't even allow me to create the trace and report the bug to bugzilla manually. It fails immediately because FAF is down and no further action is available.

I have a script using python-bugzilla for adding attachments to bug reports, and it works fine.