Ugh, I completely missed that this contained a soname bump. I'm going on vacation at the end of this week and I don't think I will have time to do the rebuilds this week.

Can you take care of this please?

And sorry for making a mess of this.

goodmirek, I've just tried and my vbox vm works fine using the vboxguest video driver which comes with the 413 kernel. Likely the problem is that you are using a vboxvideo.ko driver built from the sources coming with the vboxguest additions and those have not yet been patched to work with 4.13 (somewhat old guest-additions?) anyways kernel 4.13 comes with vboxvideo.ko as part of the mainline kernel itself and this is enabled in Fedora.

In grub at " 3" at the end of the kernel commandline to boot to textmode, then do:

rm /lib/modules/kernel-4.13.1-302.fc27/misc/vboxvideo.ko depmod -a 4.13.1-302.fc27

Then reboot and then things should work fine.

"Transaction check error: File libGLX_indirect.so.0 in conflict with package nvidia-driver-libs-2:378.13-3.fc25.x86_64"

Hmm that is an issue with the negativo17 pkgs I guess ? I coordinated this fix with the rpmfusion people, with Simone in the Cc. I'll ask Simone to fix his packages.

This fixes #1419944 for me, +1

Ok, good news selinux-policy-3.13.1-225.10.fc25 fixes the ARM issue so as soon as FEDORA-2017-31d4ea5eb1 hits stable I can push this update to stable as well.

Ugh, sorry it seems that the selinux-policy update does not fix the ARM bug (typo in the new fcontext rule), see: https://bugzilla.redhat.com/show_bug.cgi?id=1419944

So sorry, looks like this needs to stay in testing a bit longer, hopefully not much longer ...

Ok, the selinux-policy update required to not break things on ARM has been filed: FEDORA-2017-31d4ea5eb1 as soon as that hits stable, I will push this update to stable too.

The libva update I've just added resolves https://bugzilla.redhat.com/show_bug.cgi?id=1422151, so we're almost there now.

Sorry people but you will have to re-add karma before I can push this.

nanonyme, recently 2 libglvnd related bugs have come to my attentention, which I want to see resolved both before pushing this to stable:

https://bugzilla.redhat.com/show_bug.cgi?id=1419944 A fix for this has been written, waiting for a new selinux-policy build with the fix.

https://bugzilla.redhat.com/show_bug.cgi?id=1422151 This just came in yesterday I will try to write a fix for this today.

The new libglvnd and mesa builds I've just added contain the proper upstream fix for the issue for steam games using the glfw library instead of my initial patch for this.

hansvon, the new libglvnd-0.2.999-9.gitdc16f8c.fc25 I just added contains a fix which fixes the 2 steam games which were not working for you. For technical details see: https://github.com/NVIDIA/libglvnd/pull/114

anonymous, about wayland not working with the nvidia binary driver, and more specifically at gnome/mutter not automatically falling back to Xorg and instead showing a black screen, can you please file a bug about that ?

The new wlc build I've just added should fix the issue with sway not starting (it does for me).

anonymous, yes wayland does not (yet) work with the nvidia binary driver, that is expected. This reminds me that we should make mutter do the right thing and auto-fallback to Xorg in that case. I've filed: https://bugzilla.gnome.org/show_bug.cgi?id=777985 for this.

hansvon, ok. I'm busy fixing sway today. I will look into this tomorrow, but no promises, fixing these without source access is going to be hard and the bug might well be in the actual games and just getting triggered by the glvnd changes.

hansvon, thanks for testing. Can you try downgrading mesa to the -5 from updates-stable and see if that fixes things ? I wonder if the problem is really in this update or somewhere else.

corsepiu, if you install a package from updates-testing please make sure you've all packages from updates-stable installed first. Can you please do this right (allow dnf to do its thing instead of manual installing) and then provide positive karma to compensate for your wrongly given negative karma?

If you're seeing broken deps because of this update, please add positive karma to: FEDORA-2017-9f6383547e

The mesa and libglvnd updates were supposed to go out as a pair. But then airlied did another mesa update with an unrelated bug-fix and bodhi failed to squash the 2 updates together (a bodhi bug IMHO) and now mesa is in updates-stable while the matching libglvnd update is not.

Leigh,

I know but I cannnot as removing the obsoleted mesa build has reset karma. I've asked rel-eng to fast-track this to stable.

Regards,

Hans