[Desktop-packages] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
It is nearly impossible to know what the OpenCL programs require specifically. E.g., I did some testing and boinc-amd-opencl seems to work with the ICD loader by ocl-icd-libopencl1 but not with the specific one by fglrx; on the contrary, oclHashcat needs the specific libOpenCL.so.1 by fglrx but fails to run with the other; and yet sgminer will run with either. On the other hand, in a 64-bit system it is not enough to provide libopencl1 (as I suggested in #117) because wine depends on wine-i386 (and so on libopencl1:i386 too), but awkwardly fglrx-core:amd64 installs the 32-bit /usr/lib32/libOpenCL.so.1. -- 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: [SRU] 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: Fix Released Status in fglrx-installer-updates source package in Trusty: Fix Released 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: Fix Released Status in fglrx-installer-updates source package in Utopic: Fix Released 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: [Impact] * wine and fglrx are not coinstallable. [Test Case] * try to install them * there is a conflict with libopencl1 in control file, preventing coinstallation. 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
[Desktop-packages] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
That is the problem: There should be only one loader but there are two of them. fglrx at least (I ignore what is the case for nvidia) provides its own at /usr/lib/libOpenCL.so.1 and this conflicts with the one by ocl-icd-libopencl1 that goes to /usr/lib/x86_64-linux- gnu/libOpenCL.so.1. Both are the same version and the latter takes precedence, which is not what some software expects. -- 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: [SRU] 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: Fix Released Status in fglrx-installer-updates source package in Trusty: Fix Released 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: Fix Released Status in fglrx-installer-updates source package in Utopic: Fix Released 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: [Impact] * wine and fglrx are not coinstallable. [Test Case] * try to install them * there is a conflict with libopencl1 in control file, preventing coinstallation. 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
[Desktop-packages] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
It is still not fixed for me: If we do not explicitly provide libopencl1, wine still requires ocl-icd-libopencl1 which installs a conflicting libOpenCL.so -- 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: [SRU] 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: Fix Released Status in fglrx-installer-updates source package in Trusty: Fix Released 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: Fix Released Status in fglrx-installer-updates source package in Utopic: Fix Released 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: [Impact] * wine and fglrx are not coinstallable. [Test Case] * try to install them * there is a conflict with libopencl1 in control file, preventing coinstallation. 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:
[Desktop-packages] [Bug 1270960] Re: totem fails to open unable to load to egl-wayland
** This bug is no longer a duplicate of bug 1206371 libhybris breaks mesa (cannot find libwayland-egl.so.1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1270960 Title: totem fails to open unable to load to egl-wayland Status in libhybris package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: After recent updates; I can't open totem, it fails with: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory which doesn't seem right. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 20 18:54:58 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: totem UpgradeStatus: Upgraded to trusty on 2013-09-10 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1270960/+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 1270960] Re: totem fails to open unable to load to egl-wayland
I do not have libhybris and I have never installed it. It is obviously a separate issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1270960 Title: totem fails to open unable to load to egl-wayland Status in libhybris package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: After recent updates; I can't open totem, it fails with: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory which doesn't seem right. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 20 18:54:58 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: totem UpgradeStatus: Upgraded to trusty on 2013-09-10 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1270960/+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 1310492] Re: Hidden files in the home folder are being displayed by default every time a new window is opened or the application relaunched.
*** This bug is a duplicate of bug 1247221 *** https://bugs.launchpad.net/bugs/1247221 ** This bug has been marked a duplicate of bug 1247221 Nautilus doesn't remember setting for showing hidden files correctly when org.gtk.Settings.FileChooser show-hidden is true -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1310492 Title: Hidden files in the home folder are being displayed by default every time a new window is opened or the application relaunched. Status in “nautilus” package in Ubuntu: Confirmed Bug description: When I open nautilus, a new window to the home folder, the hidden files get displayed by default even if their display is toggled off. Even though this is very minor issue, it is very distracting for the user to see all the hidden files every time he/she opens or launches a new window using nautilus. This is strictly a graphical issue. I am using Ubuntu 14.04. To reproduce the issue, - Open nautilus or launch a new window which displays the home folder. - You will find the hidden files being displayed by default. - Hide them using Ctrl+H and close that window. - Open the home folder again, and you can notice that these hidden files being displayed by default again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 12:51:58 2014 GsettingsChanges: InstallationDate: Installed on 2014-04-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1310492/+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 1176304] Re: If I run 'startx' then I cannot login again to my account.
At least in my case, what happens is that .Xauthority is owned by root after running startx (as root). A workaround: sudo rm ~/.Xauthority I am not sure to which extent this constitutes a bug, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1176304 Title: If I run 'startx' then I cannot login again to my account. Status in “xorg” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 12.10 Release: 12.10 xorg: Εγκατεστημένα: 1:7.7+1ubuntu4 Υποψήφιο: 1:7.7+1ubuntu4 Πίνακας Έκδοσης: *** 1:7.7+1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I expected to have only startx but I had startx and then I could not login again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sat May 4 12:08:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-25-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GeForce GT 620 [10de:0f01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:8a91] MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=8ED80C71D80C5A3B loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd09/07/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1176304/+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 933300] Re: nm-applet needs restart after resume
*** This bug is a duplicate of bug 780602 *** https://bugs.launchpad.net/bugs/780602 Aaron, this bug has been fixed in a recent update. Maybe you are experiencing bug #1011073 which is fixed in precise-proposed and the fix should be in updates soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/933300 Title: nm-applet needs restart after resume Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: STR: 1) Resume from suspend, nm-applet displays no network connection (that has been the case on this computer for a long while, other computers on my network reconnect automatically) 2) Click on nm-applet and select the network ER: * nm applet starts animating and connects AR: * Nothing happens. I need to `pkill nm-applet nm-applet `, then I can choose my network and continue. I'm not sure when it started, I think only a few days ago ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: f26299558349e6bfa9a64225e1770925 CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Thu Feb 16 08:45:17 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10 metric 2 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-01-16 (30 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/933300/+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 865672] Re: Adobe Flash Player Settings dialog does not respond to mouse clicks
You do not need the closed-source Google Chrome just to run its Flash
plugin. It is also available in Chromium:
chromium --ppapi-flash-path=libpepflashplayer.so --ppapi-flash-
version=VERSION
You can extract the libpepflashplayer.so from chrome package. E.g., first
download
https://dl.google.com/dl/linux/direct/google-chrome-
stable_current_amd64.deb
and extract it:
ar p ./chrome.deb ./data.tar.lzma | xzcat | tar xO
./opt/google/chrome/PepperFlash/libpepflashplayer.so
./libpepflashplayer.so
The Flash version is available in the package manifest:
ar p ./chrome.deb ./data.tar.lzma | xzcat | tar xO
./opt/google/chrome/PepperFlash/manifest.json | grep version
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/865672
Title:
Adobe Flash Player Settings dialog does not respond to mouse clicks
Status in Chromium Browser:
New
Status in Compiz:
New
Status in The Mozilla Firefox Browser:
New
Status in Midori: Webkit Web browser:
Invalid
Status in Unity Distro Priority:
Fix Released
Status in “adobe-flashplugin” package in Ubuntu:
Triaged
Status in “chromium-browser” package in Ubuntu:
Invalid
Status in “firefox” package in Ubuntu:
Invalid
Status in “midori” package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1) Open a flash file. Be it a game, video, website, etc.
2) Right click on the flash player and select Settings
3) Try to click on something in the dialog box such as a checkbox or a tab
What is expected to happen:
The dialog box responds to user input, e.g. checking a checkbox or switching
to a different tab.
What happens instead:
The dialog box does not respond. Nothing happens when the user interacts with
it. The user must refresh the page to exit the dialog box.
Workaround #1:
1) Go to
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html#117645
2) Configure your Flash Player settings using the Settings Panel
Workaround #2:
1) Open Flash in fullscreen mode
2) Open Settings and configure your preferences
ORIGINAL DESCRIPTION:
Adobe flash player is configured on my system to ask before a website sets a
flash cookie, so if a video (eg on youtube) is played, a dialogue box will pop
up asking me whether or not to allow the website to store a cookie on my
machine. However, nothing happens when I click on either 'allow' or 'deny', so
the box stays put and I can't view or control the video playing beneath it.
On this machine I upgraded from 11.04 to 11.10; in 11.04 there was a program
for adjusting the flash player settings in the System Settings control panel,
but that program is no longer there and not accessible via the dash, so there
is no obvious way to just configure flash to allow all cookies and avoid the
dialogue box.
Workaround: using Unity 2D instead
Notice : the problem has been already corrected two years before :
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/410407?comments=all
I'll add that it's perhaps because of Compiz : It works with Unity 2d, KDE,
Gnome-Shell, Gnome-Session-With-No-Effect BUT it affects Ubuntu 3D,
Gnome-Session Fallback and Cairo-Dock session
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sean 1362 F pulseaudio
/dev/snd/pcmC0D0p: sean 1362 F...m pulseaudio
BuildID: 20110929002329
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 44'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,104383ce,0014'
Controls : 12
Simple ctrls : 7
Channel: release
Date: Mon Oct 3 12:51:36 2011
ExecutablePath: /usr/lib/firefox-7.0.1/plugin-container
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232},
Version=2.1.4, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
IpRoute:
default via 10.10.88.1 dev wlan0 proto
[Desktop-packages] [Bug 871728] Re: network manager forgets wifi password on suspend/restart
Since gnome3, NetworkManager no longer uses GConf but writes on /etc/NetworkManager/system-connections/ The 'available to all users' workaround has the main problem that then for the imported accounts this will save passwords to etc in plaintext and no longer in the encrypted gnome-keyring. If your network password is part of another account (eg LDAP) this can be a problem. So the solution would be to remember the password in the keyring as it was before instead of forgetting it (there is the option psk-flags=1 in system-connections which apparently could be used for that) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/871728 Title: network manager forgets wifi password on suspend/restart Status in “network-manager” package in Ubuntu: Confirmed Bug description: I've been keeping up with the oneirc updates, but within the past couple of days, the network manager has forgotten my wifi password, and every time I suspend or restart the computer I have to enter the password again. Looking at the password and keys setting application, there no longer appears to be a 'Network Secret' saved for my home (or work) wifi account, although there are some other less-used networks still in there. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Mon Oct 10 22:39:53 2011 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 10.1.1.1 dev wlan0 proto static 10.1.1.0/24 dev wlan0 proto kernel scope link src 10.1.1.8 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 IwConfig: Error: [Errno 2] No such file or directory Keyfiles: Error: [Errno 2] No such file or directory NetDevice.eth0: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=3c:4a:92:50:86:b4 NetDevice.lo: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=00:00:00:00:00:00 NetDevice.wlan0: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=4c:0f:6e:40:78:a0 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory SourcePackage: network-manager UpgradeStatus: Upgraded to oneiric on 2011-09-27 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/871728/+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 854833] Re: (oneiric) wireless passwords not remembered
In my case (WPA enterprise with TTLS) the password is remembered independently of the available to all users option. The problem is that since oneiric it is stored in /etc/NetworkManager as plaintext and not in the keyring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/854833 Title: (oneiric) wireless passwords not remembered Status in “gnome-keyring” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Triaged Bug description: With an up to date (as of 20 Sept) Oneiric beta, I have to re-enter the wireless password for all of my standard networks every time I log in. Expected behaviour is that Ubuntu remembers them. This is a regression from previous behaviour --- ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 10.45.43.1 dev eth0 proto static 10.45.43.0/24 dev eth0 proto kernel scope link src 10.45.43.13 10.45.43.0/24 dev wlan0 proto kernel scope link src 10.45.43.94 169.254.0.0/16 dev eth0 scope link metric 1000 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-11-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-09-07 (13 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/854833/+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 839767] Re: Saved wireless networks/VPNs unavailable after Oneric upgrade
to trigger the migration, you can open gconf-editor and set apps/nm- applet/stamp to 2. This should migrate the network settings (and reset then stamp to 3 automatically) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/839767 Title: Saved wireless networks/VPNs unavailable after Oneric upgrade Status in “network-manager” package in Ubuntu: Triaged Bug description: I just upgraded to Oneric (via update-manager -d), and now my saved network passwords and vpns are no long available. I can connect to wireless networks and re-enter passwords, and they persist (they show up in the 'Edit Connections' dialog), but the old networks do not. I do see the new networks in /etc/NetworkManager/system-connections. What's strange is that is see the old connections and vpns in gconf- editor under /system/network/connections. Was there something that was supposed to run and migrate these settings out of gconf? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 2 13:16:59 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.109 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to oneiric on 2011-09-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/839767/+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 885934] Re: Double clicking on a date in the calendar of the clock applet does not open evolution
It is especific of gnome-panel but not of gnome-classic session. Running gnome-panel on gnome-shell or unity also has the same problem. In all cases, running gnome-panel from the terminal displays the Cannot open display: error whenever the calendar is clicked. Additionally, I would like to clarify that the evolution calendar events are correctly displayed; it is just the editing that does not work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/885934 Title: Double clicking on a date in the calendar of the clock applet does not open evolution Status in Evolution Data Server: New Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: I am running the gnome-classic session with compiz in Oneiric. Whenever I double a click on a date in the calendar of the clock applet nothing happens. Starting the gnome-panel from the terminal I receive a message that indicates the problem. The message is Cannot open display:. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/885934/+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 885934] Re: Double clicking on a date in the calendar of the clock applet does not open evolution
** Also affects: evolution-data-server Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/885934 Title: Double clicking on a date in the calendar of the clock applet does not open evolution Status in Evolution Data Server: New Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: I am running the gnome-classic session with compiz in Oneiric. Whenever I double a click on a date in the calendar of the clock applet nothing happens. Starting the gnome-panel from the terminal I receive a message that indicates the problem. The message is Cannot open display:. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/885934/+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
