FEDORA-2019-18f7fc4f08

unspecified update in Fedora 31 for accerciser, atomix, & 50 more

Status: stable a month ago

GNOME 3.33.92

How to install

sudo dnf upgrade --advisory=FEDORA-2019-18f7fc4f08

Comments 25

This update has been submitted for testing by kalev.

This update's test gating status has been changed to 'waiting'.

This update has obsoleted sysprof-3.33.90-2.fc31, and has inherited its bugs and notes.

This update's test gating status has been changed to 'ignored'.

kalev edited this update.

This update has been pushed to testing.

Seems ok after few hours of usage.

karma: +1 critpath: +1 #1748463: +1

This appears to be a regression (from Fedora 30 anyway) https://bugzilla.redhat.com/show_bug.cgi?id=1749433

karma: +1 critpath: +1 #1748463: +1 Gnome Accessibility: -1 Gnome Lock Screen: +1 Gnome Maps: +1

Clicked +/- on the wrong test cases.

karma: +1 critpath: +1 #1748463: +1 Gnome Accessibility: -1 Gnome Lock Screen: +1 Gnome Maps: +1

This update can be pushed to stable now if the maintainer wishes

openQA test results are good, and looks OK on my desktop after a little bit of use.

karma: +1 critpath: +1 #1748463: +1

For case gnome-shell extensions install the testcase uses 'yum' command, i exchanged for 'dnf' and it listed extensions. 'gpk-applications' search for 'gnome-shell-extension' came up blank.

For case Gnome classic mode, after logging got an error screen. Couldnt do anything after.

For case Gnome Initial setup the error message was: utter-WARNING **: 22:46:37.744: Failed to create backend: Could not take control: GDBus.Error:System.Error.EBUSY: Device or resource busy

Would it be okay to substitute the instances of 'yum' in the Wiki test cases to 'dnf'?

Test Case Gnome Online Accounts Add Google - first time logging in, blank screen pops up and when the close button is closed the entire initial setup window closes. From the Settings panel/Online accounts panel, click the google item once will make a blank window appear, then closing it and clicking it a second time will make the Online accounts panel crash.

Test Case Gnome Online Accounts Add Windows Live - same as google.

Test Case Gnome Online Accounts Add Facebook - Looks like it works in initial setup, but when I go to settings/Online accounts, the account is not setup. When I click the add account link, a facebook login screen shows up, but when I enter username and password a blank screen shows up. Closing it and then trying to reclick the link will cause the app to crash.

works as expected

karma: +1 critpath: +1

This update has been submitted for stable by bodhi.

It works, but I have problems with Online accounts: Gmail stays blank, Nextcloud crashes #1749709

@alciregi, @dan1mal: are the online accounts issues a regression compared to what's in F31 stable?

Also, could someone file a bug against https://gitlab.gnome.org/GNOME/gnome-control-center and report the online accounts issue? It could also be a gnome-online-accounts bug, not gnome-control-center, but it doesn't super much matter which one to file against. Thanks!

@kalev My apologies, do you have a definition of 'regression'? Also, I thought F31 is the post-rawhide, and that it was NOT stable. I would be glad to file the bug, did you want it field at gnome or on redhat bugzilla? I did see this bug listed at the link you posted (https://gitlab.gnome.org/GNOME/gnome-control-center/issues/401), perhaps its related? And, are there any log commands that might be useful to run, and screenshot for the bug report? Any info would be helpful, I'm rather new at this. Thank you.

@dan1mal, We have a concept of updates that are being tested before being pushed to the base repository. This update is currently in "testing" state, and once it is verified to not cause additional issues compared to what's in the base repo, then it's moved to "stable". These two states correspond to the /etc/yum.repos.d/fedora.repo ("stable") and /etc/yum.repos.d/fedora-updates-testing.repo ("testing") repos.

The main thing here that's important to verify during testing is that it doesn't cause additional issues compared to what's in stable (doesn't cause regressions). No regressions mean that this update should be good to move to stable.

This doesn't mean that it's not important to find non-regression issues, but these should go to a bug tracking system and not block this update from being moved to stable. That's why I asked if this is a regression or not :)

Re https://gitlab.gnome.org/GNOME/gnome-control-center/issues/401, I doubt that's the same issue you are running into. Probably worth filing a new one and adding screenshots and anything that looks like relevant from 'journalctl -a -b'.

adamwill edited this update.

This update has been pushed to stable.

@kalev, I installed a new VM with 0905 compose. Performed a dnf update. And this time google online account works, as well as nextcloud.

@kalev, I haven't had a chance to install a previous compose, but may get to it tomorrow afternoon. But from @alciregi's comment this update would be a regression from the 0905 compose, correct?

On a side note, of good news, I forgot to mention it, but the new Gnome Desktop felt much more agile and responsive than in my F30 install.

Add Comment & Feedback

Please login to add feedback.

Content Type
RPM
Status
stable
Test Gating
Submitted by
Update Type
unspecified
Update Severity
unspecified
Karma
+6
stable threshold: 5
unstable threshold: -5
Autopush (karma)
Enabled
Autopush (time)
Enabled
Dates
submitted a month ago
in testing a month ago
in stable a month ago
modified a month ago

Related Bugs 2

00 #1747845 when the screen blanks (powersave), it can't be resumed
0+3 #1748463 GNOME 3.33.92 megaupdate should go in beta

Automated Test Results