[Bug 1163013] New: access to /dev/nvidia* no longer possible after update
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 Bug ID: 1163013 Summary: access to /dev/nvidia* no longer possible after update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: P.Suetterlin@royac.iac.es QA Contact: sndirsch@suse.com Found By: --- Blocker: --- I updated my TW system to the G05 series from the nvidia repository. After that, SDDM wouldn't start anymore, leaving me only with a black screen and mouse cursor. The logfiles revealed the greeter couldn't create an OpenGL context. So I activated autologin for sddm, so I could work, and next noticed that I cannot use accelerated glx stuff. After a *lot* of hunting around and comparing with the old, still working snapshot, I realized that the update had removed the file /usr/lib/tmpfiles.d/nvidia-logind-acl-trick.conf that created neccessary links in the uaccess part of the /run filesystem, so that systemd-logind would allow access to the /dev/nvidia* files. I noticed the file is still mentioned in the postuninstall scripts section of nvidia-gfxG05-kmp-default: lux:~% rpm -q --scripts nvidia-gfxG05-kmp-default | grep -B 1 acl-trick # cleanup of bnc# 1000625 rm -f /usr/lib/tmpfiles.d/nvidia-logind-acl-trick.conf But nothing seemed to have created it when installing the package :( The BNC thread is quite old - is this still the official method to get access to the device files, or did I miss some change? TW 20200201 nvidia-gfxG05-kmp-default-440.44_k5.3.12_2-22.1.x86_64 nvidia-computeG05-440.44-22.1.x86_64 nvidia-glG05-440.44-22.1.x86_64 x11-video-nvidiaG05-440.44-22.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c1 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |P.Suetterlin@royac.iac.es Flags| |needinfo?(P.Suetterlin@roya | |c.iac.es) --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Creation of this file has been moved to trigger script. Check with rpm --triggers vidia-gfxG05-kmp-default Maybe you can still remember, what you have done exactly? Possibly such things may happen, when updating from G04 to G5 driver series RPMs. It shouldn't happen when just updating G05 to the latest version. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c2 --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Indeed this file is being deleted when updating from G04 driver RPMs to G05 drivers RPMs (%postun of G04 kmp running after %trigger of G05 kmp). But if you're trying to do this you run into package conflicts, which you need to resolve manually. I never planned to support this and added the conflicts between G0X and G0Y (X != Y) packages by intention. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- And the issue does not happen when updating G05 driver RPMs ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c4 --- Comment #4 from Peter Sütterlin <P.Suetterlin@royac.iac.es> --- Thanks for the fast response (as always ;^>) I had done a 'zypper dup' to 20200201, then (without previous reboot) a 'zypper in' for the 4 relevant packages. Yes, I had been running G04 before, until I realized I can/should use G05 with my 1060 card. Zypper was then finding the conflicts with the G04 version, and I selected the option to remove them. Since then I had (twice) switched between G04 and G05 using zypper as above, neither way the file got re-created. So as you suspect, that might be the reason. Ah yes, I see it now in the -q --triggers output. So it seems that didn't get triggered the way I installed? Would adding the snippet to create the tmpfiles.d entry (also) to the postinstall script catch this (without hurting otherwise)? Or is it rather that the postuninstall of the old package runs after the file has been created by the new version? In any case, it's maybe not the most common thing to switch between the two, so feel free to close as 'worksforme'.... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c5 Peter Sütterlin <P.Suetterlin@royac.iac.es> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(P.Suetterlin@roya | |c.iac.es) | --- Comment #5 from Peter Sütterlin <P.Suetterlin@royac.iac.es> --- So I'll watch the file during coming updates... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163013 http://bugzilla.opensuse.org/show_bug.cgi?id=1163013#c6 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |INVALID --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- [x] Or is it rather that the postuninstall of the old package runs after the file has been created by the new version? This one. :-) Yeah, let's close it as INVALID. I could add more magic to %postun of kmp in order to figure, that there is still some other KMP around, but things are getting more and more complicated. And as said before you're overwriting conflicts here ... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com