Summary: | media-video/nvidia-settings-355.11 with x11-drivers/nvidia-drivers-355.11-r2 - file collision in /usr/lib/libnvidia-gtk2.so.355.11 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karol Krizka <kkrizka> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | bruce, chris, dark.knight.ita, email200202, fatzer2, gentoo-bugs, gokturk, jk, luksan, mail, marco.dr, Martin.vGagern, mihais23, mike, mr.pastafarianist, netbox253, silvio.gerli |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 562910 | ||
Bug Blocks: |
Description
Karol Krizka
2015-09-28 07:39:25 UTC
I'm having the same problem. Also, I generally use stable, but I keyworded nvidia-settings and nvidia-driver for this version because the stable nvidia-settings is asking to downgrade nvidia-driver (from 346.96 to 340.93, both stable versions). Something's not right in nvidia land. *** Bug 561702 has been marked as a duplicate of this bug. *** To prevent file file-collision you have to set "-tools" for nvidia-drivers. Same problem here. I try to unemerge nvidia-drivers, but it is impossible to install nvidia-settings without nvidia-drivers. (In reply to Christian Strahl from comment #3) > To prevent file file-collision you have to set "-tools" for nvidia-drivers. This should be done by the nvidia-settings ebuild by simply blocking nvidia-drivers[tools] (In reply to Sven Eden from comment #5) > (In reply to Christian Strahl from comment #3) > > To prevent file file-collision you have to set "-tools" for nvidia-drivers. > > This should be done by the nvidia-settings ebuild by simply blocking > nvidia-drivers[tools] This is odd. I just installed media-video/nvidia-settings-355.11 without disabling the tools USE flag on nvidia-drivers and it worked. Ah. I have set nvidia-drivers USE FLAGS to "tools -gtk2 gtk3" and for nvidia-settings to USE="-gtk3" So now nvidia-drivers own the gtk3-variant of the settings and nvidia-settings own the gtk2-variant of the settings. But if nvidia-drivers with the USE=tools install also all the utilities of the nvidia-settings, probably the package "nvidia-settings" are useless. I unemerged "nvidia-settings" and everything is the same. what do you think? Still UNCONFIRMED status, so I am chiming in to say I got this bug too. I have the same bug. * Detected file collision(s): * * /usr/lib/libnvidia-gtk2.so.355.11 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-drivers/nvidia-drivers-355.11-r2:0::gentoo * /usr/lib64/libnvidia-gtk2.so.355.11 * * Package 'media-video/nvidia-settings-355.11' NOT merged due to file * collisions. (In reply to Silvio from comment #7) > But if nvidia-drivers with the USE=tools install also all the utilities of > the nvidia-settings, probably the package "nvidia-settings" are useless. > > I unemerged "nvidia-settings" and everything is the same. > > what do you think? The nvidia-settings from the nvidia-drivers package sometimes does not work because it is linked against older ABI versions of system libraries. This happens from time to time. For a permanent availability we need the package nvidia-settings or the nvidia-drivers ebuild have to build nvidia-settings from source when USE="tools" is set. The /usr/bin/nvidia-settings command is installed by media-video/nvidia-settings. It is not installed by x11-drivers/nvidia-drivers even if the tools flag is set. # equery b /usr/bin/nvidia-settings * Searching for /usr/bin/nvidia-settings ... media-video/nvidia-settings-355.11 (/usr/bin/nvidia-settings) Why the Status is still "UNCONFIRMED"? Same situation here. File collision at /usr/lib/libnvidia-gtk3.so.355.11 (both packages +gtk3) Is any reason there to have a separate package for nvidia-settings? Currently I cannot uninstall them because of dependency to xfce-extra/xfce4-sensors-plugin (with VIDEO_CARDS=nvidia) My proposal is to change all dependencies from nvidia-settings to nvidia-drivers [+tools] and deprecate the nvidia-settings. (In reply to Alexander Weber from comment #13) > Is any reason there to have a separate package for nvidia-settings? > Currently I cannot uninstall them because of dependency to > xfce-extra/xfce4-sensors-plugin (with VIDEO_CARDS=nvidia) > > My proposal is to change all dependencies from nvidia-settings to > nvidia-drivers [+tools] and deprecate the nvidia-settings. See bug #414679. libXNVCtrl.a is required and is not provided by nvidia-drivers. See also bug #562910. Confirmed > But if nvidia-drivers with the USE=tools install also all the utilities of the nvidia-settings, probably the package "nvidia-settings" are useless.
And yet "app-admin/conky" with "nvidia" useflag depends upon "nvidia-settings"
I have this issue too. And I finally I hit this bug too when trying to update to nvidia-settings-355.11. So here is a summary of my nvidia-{settings|drivers} adventures since 6/8 months : 1 - nvidia-settings is installed as dependency of xfce-extra/xfce4-sensors-plugin 2 - when trying to update @world, newest stable nvidia-settings wants to force me to downgrade nvidia-drivers, but I can't. 3 - can't downgrade nvidia-drivers because of an upstream bug which was resolved in recents versions 4 - newest version of stable portage disallow me to update world until nvidia-{settings|drivers} conflict is not resolved 5 - can't update nvidia-settings to last unstable version because of this bug There is a request to merge the nvidia-settings into the nvidia-driver ebuild https://bugs.gentoo.org/show_bug.cgi?id=562910. Please vote for it or provide patch to move forward instead of waiting for this bug to be fixed. It is still "UNCONFIRMED". One workaround is to pump the version of nvidia-settings to 358.16 $ cd /usr/portage/media-video/nvidia-settings/ $ cp nvidia-settings-358.16.ebuild nvidia-settings-361.18.ebuild $ vi nvidia-settings-361.18.ebuild change the dependency to "x11-drivers/nvidia-drivers:0" $ ebuild nvidia-settings-361.18.ebuild digest $ emerge -av nvidia-settings $ nvidia-settings -v nvidia-settings: version 361.18 (portage@amd) Sun Jan 17 14:30:40 AEDT 2016 The NVIDIA X Server Settings tool. This program is used to configure the NVIDIA Linux graphics driver. For more detail, please see the nvidia-settings(1) man page. $ nvidia-settings ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at either /usr/share/nvidia/nvidia-application-profiles-358.16-key-documentation or /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot be prepopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions. I do not remember if this is a new error or exists in the old version. The problem is the ebuild will be deleted the next time you do "emerge --sync" I have nvidia-drivers 355.11-r2 and nvidia-settings is a part of it. $ qlist nvidia-drivers | grep nvidia-settings /etc/X11/xinit/xinitrc.d/95-nvidia-settings /opt/bin/nvidia-settings /usr/share/man/man1/nvidia-settings.1.bz2 Furthermore, typing `nvidia-settings` in the terminal does not produce any errors and the GUI configuration utility is started correctly. I still have this issue while updating to media-video/nvidia-settings-358.16. (In reply to Pastafarianist from comment #22) > I still have this issue while updating to media-video/nvidia-settings-358.16. try it with USE="tools" emerge --ask x11-drivers/nvidia-drivers Please use x11-drivers/nvidia-drivers[tools] instead. |