[Desktop-packages] [Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
The is an update: https://bugs.kde.org/show_bug.cgi?id=370975 Problem is not udisk, is Solid component. Patch available there (Comment 50) https://bugs.kde.org/show_bug.cgi?id=370975#c50 ** Bug watch added: KDE Bug Tracking System #370975 https://bugs.kde.org/show_bug.cgi?id=370975 ** Package changed: udisks2 (Ubuntu) => solid (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it Status in solid package in Ubuntu: New Bug description: There is a Fix proposed from comment 36 https://bugs.kde.org/show_bug.cgi?id=370975 I have this problem when trying to mount any removable device or internal disk partition, either from Dolphin or from removable device manager in panel. It always shows an error message when you try to mount the device first time, the device is not opened in Dolphin but it is mounted correctly. Then at the second attempt it does not show error message and device is opened in Dolphin. The messages that I get in Spanish: From Dolphin: "Ocurrió un error al acceder a «Carpeta personal», el sistema respondió: El dispositivo ya está montado: Device /dev/sdb3 is already mounted at `/media/yafu/PART 1'." From removable device manager in panel a window message titled "Error Cliente KIO ?" and "Formato de URL erroneo" message. By the way, in a recent Dolphin update, when you mount partitions from the small folder/home icon to the left of the Dolphin address bar (that icon only appears if you have Panels > Places disabled), every time you Mount a device from there that menu is filled enormously with "Umount <>" items. Really annoying. === Related messages in English: "Error KIO Client" with the text "malformed URL" "An error occurred while accessing 'Home', the system responded: The device is already mounted: Device /dev/sdl1 is already mounted at '/media/myuser/disk title'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
Well, I have been able to solve the problem and I am able to use nvidia driver again. The problem is that nvidia-prime blacklist nvidia driver. The file is "/etc/modprobe.d/blacklist-nvidia.conf" with content: # Do not modify # This file was generated by nvidia-prime blacklist nvidia blacklist nvidia-drm blacklist nvidia-modeset alias nvidia off alias nvidia-drm off alias nvidia-modeset off File was never re-established, even when uninstalling/purging nvidia- prime package. I think that this file should be re-established/deleted when you uninstall nvidia-prime. Thanks Alberto and other maintainers for your hard work maintaining nvidia packages ( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
(after entering user key) must be > (after entering my user password) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
Hi. I do not know if I am currently being affected by the same Bug. My system is: intel i7 3770 (HD4000 igpu) nvidia GTX 960 I have Kubuntu 18.04 updated to date. I was using 390.48 nvidia proprietary driver correctly. I decided to try nvidia-prime in Kubuntu 18.04, so from the BIOS I enabled iGPU as the primary display. I opened nvidia-settings GUI and from Prime options I chose Intel. After entering user password, it took about a minute for the message to appear that the change had been successful. So I rebooted the system and it worked correctly, the system was using intel iGPU. But then when trying to return to nvidia something went wrong. After rebooting the system, PRIME options of nvidia-settings GUI disappeared. nvidia-settings GUI is only shown in the minimal version, only items from Application Profiles and nvidia-settings Configuration is displayed. If I select my nvidia as a Primary Display from BIOS, the system enters in graphic mode but it apparently is not using nvidia driver, system and graphics work very slow and take time to refresh. nvidia-settings GUI just keeps showing minimal interface with almost no options. All this despite the fact that from the terminal, PRIME is informed that nvidia is selected: $ sudo prime-select query nvidia I have tried to purge all nvidia package and reinstalling the driver from driver manager, but everything remains the same. Since troubleshooting nvidia problems is more difficult with new packaging system: https://askubuntu.com/questions/1011589/what-has-changed-in-nvidia-proprietary-driver-packaging-in-18-04-bionic I do not know if I did it right. These are the packages that I currently have installed: http://pasteall.org/915940 Just a question to see if I can reverse PRIME changes. Which configuration file is modified when you select nvidia or intel from PRIME options in nvidia-setings GUI (after entering user key)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1762163] [NEW] [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
Public bug reported: There is a Fix proposed from comment 36 https://bugs.kde.org/show_bug.cgi?id=370975 I have this problem when trying to mount any removable device or internal disk partition, either from Dolphin or from removable device manager in panel. It always shows an error message when you try to mount the device first time, the device is not opened in Dolphin but it is mounted correctly. Then at the second attempt it does not show error message and device is opened in Dolphin. The messages that I get in Spanish: >From Dolphin: "Ocurrió un error al acceder a «Carpeta personal», el sistema respondió: El dispositivo ya está montado: Device /dev/sdb3 is already mounted at `/media/yafu/PART 1'." >From removable device manager in panel a window message titled "Error Cliente KIO ?" and "Formato de URL erroneo" message. By the way, in a recent Dolphin update, when you mount partitions from the small folder/home icon to the left of the Dolphin address bar (that icon only appears if you have Panels > Places disabled), every time you Mount a device from there that menu is filled enormously with "Umount <>" items. Really annoying. === Related messages in English: "Error KIO Client" with the text "malformed URL" "An error occurred while accessing 'Home', the system responded: The device is already mounted: Device /dev/sdl1 is already mounted at '/media/myuser/disk title'. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it Status in udisks2 package in Ubuntu: New Bug description: There is a Fix proposed from comment 36 https://bugs.kde.org/show_bug.cgi?id=370975 I have this problem when trying to mount any removable device or internal disk partition, either from Dolphin or from removable device manager in panel. It always shows an error message when you try to mount the device first time, the device is not opened in Dolphin but it is mounted correctly. Then at the second attempt it does not show error message and device is opened in Dolphin. The messages that I get in Spanish: From Dolphin: "Ocurrió un error al acceder a «Carpeta personal», el sistema respondió: El dispositivo ya está montado: Device /dev/sdb3 is already mounted at `/media/yafu/PART 1'." From removable device manager in panel a window message titled "Error Cliente KIO ?" and "Formato de URL erroneo" message. By the way, in a recent Dolphin update, when you mount partitions from the small folder/home icon to the left of the Dolphin address bar (that icon only appears if you have Panels > Places disabled), every time you Mount a device from there that menu is filled enormously with "Umount <>" items. Really annoying. === Related messages in English: "Error KIO Client" with the text "malformed URL" "An error occurred while accessing 'Home', the system responded: The device is already mounted: Device /dev/sdl1 is already mounted at '/media/myuser/disk title'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1762163/+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 1632019] Re: [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display
I forgot to say that this is the message you get if you try to use nvidia-smi from the terminal with iGPU as primary display: $ watch -n 1 nvidia-smi Every 1,0s: nvidia-smi Mon Oct 10 13:24:51 2016 NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system. Please also try adding directory that contains libnvidia-ml.so to your system PATH. ** Description changed: Related links: https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/ https://devtalk.nvidia.com/default/topic/970144/linux/intel-for-display- nvidia-for-cuda-optimus-bug-/ So the problem is that you can not monitor the temperature with nvidia- smi and also can't set the fan speed if iGPU is as a primary display selected from Prime profiles in Nvidia-Settings. In the second link it is mentioned a workaround that might give a clue about the cause of the problem. That is, I think 'nvidia-smi " should work by default without running this workaround as root. To make it clear, nvidia-smi works as expected if you have selected nvidia gpu as the primary display. + Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. - As additional information regarding this PPA Proprietary GPU Drivers (since it is the only way Ubuntu users can update the drivers with .deb packages): + As additional information regarding the Proprietary GPU Drivers PPA (since it is the only way Ubuntu users can update the drivers with .deb packages): https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa If you install the drivers from the PPA (I tested 370.28 and 367.44) and iGPU as the primary display using PRIME, you can not even able to use CUDA in applications such as Blender/Cycles (CUDA is not available in - Blender for GPU compute). This problem does not occur with drivers from - official repositories of Ubuntu, for example 361.42 is working well in - Kubuntu 16.04. So I do not know if it is because PPA packages are built - differently from the official repository. It would be good you to take a - look at this. + Blender for GPU compute). This problem (not having CUDA available) does + not occur with drivers from official repositories of Ubuntu, for example + 361.42 is working well in Kubuntu 16.04. So I do not know if it is + because PPA packages are built differently from the official repository. + It would be good you to take a look at this. Thanks. - System and Hardware specs: i7 3770 - HD 4000 GTX 960 Kubuntu 16.04 64bits $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) $ uname -r 4.4.0-38-generic nvidia 361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1632019 Title: [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Related links: https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/ https://devtalk.nvidia.com/default/topic/970144/linux/intel-for- display-nvidia-for-cuda-optimus-bug-/ So the problem is that you can not monitor the temperature with nvidia-smi and also can't set the fan speed if iGPU is as a primary display selected from Prime profiles in Nvidia-Settings. In the second link it is mentioned a workaround that might give a clue about the cause of the problem. That is, I think 'nvidia-smi " should work by default without running this workaround as root. To make it clear, nvidia-smi works as expected if you have selected nvidia gpu as the primary display. Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. As additional information regarding the Proprietary GPU Drivers PPA (since it is the only way Ubuntu users can update the drivers with .deb packages): https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa If you install the drivers from the PPA (I tested 370.28 and 367.44) and iGPU as the primary display using PRIME, you can not even able to use CUDA in applications such as Blender/Cycles (CUDA is not available in Blender for GPU compute). This problem (not having CUDA available) does not occur with drivers from official repositories of Ubuntu, for example 361.42 is working well in Kubuntu 16.04. So I do not know if it is because PPA packages are built differently from the
[Desktop-packages] [Bug 1632019] [NEW] [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display
Public bug reported: Related links: https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/ https://devtalk.nvidia.com/default/topic/970144/linux/intel-for-display- nvidia-for-cuda-optimus-bug-/ So the problem is that you can not monitor the temperature with nvidia- smi and also can't set the fan speed if iGPU is as a primary display selected from Prime profiles in Nvidia-Settings. In the second link it is mentioned a workaround that might give a clue about the cause of the problem. That is, I think 'nvidia-smi " should work by default without running this workaround as root. To make it clear, nvidia-smi works as expected if you have selected nvidia gpu as the primary display. Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. As additional information regarding the Proprietary GPU Drivers PPA (since it is the only way Ubuntu users can update the drivers with .deb packages): https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa If you install the drivers from the PPA (I tested 370.28 and 367.44) and iGPU as the primary display using PRIME, you can not even able to use CUDA in applications such as Blender/Cycles (CUDA is not available in Blender for GPU compute). This problem (not having CUDA available) does not occur with drivers from official repositories of Ubuntu, for example 361.42 is working well in Kubuntu 16.04. So I do not know if it is because PPA packages are built differently from the official repository. It would be good you to take a look at this. Thanks. System and Hardware specs: i7 3770 - HD 4000 GTX 960 Kubuntu 16.04 64bits $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) $ uname -r 4.4.0-38-generic nvidia 361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1632019 Title: [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Related links: https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/ https://devtalk.nvidia.com/default/topic/970144/linux/intel-for- display-nvidia-for-cuda-optimus-bug-/ So the problem is that you can not monitor the temperature with nvidia-smi and also can't set the fan speed if iGPU is as a primary display selected from Prime profiles in Nvidia-Settings. In the second link it is mentioned a workaround that might give a clue about the cause of the problem. That is, I think 'nvidia-smi " should work by default without running this workaround as root. To make it clear, nvidia-smi works as expected if you have selected nvidia gpu as the primary display. Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. As additional information regarding the Proprietary GPU Drivers PPA (since it is the only way Ubuntu users can update the drivers with .deb packages): https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa If you install the drivers from the PPA (I tested 370.28 and 367.44) and iGPU as the primary display using PRIME, you can not even able to use CUDA in applications such as Blender/Cycles (CUDA is not available in Blender for GPU compute). This problem (not having CUDA available) does not occur with drivers from official repositories of Ubuntu, for example 361.42 is working well in Kubuntu 16.04. So I do not know if it is because PPA packages are built differently from the official repository. It would be good you to take a look at this. Thanks. System and Hardware specs: i7 3770 - HD 4000 GTX 960 Kubuntu 16.04 64bits $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) $ uname -r 4.4.0-38-generic nvidia 361 from official Ubuntu 16.04 repos. Installed libcuda1 and nvidia-prime packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1632019/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
@Are you Ubuntu package maintainer? Why you are assigned to this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf - 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
Sorry, my previous post was for Márcio Jorge PimentaParola -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf - 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
Putting the package in backports is just a workaround. nvidia-modprobe should be automatically installed when you install the nvidia driver. Does it happening currently with new versions of Ubuntu? Otherwise, this is still a big problem for users: http://blenderartists.org/forum/showthread.php?355719-No-Cuda-option @r0ma1ne, you read that thread in latest posts (user have mint 17) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf - 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
I don't know is this is the same problem, but this is happening in Ubuntu 14.10 Utopic beta, nVidia 331.89: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1375841 I hope this will be solved before 14.10 be released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf - 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1375841] Re: [nvidia-331-updates] [14.10 Utopic] CUDA only works as root
I think maybe this report is related with this: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1375841 Title: [nvidia-331-updates] [14.10 Utopic] CUDA only works as root Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Using Kubuntu 14.10 64bits == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 Codename: utopic == $ sudo dpkg -l | grep -i nvidia ii bbswitch-dkms 0.7-2ubuntu1 amd64Interface for toggling the power on nVidia Optimus video cards ii libcuda1-331-updates 331.89-0ubuntu5 amd64NVIDIA CUDA runtime library ii nvidia-331-updates331.89-0ubuntu5 amd64NVIDIA binary driver - version 331.89 ii nvidia-331-updates-uvm331.89-0ubuntu5 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331-updates 331.89-0ubuntu5 amd64NVIDIA OpenCL ICD ii nvidia-prime 0.6.6 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver == $ lsmod | grep nvi nvidia 10728519 40 drm 310919 3 nvidia I am using the Blender 3D 2.71 binary downloaded from the official Blender site. It contain precompiled CUDA Kernel (cuda toolkit is not required to be installed). If I run Blender then CUDA is not available under File User Preferences System Compute Device . If I run as super user Blender (kdesudo ./blender), then CUDA is available. Here's a related thread on nvidia devtalk forum (see message #8): https://devtalk.nvidia.com/default/topic/699610/334-21-driver- returns-999-on-cuinit-cuda-/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1375841/+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 1375841] Re: [nvidia-331-updates] [14.10 Utopic] CUDA only works as root
Well, I installed the nvidia-modprobe package and that seems to solve the problem. $ lsmod | grep nvi nvidia_uvm 34855 0 nvidia 10728519 41 nvidia_uvm drm 310919 3 nvidia Definitely when the nvidia drive is installed then nvidia-modprobe should be automatically installed as a dependency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1375841 Title: [nvidia-331-updates] [14.10 Utopic] CUDA only works as root Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Using Kubuntu 14.10 64bits == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 Codename: utopic == $ sudo dpkg -l | grep -i nvidia ii bbswitch-dkms 0.7-2ubuntu1 amd64Interface for toggling the power on nVidia Optimus video cards ii libcuda1-331-updates 331.89-0ubuntu5 amd64NVIDIA CUDA runtime library ii nvidia-331-updates331.89-0ubuntu5 amd64NVIDIA binary driver - version 331.89 ii nvidia-331-updates-uvm331.89-0ubuntu5 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331-updates 331.89-0ubuntu5 amd64NVIDIA OpenCL ICD ii nvidia-prime 0.6.6 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver == $ lsmod | grep nvi nvidia 10728519 40 drm 310919 3 nvidia I am using the Blender 3D 2.71 binary downloaded from the official Blender site. It contain precompiled CUDA Kernel (cuda toolkit is not required to be installed). If I run Blender then CUDA is not available under File User Preferences System Compute Device . If I run as super user Blender (kdesudo ./blender), then CUDA is available. Here's a related thread on nvidia devtalk forum (see message #8): https://devtalk.nvidia.com/default/topic/699610/334-21-driver- returns-999-on-cuinit-cuda-/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1375841/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
Well, I installed the nvidia-modprobe package and that seems to solve the problem. $ lsmod | grep nvi nvidia_uvm 34855 0 nvidia 10728519 41 nvidia_uvm drm 310919 3 nvidia Definitely when the nvidia drive is installed then nvidia-modprobe should be automatically installed as a dependency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf - 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1375841] [NEW] [nvidia-331-updates] [14.10 Utopic] CUDA only works as root
Public bug reported: Using Kubuntu 14.10 64bits == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 Codename: utopic == $ sudo dpkg -l | grep -i nvidia ii bbswitch-dkms 0.7-2ubuntu1 amd64Interface for toggling the power on nVidia Optimus video cards ii libcuda1-331-updates 331.89-0ubuntu5 amd64NVIDIA CUDA runtime library ii nvidia-331-updates331.89-0ubuntu5 amd64NVIDIA binary driver - version 331.89 ii nvidia-331-updates-uvm331.89-0ubuntu5 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331-updates 331.89-0ubuntu5 amd64NVIDIA OpenCL ICD ii nvidia-prime 0.6.6 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver == $ lsmod | grep nvi nvidia 10728519 40 drm 310919 3 nvidia I am using the Blender 3D 2.71 binary downloaded from the official Blender site. It contain precompiled CUDA Kernel (cuda toolkit is not required to be installed). If I run Blender then CUDA is not available under File User Preferences System Compute Device . If I run as super user Blender (kdesudo ./blender), then CUDA is available. Here's a related thread on nvidia devtalk forum (see message #8): https://devtalk.nvidia.com/default/topic/699610/334-21-driver- returns-999-on-cuinit-cuda-/ ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: 3d blender cuda nvidia ** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/1375841/+attachment/4220380/+files/Xorg.0.log ** Summary changed: - [nvidia-331-updates] CUDA only works as root + [nvidia-331-updates] [14.10 Utopic] CUDA only works as root -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1375841 Title: [nvidia-331-updates] [14.10 Utopic] CUDA only works as root Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Using Kubuntu 14.10 64bits == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 Codename: utopic == $ sudo dpkg -l | grep -i nvidia ii bbswitch-dkms 0.7-2ubuntu1 amd64Interface for toggling the power on nVidia Optimus video cards ii libcuda1-331-updates 331.89-0ubuntu5 amd64NVIDIA CUDA runtime library ii nvidia-331-updates331.89-0ubuntu5 amd64NVIDIA binary driver - version 331.89 ii nvidia-331-updates-uvm331.89-0ubuntu5 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331-updates 331.89-0ubuntu5 amd64NVIDIA OpenCL ICD ii nvidia-prime 0.6.6 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver == $ lsmod | grep nvi nvidia 10728519 40 drm 310919 3 nvidia I am using the Blender 3D 2.71 binary downloaded from the official Blender site. It contain precompiled CUDA Kernel (cuda toolkit is not required to be installed). If I run Blender then CUDA is not available under File User Preferences System Compute Device . If I run as super user Blender (kdesudo ./blender), then CUDA is available. Here's a related thread on nvidia devtalk forum (see message #8): https://devtalk.nvidia.com/default/topic/699610/334-21-driver- returns-999-on-cuinit-cuda-/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1375841/+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 1070877] Re: vfat mounts as showexec
Yes, showexec can not allows change attributes of files and make them executable. I find no sense in Linux that device is mounted with showexec http://www.tomas-m.com/blog/19318-Bootinst-script-improvements.html https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/663815 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1070877 Title: vfat mounts as showexec Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: Kinda surprised to see *.py/*.sh not executable on pen drives... showexec If set, the execute permission bits of the file will be allowed only if the extension part of the name is .EXE, .COM, or .BAT. Not set by default. The good news is that i learned a new (useless) mount option, so today.. I am a better person for that knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1070877/+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 993187] Re: ubuntu 12.04 completely freezes frequently.
I installed the nvidia proprietary drivers and after three days no freezing occurred in Kubuntu. I uninstalled the proprietary drivers and freezes are back. Clearly, my problem is related to the nouveau drivers. In a few posts above I put what I get after freezing in kern.log file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Won't Fix Status in “linux” source package in Precise: Won't Fix Status in “xserver-xorg-video-intel” source package in Precise: Won't Fix Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+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 993187] Re: ubuntu 12.04 completely freezes frequently.
This is disconcerting. In the bug report some people have nVidia cards - ATI and Intel, and all with the same problem. A lot of people affected and apparently Ubuntu responsible have no idea what could be the problem. I'm using Kubuntu 12.04 64bits and I have a nvidia card: 01:00.0 VGA compatible controller: nVidia Corporation GF108 [GeForce GT 430] (rev a1) and I can not detect what is causing the freeze. The final lines of kern.log I get are related always with dri and nouveau after the freeze: == Sep 23 20:45:43 yafupc kernel: [ 5981.225699] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 Sep 23 20:45:58 yafupc kernel: [ 5995.352503] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 Sep 23 20:46:04 yafupc kernel: [ 6001.512805] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 Sep 23 20:46:04 yafupc kernel: [ 6001.512811] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f Sep 23 20:46:50 yafupc kernel: [ 6048.184954] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 Sep 23 20:47:50 yafupc kernel: [ 6108.196017] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 Sep 23 20:47:50 yafupc kernel: [ 6108.196017] [drm] nouveau :01:00.0: PFIFO: unhandled status 0x0080 == Sep 24 17:41:06 yafupc kernel: [24326.885728] [drm] nouveau :01:00.0: fail set_domain Sep 24 17:41:06 yafupc kernel: [24326.885736] [drm] nouveau :01:00.0: validate gart_list Sep 24 17:41:06 yafupc kernel: [24326.885755] [drm] nouveau :01:00.0: validate: -22 Sep 24 17:41:06 yafupc kernel: [24326.888564] [drm] nouveau :01:00.0: PFIFO: read fault at 0x000d7e3000 [PAGE_NOT_PRESENT] from PGRAPH/GPC0/TEX on channel 0x0001799000 == Sep 25 10:59:45 yafupc kernel: [ 7205.739725] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.739736] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.739762] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.856639] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.856651] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.856673] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.87] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.875567] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.875590] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.885346] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.885358] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.885381] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.914156] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.914168] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.914190] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.935033] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.935046] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.935067] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.940093] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.940111] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.940135] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.951218] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.951230] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.951253] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.971454] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.971466] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.971486] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7205.981017] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7205.981030] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7205.981052] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7206.000106] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7206.000118] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7206.000139] [drm] nouveau :01:00.0: validate: -22 Sep 25 10:59:45 yafupc kernel: [ 7206.012955] [drm] nouveau :01:00.0: fail set_domain Sep 25 10:59:45 yafupc kernel: [ 7206.012968] [drm] nouveau :01:00.0: validate gart_list Sep 25 10:59:45 yafupc kernel: [ 7206.012992] [drm] nouveau :01:00.0:
[Desktop-packages] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
Sorry, I meant before drm instead of dri. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Won't Fix Status in “linux” source package in Precise: Won't Fix Status in “xserver-xorg-video-intel” source package in Precise: Won't Fix Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+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 721471] Re: evdev is not compatible to QT-applications when using tablets
@Alexei, This bug is not related to that bug. The problem is related with this bug in Qt: https://bugreports.qt-project.org/browse/QTBUG-25329 There is a simple workaroun that solves the problem by modifying the src/gui/kernel/qapplication_x11.cpp file in qt-everywhere-opensource-src-4.8.1.tar.gz source. I think the package in Kubuntu is libqtcore4 (qt4-x11): http://forum.kde.org/viewtopic.php?f=139t=98347 In the Krita forum, in page 1 and 2 they discuss the workaround. This bug causes that if you use a non-Wacom graphics tablet, the stylus pressure sensitivity not working in Qt programs (Krita, pencil). Would be nice if could be include that workaroun in Kubuntu 12.10 - Quantal Quetzal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/721471 Title: evdev is not compatible to QT-applications when using tablets Status in “xserver-xorg-input-evdev” package in Ubuntu: New Bug description: Binary package hint: xserver-xorg-input-evdev Hello, evdev has the problem that it is not compatible to QT-Applications, I have tested this with a self-programmed software. Tested this in kubuntu 11.04 daily build (2011-02-18). I think QT-Applications like Krita, ... doesn't work, too (based on previous experience) evdev is not compatible to the QTabletEvent from QT, see here: http://doc.qt.nokia.com/4.7/qtabletevent.html See here, too, there is described that it works with WIZARDPEN-driver in ubuntu 9.10 but doesn't work in 10.10: http://ubuntuforums.org/showthread.php?t=1597558 9.10 config works (with WIZARDPEN) with setting device name to stylus in 9.10 with that line: merge key=info.product type=stringstylus/merge in hal-config of wizardpen I'm using the wacom driver for my Genius G-Pen F610 tablet. This work's fine. But there are other tablets have perhaps a need for the evdev driver - I don't know. With kubuntu 11.04 daily-build (2011-02-18) now my tablet works fine in GTK-applications (in (k)ubuntu 10.10 evdev doesn't work fine - see ubuntuforums link (click event when only moveing the stylus)). How long it does until the much tablet drivers: wizardpen, aiptek, evdev and wacom are going into one driver (a.e. the wacom driver)? It clould be that X11 could be replaced by Wayland, that you have heared - I think. I dont't know if this too much of work (making evdev working with QT), if X11 will replaced to Wayland or the much tablet drivers going into one. Best regard and thanks Stefan Koch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/721471/+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 863154] Re: Wacom Bamboo One tablet random coordinate malfunctions
Thanks alexiade for the patch! Thanks grumbel for the PPA! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/863154 Title: Wacom Bamboo One tablet random coordinate malfunctions Status in The GNU Image Manipulation Program (GIMP): New Status in “gimp” package in Ubuntu: Confirmed Bug description: The tablet in overall seems to work correctly, with all pressure- features working. But quite frequently, while drawing, GIMP seems to wrongly read the coordinates of the stylus (as zeros, or negative values?), resulting in frequent, random 'line-peaks' in the direction of the left and upper image edges. With this bug it is hard to even use the tablet, since these problems are very frequent (see the exemplary image attached). The tablet works with no problems in MyPaint. The bug is reproducible in both Unity-2d and Unity-3d. I also notice the CPU usage increasing dramatically during drawing with any brush. Steps to reproduce: 1. Connect the Wacom Bamboo One tablet 2. Open GIMP 3. Start drawing longer strokes with any brush Expected result: The brush stroke as intended by moving the stylus Actual result: The brush stroke as intended with frequent, random line-strokes towards image edges System: Ubuntu 11.10 oneiric (development branch) GIMP version: 2.6.11 (package version: 2.6.11-2ubuntu3) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/863154/+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 863154] Re: Wacom Bamboo One tablet random coordinate malfunctions
@alexiade, I think most of the persons that have referred to mouse in screen mode has been to point out that the problem occurs with any device in screen mode (mouse or any tablet), not only with the Wacom tablet. Regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/863154 Title: Wacom Bamboo One tablet random coordinate malfunctions Status in The GNU Image Manipulation Program (GIMP): Unknown Status in “gimp” package in Ubuntu: Confirmed Bug description: The tablet in overall seems to work correctly, with all pressure- features working. But quite frequently, while drawing, GIMP seems to wrongly read the coordinates of the stylus (as zeros, or negative values?), resulting in frequent, random 'line-peaks' in the direction of the left and upper image edges. With this bug it is hard to even use the tablet, since these problems are very frequent (see the exemplary image attached). The tablet works with no problems in MyPaint. The bug is reproducible in both Unity-2d and Unity-3d. I also notice the CPU usage increasing dramatically during drawing with any brush. Steps to reproduce: 1. Connect the Wacom Bamboo One tablet 2. Open GIMP 3. Start drawing longer strokes with any brush Expected result: The brush stroke as intended by moving the stylus Actual result: The brush stroke as intended with frequent, random line-strokes towards image edges System: Ubuntu 11.10 oneiric (development branch) GIMP version: 2.6.11 (package version: 2.6.11-2ubuntu3) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/863154/+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 863154] Re: Wacom Bamboo One tablet random coordinate malfunctions
Sorry, but I think the importance of this bug is not low. This bug makes GIMP unusable in many cases. Need a quick solution, or at least a workaround. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/863154 Title: Wacom Bamboo One tablet random coordinate malfunctions Status in The GNU Image Manipulation Program (GIMP): Unknown Status in “gimp” package in Ubuntu: Confirmed Bug description: The tablet in overall seems to work correctly, with all pressure- features working. But quite frequently, while drawing, GIMP seems to wrongly read the coordinates of the stylus (as zeros, or negative values?), resulting in frequent, random 'line-peaks' in the direction of the left and upper image edges. With this bug it is hard to even use the tablet, since these problems are very frequent (see the exemplary image attached). The tablet works with no problems in MyPaint. The bug is reproducible in both Unity-2d and Unity-3d. I also notice the CPU usage increasing dramatically during drawing with any brush. Steps to reproduce: 1. Connect the Wacom Bamboo One tablet 2. Open GIMP 3. Start drawing longer strokes with any brush Expected result: The brush stroke as intended by moving the stylus Actual result: The brush stroke as intended with frequent, random line-strokes towards image edges System: Ubuntu 11.10 oneiric (development branch) GIMP version: 2.6.11 (package version: 2.6.11-2ubuntu3) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/863154/+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 863154] Re: Wacom Bamboo One tablet random coordinate malfunctions
The same problem using any device in Screen mode (Mouse or Genius EasyPen i405 Tablet with wizardpen driver). With the mouse in screen mode de problem is more evident. Random lines appear while I'm drawing. Kubuntu 11.10 Oneiric 64bits. Gimp 6.2.11-2ubuntu4 package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/863154 Title: Wacom Bamboo One tablet random coordinate malfunctions Status in The GNU Image Manipulation Program (GIMP): Unknown Status in “gimp” package in Ubuntu: Confirmed Bug description: The tablet in overall seems to work correctly, with all pressure- features working. But quite frequently, while drawing, GIMP seems to wrongly read the coordinates of the stylus (as zeros, or negative values?), resulting in frequent, random 'line-peaks' in the direction of the left and upper image edges. With this bug it is hard to even use the tablet, since these problems are very frequent (see the exemplary image attached). The tablet works with no problems in MyPaint. The bug is reproducible in both Unity-2d and Unity-3d. I also notice the CPU usage increasing dramatically during drawing with any brush. Steps to reproduce: 1. Connect the Wacom Bamboo One tablet 2. Open GIMP 3. Start drawing longer strokes with any brush Expected result: The brush stroke as intended by moving the stylus Actual result: The brush stroke as intended with frequent, random line-strokes towards image edges System: Ubuntu 11.10 oneiric (development branch) GIMP version: 2.6.11 (package version: 2.6.11-2ubuntu3) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/863154/+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
