Description of problem: Screen blank option could not be changed. open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Version-Release number of selected component (if applicable): F37 Pre-Release testing How reproducible: open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Steps to Reproduce: 1. 2. 3. Actual results: open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Expected results: Changed option should be saved. Additional info:
Proposed as a Blocker for 37-beta by Fedora user naraiank using the blocker tracking app because: ### CANDIDATE COMPOSE ### == Blockers == Description of problem: Screen blank option could not be changed. open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Version-Release number of selected component (if applicable): F37 Pre-Release testing How reproducible: open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Steps to Reproduce: 1. 2. 3. Actual results: open gnome control center and go to power options, there try to change screen blank option and close the window. When re-open, the default option re-appears. Expected results: Changed option should be saved. Additional info:
I can confirm this with gnome-control-center-43~beta-1.fc37.x86_64. Not only "Screen Blank" changes are ignored, "Power Button Behavior" changes are ignored as well. @knaraian Can you please file a bug upstream at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues and link it here? Thanks!
There is a workaround - you can set "Blank Screen Delay" from Privacy -> Screen, and that change is remembered. There seems to be no workaround for "Power Button Behavior", though.
A blocker discussion ticket: https://pagure.io/fedora-qa/blocker-review/issue/854
+4 in https://pagure.io/fedora-qa/blocker-review/issue/854 , marking accepted.
Proposed as a Blocker for 37-beta by Fedora user naraiank using the blocker tracking app because: Standard operation.
This is already accepted as a Final blocker, which is the point at which we block on things like this. There is no relevant criterion at Beta.
(In reply to Kamil Páral from comment #2) > I can confirm this with gnome-control-center-43~beta-1.fc37.x86_64. Not only > "Screen Blank" changes are ignored, "Power Button Behavior" changes are > ignored as well. > > @knaraian Can you please file a bug upstream at > https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues and link it > here? Thanks! Is it compulsory for me to open gnome ticket?
(In reply to K Naraian from comment #8) > Is it compulsory for me to open gnome ticket? Nothing is compulsory for you in Fedora, so I don't really understand the question. But if you want to see it fixed, you need to report it to GNOME developers to their upstream tracker, they (mostly) don't follow Fedora bugs. So the best approach is to report it upstream, and if you want to propose it as a Fedora release blocker, then make a very short Bugzilla report here (just a link to the upstream ticket) a use it to propose the blocker. But never mind, as this was accepted as a blocker, I wanted to report it upstream myself, and found the issue already present there. No further action needed. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025
*** Bug 2119952 has been marked as a duplicate of this bug. ***
(In reply to Kamil Páral from comment #9) > (In reply to K Naraian from comment #8) > > Is it compulsory for me to open gnome ticket? > > Nothing is compulsory for you in Fedora, so I don't really understand the > question. But if you want to see it fixed, you need to report it to GNOME > developers to their upstream tracker, they (mostly) don't follow Fedora > bugs. So the best approach is to report it upstream, and if you want to > propose it as a Fedora release blocker, then make a very short Bugzilla > report here (just a link to the upstream ticket) a use it to propose the > blocker. > > But never mind, as this was accepted as a blocker, I wanted to report it > upstream myself, and found the issue already present there. No further > action needed. > https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025 Thanks a lot. Any way thank you for letting me know how gnome bug tracker helps in resolving the issue. But I thought, the developer would have more stronger presence to the Gnome bugs tracker. Any how, I will try to escalate gnome issues to gnome bugs tracker, from next on..
(In reply to Kamil Páral from comment #9) > https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025 Fixed in upstream repo.
*** Bug 2118956 has been marked as a duplicate of this bug. ***
Proposing as a Beta FE too, as this is annoying and affects live boot and first boot so can't be fixed fully with an update. Technically speaking, these really were two separate bugs - they're just *similar*. But upstream decided to combine them so I guess we can too. :D
FEDORA-2022-bf857cfff3 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf857cfff3
FEDORA-2022-bf857cfff3 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-bf857cfff3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf857cfff3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/854 (the bot's count of +2 is because one comment is slightly misformatted), marking accepted Beta FE.
FEDORA-2022-bf857cfff3 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
I verified that this is fixed with gnome-control-center-43~beta-2.fc37.x86_64