I can easily reproduce this both on my desktop and in a VM. ABRT doesn't show any crashes, which is its basic functionality. A blocker per https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Default_application_functionality

FinalBlocker +1

Actually, it seems to be a race :-/

Although it seems to be a race, it cannot be fixed by restarting one's computer. I have tried several times to reboot the machine and I could not report anything in about 40% of cases.

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1
AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+4, 0, -0)
  • +1 by kparal, lruzicka, frantisekz, adamwill

Let's re-evaluate this one at Monday's meeting. It doesn't look like we've been able to reproduce it for close to two weeks now.

I'm gonna propose we re-vote this one.

The bug is still present in RC2 (there's a potential fix that arrived this morning). But it's definitely intermittent, and it goes away on reboot.

The bug was accepted as a blocker as a violation of the "basic criteria" requirement for default-installed desktop apps (so in this case, the crash viewer). With the information we currently have, I would argue against that. The bug doesn't always happen, and when it does happen, always seems to affect only the very first boot; it works OK after a reboot. To me that's not serious enough to violate this criterion or any other I'm aware of. So:

REVOTE FinalBlocker
FinalBlocker -1

@lruzicka @kparal @frantisekz revote time

FinalBlocker -1

My only hesitation is that every boot of a live image is the first boot, but it doesn't affect every first boot and it doesn't really impact what people would actually use a live image for so...

Yeah, and filing crashes from the live image is...well...if retrace server doesn't have everything it'll never work, and it gets increasingly useless over time as the versions are older and older.

FinalBlocker -1

Ok, good revoting...

FinalBlocker -1

Although I was the one proposing this originally, I have learnt over time that this does not have an impact that is worth blocking. We could easily describe this behavior in the CommonBugs to notify power users that something like that might be an issue for them.
However, if regular users use their Fedoras, they will never know about crashes when Abrt will not tell them, so they will probably have rebooted many times, until their first serious crash occurs and that one will be caught and reported.

FinalBlocker -1
CommonBugs +1

If we could reproduce it deliberately, I'd vote +1. But we can't.

FinalBlocker 0

always seems to affect only the very first boot

Unless something changed in the last updates, that's not correct. It seems to affect each boot randomly. Either it's a race, or there's some trigger we're not aware of.

FinalBlocker -1

FinalBlocker -1

Since this looks to get rejected as a blocker, please vote for a freeze exception to push the available fix.

FinalFE +1

FinalFE +1

FinalFE +1
AGREED RejectedFinalBlocker AcceptedFinalFE

The following votes have been closed:

• Rejected FinalBlocker (+0, 1, -7)
  • 0 by kparal
  • -1 by adamwill, bcotton, sgallagh, geraldosimiao, lruzicka, jmaybaum, catanzaro
• Accepted FinalFreezeException (+3, 0, -0)
  • +1 by kparal, geraldosimiao, adamwill

Release F37 is no longer tracked by BlockerBugs, closing this ticket.