I am also seeing the issues that @xenithorb is seeing. After the update, I see the default wallpaper instead of the one I configured (though strangely, clicking on the "Activities" widget shows my configured background as the one in use?) and the main panel is missing. Right clicking on the desktop and selecting add default or empty panel does not work. I can only start applications with ALT-F2.
sqlalchemy-1.1.0 is not backwards compatible with 1.0.x. It's pretty late in the cycle to push a backwards incompatible change out to Fedora 25, given that changes were supposed to be in by the alpha for testing. I suggest considering holding this for Fedora 26 only.
I used fedpkg on EL 7 with bodhi 2.2.0 on EL 7 to submit a new Bodhi update for Bodhi to EL 7:
rbarlow@tesla ~/f/bodhi> bodhi --version 2.2.0 rbarlow@tesla ~/f/bodhi> fedpkg --user bowlofeggs update Password: ================================================================================ bodhi-2.2.0-2.el7 ================================================================================ Update ID: FEDORA-EPEL-2016-1f34e8df2b Release: Fedora EPEL 7 Status: pending Type: security Karma: 0 Request: testing Notes: Backport two patches to correct module paths from the devel branch : upstream. ---- Update to 2.2.0. Release notes : available at https://github.com/fedora- : infra/bodhi/blob/2.2.0/docs/release_notes.rst ---- : Updated to work better against bodhi2 with the latest : python-fedora bindings. Submitter: bowlofeggs Submitted: 2016-09-21 04:05:37 Comments: bodhi - 2016-09-21 04:05:38 (karma 0) This update has been submitted for testing by bowlofeggs. bodhi - 2016-09-21 04:05:43 (karma 0) This update has obsoleted bodhi-2.2.0-1.el7, and has inherited its bugs and notes.
Caveats: This update has obsoleted bodhi-2.2.0-1.el7, and has inherited its bugs and notes.
Thank you for backporting this fix for us! I was able to get this working, but I did have to also make a configuration change to get the VPN working. I had to edit the VPN connection, go to advanced settings, and uncheck the LZO option (in my particular case). After I did that, I was able to use the VPN as I used to be able to do.
In my opinion, it would be ideal if users didn't have to make any configuration changes in order to get this fix since the update that broke things (which seems to be NetworkManager-openvpn) was released during a stable Fedora 24 release. However, that wasn't your fault, so I'm going to mark this with positive karma.
Thanks so much!