I guess there'll be some explanation why this doesn't work as expected. For example that it only affects flatpak applications (without being labeled as such). But unless I completely misunderstood something, this looks like a blocker bug to me. At the same time, I'd be +1 for waiving it at Go/NoGo, because it was obviously reported as a last-minute bug, but also because this has been present for a long time and we haven't seen any complaints about it.

-1 FinalBlocker

I think this is another example of the "basic functionality test" being too broad and too open to expansive interpretation.

I do think that this is confusing and should be better, but I think documenting it is sufficient. There are actually already other things in the same bit of the control panel that are confusing in the same way. For example, "Location services turned off: No applications can obtain location information" doesn't actually prevent Firefox from doing its own location thing.

Is there an upstream bug?

-1 FinalBlocker

I mean, I'm OK with the "basic functionality" wording, we just have to be firm about what's "basic", I guess :D

This actually is a fairly bad bug, but if it's been broken since F30 there's no point suddenly deciding to block on it now.

For the record, for me, "basic functionality" means the app broadly speaking works. You can type stuff in a text editor and save it. You can type stuff in a word processor and print it. For gnome-control-center I'd say it was intended to mean "you can run it and it's not completely broken; switching between panes works, it doesn't crash, it doesn't blow up when you click on a setting, the basic mechanism of actually toggling settings isn't completely broken". But not "every single setting it exposes must work".

-1 FinalBlocker , exactly what @adamwill says

FinalBlocker -1

At some point, we do have to draw the "basic" line.

FinalBlocker -1

FinalBlocker -1

FinalBlocker -1

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