sudo dnf upgrade --refresh --advisory=FEDORA-2017-9f6383547e
This update has been submitted for testing by jwrdegoede.
Objecting this update in Fedora 25 as it is disruptive for sway WM as discussed: https://bugzilla.redhat.com/show_bug.cgi?id=1413579#c14 and on.
It also violates the update policy, specifically
Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience.
glvnd is an important F25 feature which has been widely advertised as such, see e.g. : https://blogs.gnome.org/uraeus/2016/11/01/discrete-graphics-and-fedora-workstation-25/
This is not something which we are doing lightly, I'm sorry that this breaks sway, but until yesterday I had never heard about sway. This is similar to how we do kernel or mesa updates, e.g. mesa has gone from 12.0 to 13.0 in F25's lifetime. Sometimes we need to find a balance between bringing in a new release which fixes bugs, vs potential new bugs this introduces. And yes enabling glvnd is ultimately a bug-fix as it stops things breaking every other update for nvidia driver users.
I've disabled auto karma based pushing for this and rest assured that if this causes any serious issues I will unpush this. But sway is such a niece use-case that I do not consider it a blocker for enabling glvnd support, sorry.
That only implies that the impact of the update at the cons side is not evaluated, which it likely should as mesa is on critical path.
@jwrdegoede: The fact that you have never heard of a package does not justify you to break it. Also the fact that you say is a nece (without data) does not justify you to break it.
Said so, I'm open to work with you to make adjustments to sway code or packaging to make glvnd not breaking it
Note also that main libglvnd maintainer was not in favor of proceeding
with such an update in Fedora 25:
Works well for me with Gnome3 on both Wayland and X11. Tested on an Optimus system with Intel and NVidia (through nouveau).
Works fine here with cinnamon using nvidia driver.
Works great! LGTM! =)
works for me
This update has been pushed to testing.
works fine an dandy for me :)
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
jwrdegoede edited this update.
You need to push libglvnd to stable to match the mesa update
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.
I've opened a FESCo ticket about this: https://pagure.io/fesco/issue/1675
Breaks sway windowmanager here :(
Package is uninstallable:
Error: Transaction check error:
file /usr/lib64/libEGL.so.1.0.0 from install of libglvnd-egl-1:0.2.999-7.gitdc16f8c.fc25.x86_64 conflicts with file from package mesa-libEGL-13.0.3-1.fc25.x86_64
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?
Fixes broken in F25 updates
works, using intel gfx and the modesetting driver.
Solved the broken mesa-13.0.3-4.fc25 dependencies.
@jwrdegoede: What I actually did was to run
# dnf update --enablerepo=updates-testing 'mesa-libGL*' 'libglvnd*'
to check if it resolves the current brokeness related to mesa/libglvnd in current "stable"
[How could this have happened? Does Fedora have any QA?]
# dnf update --refresh --enablerepo=updates-testing 'mesa-lib*' 'libglvnd*'
Works great! LGTM =)
This update has been submitted for stable by bodhi.
It seems this mesa/libglvnd update breaks Steam games on my intel integrated laptop. Steam, the browser, still works but games, tried two, segfault.
I'm going to unpush this and push it back to testing until there's a sway fix and other issues can be investigated. If thats going to take more than a day or two we should push a reverted mesa in the mean time.
This update has been unpushed.
kevin edited this update.
This update has been submitted for testing by kevin.
@kevin Now mesa isn't installable as well as the nvidia driver update.
Screw waiting for sway/wlc, the maintainer hasn't even filed an upstream issue!!!
steam-188.8.131.52-4.fc25 is working OK here (tested with dota2 vulkan).
Fedora 25 should not be broken so those problems should have been thought and investigated before pushing this package (and mesa) ahead
I've not yet understood what exactly created the problem and therefore I have no idea what to say to upstream (if you have, please submit the bug)
@hansvon said that Steam is broken with Intel hardware. The fact that it works with your Nvidia card does not really count as "hansvon problem is not a problem"
We get a major kernel update that breaks countless user setups more often than I change my pants :-)
Did you try running 'strace sway' to see any issues?
Either push to stable or remove. Community is already enabling updates-testing to fix the broken depenency so the situation is getting worse every passing moment. See https://bugzilla.redhat.com/show_bug.cgi?id=1417431
kalev edited this update.
This update has been submitted for testing by kalev.
Sorry for the edit spam. We ran into a bodhi bug here adding the mesa build to the update here.
A quick status update: I've reverted the libglvnd support in mesa -5 build which got fast tracked to stable, in order to fix broken deps in the stable builds. The mesa -6 update here now adds the libglvnd support back.
works fine for me on my trusty 64bit Machine
I made a few more tests with Steam (Intel laptop), running mesa -6. Most games I own run but not all:
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.
Yes, I'm back on -5 (had to remove libglvnd* with rpm -e --nodeps to downgrade mesa). Both games run fine.
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.
mesa-13.0.3-6.fc25 libglvnd-0.2.999-7.gitdc16f8c.fc25 + negative17 nvidia driver works for me only on x sessions. if i select the wayland session the screen stays black after login. but big improvement as i'm able to install the nvidia drivers at all an use them in some kind. handling my tipple head setup :)
using a lenovo t430 with nvidia nvs 5400m
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.
The new wlc build I've just added should fix the issue with sway not starting (it does for me).
I can confirm the new wlc build fixes the sway issue.
sway (and everything else I have) works fine now :) But please wait with push to stable for some days to see if there are other affected applications :)
I can confirm that sway works for me as well. I see a bug with some window decorators, but I don't think is anywhere related to this
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 ?
Works fine on x86_64.
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
@jwrdegoede thanks, that indeed solves the issue with these two games.
I can confirm the last libglvnd unbreaks several Steam games.
work for me
Works for me
OK here on x86_64.
I'm sorry but I am sick of this treating Nvidia like a first class citizen and shoving AMD by the wast side. Over the last 6 months all I heard is excuses of how LLVM versions can't be bumped mid release and other excuses. A large number of Radeon users have suffered because of this lack of tracking upstream versions more vigorously but when it comes to Nvidia RH is running around saying `yes sir yes sir'..
When it comes to a corporate agreement between RH and Nvidia these sweeping changes that break things for the community are pushed though hard and fast.
This update breaks many things for me locally as well as things like sway and seems to break many thing for other users. Why so much pressure to push this though before a next release, why not listen to your users that are clearly stating NO! Why tell users that only a small number use sway and therefore you don't care.
I fully expect the issue(s) will be fixed promptly enough but not until many users suffer from the fallout and the damage has been done because of this clearly disruptive change that should be been as a release milestone. This is utter crap and I expect better from the Fedora project.
Works for me
@funfunctor Please keep this kind of discussions related to bugs, not politics. You're commenting about bugs that were already fixed. If you find new ones, please file and link. Just FWIW you're completely wrong and airlied already commented earlier that he was planning on backporting LLVM soon and this libglvnd feature is currently blocking that. (I didn't ask why he was planning to go through the effort, I was just happy to hear he would) Please don't make things worse for the rest of us AMD hardware users by doing political downvotes
@funfunctor Please mind your tone. So far 2 issues were reported (sway broken, and 2 games not starting) and both have been resolved promptly. At this moment I see no outstanding issues. If you see some, please verify you have the latest versions are stated in this update. If the problems persist, please file a bug and link it here, I'm sure @jwrdegoede will look at it soon. The graphics driver team in Fedora are doing a great work and put a lot of effort into their tasks, considering it's just a handful of people.
The fact that you have a pet peeve on not having latest llvm in Fedora (yes, as an AMD user I'd love that as well) does not mean you need to block useful updates for Nvidia users just in spite. Btw this feature might be very useful even for AMD users once AMDGPU-PRO is libglvnd-enabled.
Update feedback: I have Radeon R9 270 and see no issues, desktop works, Steam games work.
@nanoyme Its not "political" and it is a policy violation, the Fedora policy is clear. Disruptive changes like this are for release milestones, its funny how the definitions change when a RH eng is making the change.
I didn't suggest airlied wasn't doing excellent work, in fact I made no mention of - what so ever - so you are making it political so don't!
@kparal I am not "block useful updates for Nvidia users just in spite" I am blocking it because its a Fedora policy violation and it created breakage. Its a highly disruptive change to make mid-release.
Your just a troll so drop dead.
looks good to me. no issues noticed.
Works for me.
It work for me
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.
I would provide karma for this, but it would most likely be ignored.
There is so far five negativa karma, and thirtyfour positive karma. Despite all this, it currently has a total karma of zero, and hasn't even been pushed to testing yet. What is the point of testing and adding karma, and then more testing and additional karma for the new build, if nothing is pushed to stable after two weeks?
Wake me up when F26 is released, then maybe this will finally be pushed stable. F26 release is what this update should have waited for in the first place.
Works fine here.
@jag: Whenever a build is added or removed, it resets karma. Also, it obviously requires a re-push to updates-testing, as you can see from bodhi comments. This update will stay in updates-testing until FESCo decides whether it is OK to go stable. See the devel mailing list.
new build works fine on x86_64.
Tried the latest build from updates-testing and none of my steam games appear to work without STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 on amdgpu/radeonsi. I tried Mad Max, The Long Dark and Hotline Miami. glxgears and other basic stuff seems to work correctly. After a forceful removal of libglvnd and downgrade to mesa-13.0.3-5 and my games run fine again.
Nope, scrap that, I didn't look careful enough and still had mesa-13.0.3-7 running. With mesa-libgbm-13.0.4-1 they all appear to be running great.
@kparal: I know all that, please reread my post. My point (which should be clear, but I will state the obvious) is: If this requires testing and retesting, with 44 karma added (-6, +38), submitted for testing eight times by three different people (including one stable submit / unpush), and_ still_ hasn't been submitted for stable after two weeks, maybe it should have waited until F26, hmmmmm?
Also, this currently has three karma, although four people have given positive karma. Shouldn't dutchy's negative karma be replaced by the positive karma given later, for a total of four?
No issues found with open AMD drivers
No regressions noted in a VM.
no regressions noted here
Works for me; tested in a VM under X11
@jwrdegoede is there any plan on getting this finally to stable now that FESco gave the ACK?
nanonyme, recently 2 libglvnd related bugs have come to my attentention, which I want to see resolved both before pushing this to stable:
A fix for this has been written, waiting for a new selinux-policy build with the fix.
This just came in yesterday I will try to write a fix for this today.
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.
Works in general, did not test the libva fix.
Works for me, AMDGPU system
@jwrdegoede Please be proactive in the further in communicating about blocker bugs in the future so people won't be left wondering whether this was just forgotten open
Works for me and allows multiseat systems with both Nvidia and Intel graphics cards to use all the seats
Things generally work now for me at last.
When this will be pushed to stable?
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.
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 ...
Welp, this was a trainwreck.
While extremely unfortunate, I don't see how a typo in SELinux policy constitutes a trainwreck
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.
It seems vainfo fails on optimus laptops in wayland session on intel driver, the error is
$ LC_ALL=C; LIBVA_DRIVER_NAME=i965 vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: User requested driver 'i965'
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
error: failed to resolve wl_drm_interface(): /lib64/libEGL.so.1: undefined symbol: wl_drm_interface
libva error: /usr/lib64/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
while it works if I logout and back in using Xorg on nvidia drivers
I am using negativo17's nvidia drivers.
Everything else seems to be fine
@aditya1212 do you have the libva-intel-driver 1.7.3-2 from rpmfusion? It's supposed to fix libva on wayland. From the changelog:
This update has been submitted for stable by jwrdegoede.
Yups, sorry seems I should have used --refresh flag to force dbcache update.
This update has been pushed to stable.
this seems to break it for people running proprietary nvidia drivers - https://devtalk.nvidia.com/default/topic/996408/linux/quadro-k620-on-fedora-25-unable-to-load-the-nvidia-drm-/
Potentially coincidence. There were some comments in related selinux-policy update that it started causing nvidia kernel module loading failures.
WFM with the official nvidia installer but only if I select the option to install & overwrite the existing libglvnd installation.
This breakes vmplayer 12.5.2 (and probabbly other versions) running a Windows 7 VM (with signal 11). Downgrading to 13.0.3-5 resolves the issue. Based on other comments stating this also breaks some games, it appears to me this version is not stable enough, although it may seem to light users.
In addition to the above comment: Graphics card is i7 Intel HD Graphics 4000
This is already in stable so giving this negative karma has no impact. Please file bugs.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2022 Red Hat, Inc. and
bodhi-server 6.0.0 on
bodhi is Free Software.
if you have any problems. Read the documentation.