Airplane mode improperly activated on every startup violates basic release criteria Basic networking.

It must be possible to establish both IPv4 and IPv6 network connections using both typical router-provided addressing systems (e.g. DHCP on IPv4 or SLAAC or IPv6) and static addressing. The default network configuration tools for the console, for release-blocking desktops and for installer environments must work well enough to allow typical network connection configuration operations without major workarounds.

Common wireless network configurations using supported hardware as defined above are covered by this criterion.

FinalBlocker +1

FinalFreezeException +1

I don't think this will qualify as a blocker, because I'm completely certain this has behaved exactly like this for years. See my upstream comment. The closest criterion we have for this is this one (for System Settings):
https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Default_application_functionality

But it's not completely broken, it's just annoying. Activating the Airplane mode does deactivate BT+Wifi, that works. But when deactivating the Airplane mode, it enables BT when it shouldn't. And also if you want BT+Wifi disabled, you'll need to suffer with an airplane icon permanently visible. But it doesn't prevent cable networking or enabling BT or Wifi, it's just an annoying icon permanently visible. I don't think that violates basic functionality criterion.

FinalBlocker -1
FinalFreezeException +1

@kparal Thanks for the explanation. I haven't seen Airplaine mode myself in Gnome (it hasn't affected me), I only know it from smartphones. Your description shows me that it works different than I thought. So I agree with you now.

FinalBlocker -1
FinalFreezeException +1

FinalFE +1
FinalBlocker -1

FinalBlocker -1
FinalFreezeException +1

Surely you can't be serious.

FinalBlocker -1
FinalFE +1

Don't call me Shirley.

FinalBlocker -1
FinalFE +1

AGREED RejectedFinalBlocker AcceptedFinalFE

The following votes have been closed:

• Rejected FinalBlocker (+0, 0, -6)
  • -1 by imsedgar, kparal, gui1ty, geraldosimiao, bcotton, adamwill
• Accepted FinalFreezeException (+7, 0, -0)
  • +1 by tablepc, kparal, imsedgar, gui1ty, geraldosimiao, bcotton, adamwill

I don't think this will qualify as a blocker, because I'm completely certain this has behaved exactly like this for years. See my upstream comment.

FWIW I'm completely certain this is a regression in F37. There is no way I would have failed to notice airplane mode activating itself without my permission. It happens on every single boot since I upgraded to F37, and it never happened before.

But it's not completely broken, it's just annoying. Activating the Airplane mode does deactivate BT+Wifi, that works. But when deactivating the Airplane mode, it enables BT when it shouldn't. And also if you want BT+Wifi disabled, you'll need to suffer with an airplane icon permanently visible. But it doesn't prevent cable networking or enabling BT or Wifi, it's just an annoying icon permanently visible. I don't think that violates basic functionality criterion.

I'm not complaining that airplane mode is a little weird. I'm complaining that it actives itself on startup.

And also if you want BT+Wifi disabled, you'll need to suffer with an airplane icon permanently visible.

This was not true in F36 and it's not true in F37 either. I have bluetooth and wi-fi disabled right now, but airplane mode is not active.

There is no way I would have failed to notice airplane mode activating itself without my permission.

And I'm not disagreeing with you :D For some reason, this now affects you and it didn't before, not sure why. I'm just saying I've been living with this for years (probably on every system I used). Usually it's not a problem because I have wifi enabled almost all the time. But I just checked with my F36 laptop again, and it behaves exactly as you describe - the airplane mode gets activated on system boot, if wifi and BT are disabled. Even if I shuffle the sliders and convince GNOME not to show the airplane icon, after reboot, it's there. So while it's a regression for you, it's certainly not a regression in general, as I can demonstrate.

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