[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
And yes, xrandr at all times shows this: andrew@desky:~$ xrandr --verbose Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 DisplayPort-0 connected primary 1920x1080+0+0 (0x5a) normal (normal left inverted right x axis y axis) 480mm x 270mm Identifier: 0x55 Timestamp: 9033 Subpixel: unknown Gamma: 0.92:0.94:0.90 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 3 4 5 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00001e6d355b01010101 0b1a0104a53c2278fb7b45a4554aa227 0b5054210800714081c0810081809500 9040a9c0b3002a4480a0703827403020 3500e00e111e00fd00284b55 5512010a20202020202000fc004d 503539470a20202020202020023a8018 71382d40582c4500e00e111e016f 02031cf149900403011012101f132309 0707830165030c00123a8018 71382d40582c4500fe22111e011d 007251d01e206e285500fe22111e 8c0ad08a20e02d10103e9600fe221100 0018 00e2 GAMMA_LUT_SIZE: 4096 range: (0, -1) DEGAMMA_LUT_SIZE: 4096 range: (0, -1) GAMMA_LUT: 0 range: (0, 65535) CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 DEGAMMA_LUT: 0 range: (0, 65535) TearFree: auto supported: off, on, auto subconnector: Native supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled vrr_capable: 1 range: (0, 1) max bpc: 8 range: (8, 16) underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, on, auto scaling mode: None supported: None, Full, Center, Full aspect link-status: Good supported: Good, Bad CONNECTOR_ID: 94 supported: 94 non-desktop: 0 range: (0, 1) 1920x1080 (0x5a) 174.500MHz +HSync +VSync *current +preferred h: width 1920 start 1968 end 2000 total 2080 skew0 clock 83.89KHz v: height 1080 start 1083 end 1088 total 1119 clock 74.97Hz 1920x1080 (0x5b) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x5c) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x5d) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1680x1050 (0x5e) 146.250MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.29KHz v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz 1400x1050 (0x5f) 121.750MHz -HSync +VSync h: width 1400 start 1488 end 1632 total 1864 skew0 clock 65.32KHz v: height 1050 start 1053 end 1057 total 1089 clock 59.98Hz 1600x900 (0x60) 108.000MHz +HSync +VSync h: width 1600 start 1624 end 1704 total 1800 skew0 clock 60.00KHz v: height 900 start 901 end 904 total 1000 clock 60.00Hz 1280x1024 (0x61) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x62) 106.500MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew0 clock 55.93KHz v: height 900 start 903 end 909 total 934 clock 59.89Hz 1280x800 (0x63) 83.500MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew0 clock 49.70KHz v: height 800 start 803 end 809 total 831 clock 59.81Hz 1152x864 (0x64) 81.768MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew0 clock 53.79KHz v: height 864 start 867 end 871 total 897 clock 59.97Hz 1280x720 (0x65) 74.250MHz +HSync +VSync h: width 1280 start 1390 end 1430 total 1650
[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
Been a while, but now that I'm on 21.10, colord is not picking up all devices once again - just one monitor and printer... andrew@desky:~$ sudo colormgr get-devices-by-kind display [sudo] password for andrew: Object Path: /org/freedesktop/ColorManager/devices/xrandr_LG_Electronics_MP59G_16843009_andrew_1000 Owner: andrew Created: March 18 2022, 12:32:29 AM Modified: March 18 2022, 12:32:29 AM Type: display Enabled: Yes Embedded: Yes Model: MP59G Vendor:LG Serial:16843009 Seat: seat0 Scope: temp Colorspace:rgb Device ID: xrandr-LG Electronics-MP59G-16843009 Profile 1: icc-0ce2e8ad3e9d95972c92b26c7cf1ff76 /var/lib/colord/icc/MP59G #1 2019-04-20 08-41 2.2 F-S XYZLUT+MTX.icc Profile 2: icc-47d27b769d969b5b00c90fa6a22b30db /home/andrew/.local/share/icc/edid-6f5d0bc1638b2166d7bc7cba7f413205.icc Profile 3: icc-cc0f880e5208bfe2b012688549fa1d31 /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S XYZLUT+MTX.icc Profile 4: icc-275750a8cb6525973773ab3c4861e84e /home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc Metadata: OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712 Metadata: OutputPriority=primary Metadata: XRANDR_name=DisplayPort-0 Metadata: OwnerCmdline=/usr/bin/kded5 Reinstall colord and this is the result: andrew@desky:~$ sudo colormgr get-devices-by-kind display [sudo] password for andrew: Object Path: /org/freedesktop/ColorManager/devices/xrandr_DisplayPort_0_andrew_1000 Owner: andrew Created: March 18 2022, 01:06:41 AM Modified: March 18 2022, 01:06:41 AM Type: display Enabled: Yes Embedded: Yes Model: MP59G Vendor:LG Serial:16843009 Seat: seat0 Scope: temp Colorspace:rgb Device ID: xrandr-DisplayPort-0 Profile 1: icc-6cc2fc162f8d590624da325d5aecf601 /var/lib/colord/icc/MP59G #1 2021-07-23 11-58 2.2 F-S XYZLUT+MTX.icc Profile 2: icc-275750a8cb6525973773ab3c4861e84e /home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc Profile 3: icc-cc0f880e5208bfe2b012688549fa1d31 /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S XYZLUT+MTX.icc Metadata: OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712 Metadata: OutputPriority=primary Metadata: XRANDR_name=DisplayPort-0 Metadata: OwnerCmdline=/usr/bin/kded5 Object Path: /org/freedesktop/ColorManager/devices/xrandr_DisplayPort_1_andrew_1000 Owner: andrew Created: March 18 2022, 01:06:41 AM Modified: March 18 2022, 01:06:41 AM Type: display Enabled: Yes Embedded: Yes Model: MP59G Vendor:LG Serial:16843009 Seat: seat0 Scope: temp Colorspace:rgb Device ID: xrandr-DisplayPort-1 Profile 1: icc-cc0f880e5208bfe2b012688549fa1d31 /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S XYZLUT+MTX.icc Profile 2: icc-275750a8cb6525973773ab3c4861e84e /home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc Metadata: OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712 Metadata: OutputPriority=primary Metadata: XRANDR_name=DisplayPort-1 Metadata: OwnerCmdline=/usr/bin/kded5 Picks up both screens, looses the printer. Next reboot, right back at square one where colord only picks up one monitor and the printer until I reinstall colord, and once I do that I can see both monitors but not the printer... *SIGH* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module Status in colord package in Ubuntu: New Bug description: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.
[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
Well, colord no one tracks bugs (and I see lot's of ancient and very open bugs). Seen a couple that may or may not be similar, and the bugs go all the way back to 11.04 - so I guess I'm the only person in the entire world experiencing this... But in case not, this problem would have a downstream effect on other projects: gnome-color-manager (in my case it's pulled in by colord-kde). Perhaps it's a problem in libxrandr2? I'm not fully sure of the interrelations between the libraries for xrandr, colormgr, X, KDE, Gnome, etc... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module Status in colord package in Ubuntu: New Bug description: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
Okay, if I do a reinstallion of colord, I can see both monitors and actually set the profile on the second screen. I lose the printer profile upon doing this. This works until next reboot and then everything reverts (only see one monitor and the printer color profiles). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module Status in colord package in Ubuntu: New Bug description: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
>From system settings, I can see both monitors in Display configuration. >From command prompt, I can see both displays when I use xrandr. >From command prompt, I can only see one display when I use colormgr get- devices-by-kind display Did not have this issue with Kubuntu 20.10. My notebook, which hasn't been upgraded from 20.10 yet (I'll hold off) does not have this issue and it does show all display devices in Display Configuration, useing xrandr from command prompt, and colormgr from command prompt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module Status in colord package in Ubuntu: New Bug description: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934409] [NEW] Only one monitor showing in Color Corrections - System Settings Module
Public bug reported: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module Status in colord package in Ubuntu: New Bug description: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Actually looking at my nVidia equipped system, the nVidia packages installed on it, and my AMD system and the AMD packages installed on it right now... Thinking about it, shouldn't the AMD driver depend on ocl- icd-libopencl1 package? Should the AMD pacakge be broken up into seperate packages like the nVidia one (which would enable quicker bug and/or updates to portions of it and such). Just food for thought. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/11294
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Well, in respect to what I see in the nVidia drivers (nvidia-opencl- icd-331-updates) and in the AMD drivers, shouldn't there be an enhances line (Enhances libopencl1) - the AMD driver is afterall providing enhancements, but in it's base package as opposed to a seperate opencl pacakge... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.ne
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Sorry for pointing that out - I just want to see this fixed right the first time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
I posted on bug # 1376587... I fixed a couple bugs regarding the AMD Catalyst drivers... Okay, so the replaces line needs to change to this: Enhances: libopencl1 Replaces: fglrx-driver-core Provides: fglrx-driver-core, opencl-icd, amd-opencl-icd Fresh install, I had to get rid of libopencl1 in the repalces line as it causes a fight between packages.. I added the enhances line becasue, well, it enhances OpenCL with GPGPU support. This allow's both the updates driver from the repo's and the drivers form AMD's website to install with wine gracefully. Why the Enhances line - I noticed that OpenCL wasn't working on my system. SO a few more changes was in order: In /usr/lib I create thed following symlink: libOpenCL.so and pointed it at libOpenCL.so.1 Then I created two more symlinks for completness: libOpenCL.so.1.1 and libOpenCL.so.1.2 and both of those pointed to libOpenCL.so (I did this incase AMD or someone decides that proviced libOpenCL.so.1 file name should be corrected to libOpenCL.so). I then did the same in /usr/lib32 Then I went into /etc/OpenCL/venders and coped amdocl64.icd in the same dir but called it amdocl32.icd I edited that file, and changed libamdocl64.so to libamdocl32.so Next, in /etc/ld.so.conf.d I made a file called opencl-vender-amd.conf and add the line: /etc/OpenCL/venders I then ran ldconfig to finalise the settings. Wine works fine as well as GPGPU accelerated OpenCL (tested with BOINC). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
