This really sucks, but presumably everything else is still going to work, so:

FinalBlocker -1

Can't reproduce with RC1.4

Not breaking functionality

FinalBlocker -1
FinalFE +1

I wouldn't call this "basic functionality", but it would definitely be good to fix if we have a solution and do another RC.

Can't reproduce that bug here, me and other contributor also.
FinalBlocker -1

One consideration is this is (a) highly noticeable, and (b) cannot be fixed with an update post-install. If you have an affected install, you have to recover manually. You're permanently missing our default .bash_logout, .bash_profile, .bashrc, .kshrc, .mozilla, .zprofile, .zshrc... everything from /etc/skel. So this is actually probably worse than many of the issues we're considering as blockers....

Ouch, that a bad one then...

+1 FinalBlocker

I hate to vote this way at the last minute, but... if this can be consistently reproduced, it is a symptom of something very wrong with setting up home directories for user accounts, not a cosmetic problem.

FWIW, I have not seen it on about ~10 installs of Fedora Workstation over the course of the beta.

+1 FinalBlocker

I hate to vote this way at the last minute, but... if this can be consistently reproduced, it is a symptom of something very with setting up home directories for user accounts, not a cosmetic problem.

FWIW, I have not seen it on about ~10 installs of Fedora Workstation over the course of the beta.

Mat, but thats the point: as I see, It can't be consistently reproduced...

FinalBlocker -1

Mat, but thats the point: as I see, It can't be consistently reproduced...

Right, it seems to strike randomly. We know of only one other user who has reported it so far.

But if you are unlucky enough to be affected, it's quite bad.

Likelyhood seems low, but impact is severe, so

Can't reproduce with RC1.4

@augenauf There is no RC1.4. You're probably using the Beta image, while we're using Final RC1.3 image.

I'd suggest waiting on voting on this until we know more about it and we can run more installs. If we can reproduce this or if it happens often, I'd say this is a definite blocker, because missing the default user configuration will break a million things. But if this is a rare race condition which we can't figure out, we'll have to just accept it.

OK, I'll remove my vote until we know more.

FinalBlocker 0

@kparal , sorry I confused things. I’m using beta 1.4, not RC 1.3.

As suggested, revoking vote until we know more.

Yeah, this is clearly very severe when it happens, but doesn't seem to happen much (we have two recorded cases, AFAICS). Tricky. Especially since that will make it hard to debug.

FinalBlocker +1

No problem here R.C. 1.4
FinalBlocker +1

FinalBlocker -1
FinalFE +1

Appears like a very uncommon issue

FinalBlocker -1
FinalFE +1

FinalBlocker -1

on the grounds that we're not seeing a lot of reports and we don't have a reproducer.

FInalBlocker -1

Unable to reproduce on aarch64 Workstation RC 1.5.

FinalBlocker -1

unless somebody manages to reproduce this again.

FinalBlocker -1

FinalBlocker -1
FreezeException -1

At this point, seems clear this is rare.

FinalBlocker -1

The terminal shows {username@fedora}
Not bad that, I would not say that is a blocker..

jpbn

Sent with ProtonMail secure email.
------- Original Message -------
On Thursday, May 5th, 2022 at 18:06, Michael Catanzaro pagure@pagure.io w=
rote:

catanzaro added a new comment to an issue you are following:
At this point, seems clear this is rare. FinalBlocker -1

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-qa/blocker-review/issue/806

FinalBlocker -1

AGREED RejectedFinalBlocker

The following votes have been closed:

• Rejected FinalBlocker (+2, 0, -12)
  • +1 by asciiwolf, jpbn
  • -1 by catanzaro, bcotton, geraldosimiao, mattdm, humaton, somethingsomethingfedora, nb, coremodule, kparal, augenauf, sgallagh, mrinmoy

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