Message boards :
Number crunching :
Anybody run into troubles with the Nvidia 410.78 driver update in Linux?
Message board moderation
Author | Message |
---|---|
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
So I got offered the update from my current 410.73 drivers to a minor update of 410.78. Found out it will not run nvidia-settings now without an error. root@Serenity:/home/keith/Desktop# /usr/bin/nvidia-settings libEGL warning: DRI2: failed to authenticate (nvidia-settings:3214): GLib-GObject-CRITICAL **: 16:49:45.561: g_object_unref: assertion 'G_IS_OBJECT (object)' failed libEGL warning: DRI2: failed to authenticate ** Message: 16:49:46.239: PRIME: No offloading required. Abort ** Message: 16:49:46.239: PRIME: is it supported? no Anybody else run into this issue yet and can offer a fix? All my Google searches don't turn up anything relevant for the error. I have none of the factors or applications in any of the hits. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
bluestar Send message Joined: 5 Sep 12 Posts: 7408 Credit: 2,084,789 RAC: 3 |
Which ones? |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
Well I got brave and applied the update to a second computer. Same errors but this time each nvidia-settings parameter command actually applied. So now it is just a cosmetic issue it seems as I can't detect any harm in the error message so far. I'm surprised that these error messages haven't been discussed in the forums. So something changed in one of the applied driver updates that now throws the libEGL failed to authenticate error every time nvidia-settings is invoked. Still have heard nothing from the ppa maintainers. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
juan BFP ![]() ![]() ![]() ![]() Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 ![]() ![]() |
Just updated and no issue at all. At least for now. ![]() |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
Just updated and no issue at all. Did you get the libEGL error message after a nvidia-settings call in Terminal? [Edit] I posted ANOTHER message in the Ubuntu.org forums hoping to attract any attention to the issue. Even though it seems to be benign I want to understand what is causing it. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
juan BFP ![]() ![]() ![]() ![]() Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 ![]() ![]() |
Just updated and no issue at all. Not see any. But i have too much alcohol in my system to be sure. Lol ![]() |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.