[Ubuntu-x-swat] [Bug 1910863] Re: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Summary changed: - Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. + Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1910863] Re: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Attachment added: "cpp code that crashes clang-11" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451542/+files/qs_adr-d57687.cpp -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1910863] Re: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Attachment added: "shell script generated by clang" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451541/+files/qs_adr-d57687.sh -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1910863] [NEW] Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
Public bug reported: clang11 provided by ubuntu on 20.10 crashes on some C++ code with the message: sorry, this include generates a translation unit too large for Clang to process. Installing clang-11 from llvm fixes the issue. This issue occur only on 20.10 ** Affects: llvm-toolchain-11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1827235] [NEW] Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS
Public bug reported: Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et reste figé sur les points sous le logo Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 1 17:30:47 2019 DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2019-04-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed May 1 17:26:15 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1827235 Title: Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827235/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1782618] [NEW] package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: trying desperately to install ubuntu on a new Kingston SSD drive... allways a bug bitchin' around :-\ ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None Date: Thu Jul 19 19:37:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] N210 [Geforce 210] PCIe graphics adapter [1462:8094] InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=9f0de313-6b29-4eab-9c70-eba1602a7ede ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1782618 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1782618/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
Well… Switching to another window manager doesn't solve the “any 3D/GLX app would crash” issue… In my case I would have preferred to use the nouveau driver from the beginning, except that for ancient cards like the 6150SE it makes the whole system freeze after only a few minutes… Finally, I was so p*ssed off about this bug and the fact that I have to tune this or that after some security update, that I looked back into this nouveau driver bug for 2 days and finally found a way to use it without patching/installing anything or totally disabling all graphic accelerations. (options nouveau config="PMPEG=0" => works for me/my card) So now that I have returned to The open and happy world and am not concerned with this bug anymore. Goodluck everybody else! :-P -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, after a kernel upgrade the NVIDIA driver was unusable again. This time was because of the DKMS mechanism which, for whatever reason I didn't investigate yet (could it be because of the apt-pinning??), didn't success to build and install the nvidia_304.ko module for the new kernel. If that happens to you, the solution is to run these commands: dpkg-reconfigure nvidia-304 service lightdm restart (no need to reboot) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
Sorry for the typos and long-lines… Can't find a way to edit back my posts… :-/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
In my case I have a GeForce 6150SE so I really need this 304.131 and can't higher version like 340.xx. For people needing to downgrade, this is one (among others) correct way to do so with Ubuntu 16.04: - first create a file named /etc/apt/preferences.d/local-nvidia-quirks with the following content: Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-opencl-icd-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 - then reinstall the working old packages (they are still available in the repository): sudo apt install nvidia-304=304.131-0ubuntu3 nvidia-opencl- icd-304=304.131-0ubuntu3 - finally, reboot your computer (because it also affects the initrd boot image) The previous way only blocks the currently known not working version, without blocking future updates. If you want a way to stay at the known working version without further updates, here is the content you should use for your /etc/apt/preferences.d/local-nvidia-quirks: Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-opencl-icd-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
Since this problem greatly affects usability (no graphic login anymore), may be it's worth (in the users' point of view) creating a “fake version” security-upgrade like "304.132-0ubuntu0.16.04.2+really304.131" to fill the gap while waiting for Nvidia to provide a fix for 304.132, IMHO. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
** Bug watch added: Debian Bug tracker #840342 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 ** Also affects: nvidia-graphics-drivers-legacy-304xx (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
A debdiff between the packages shows the difference is mainly a version upgrade from 304.131 to 304.132. And it seems a lot of people are experiencing problems with version 304.132, cf https://devtalk.nvidia.com/search/more/sitecommentsearch/304.132/ A specific thread retained my attention: https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le- with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request- badvalue-quot-/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, downgrade “solved” the problem for me too. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Philippe, I am not really sure what you want to do with those commands... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Another thing I just noticed : with or without the patch, the only thing that works with two screen is the extended mode. When I try to go from two screen extended to two screen clone mode, both screens switch off and cannot be switched back on. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
In the next comment, you will findthe output of xrandr --verbose, when both monitors are enabled, with the original (non patched) drivers. I must say that the patch you posted in comment #47 works perfectly when it comes to wake the monitor after some time of sleep. Only the problem of black screens when switching from one to two screens enabled remains. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "Xrandr output" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4702793/+files/xrandr -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "20160706_120743.jpg" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696357/+files/20160706_120743.jpg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "black_screen.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696354/+files/black_screen.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "before_black_screen.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696355/+files/before_black_screen.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
I must add that without the patch, after the black screen and the ctrl-alt-F1 then ctrl-alt-F7, I had a dialog box saying : "Impossible de restaurer la configuration de l'affichage could not set the configuration for CRTC 80". -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Same problem with this patch. Well in fact, it's even worse as I got a kernel panic when trying to switch from 2 screens to only one (see picture attached). I attached the output of xrandr before and after the black screen (but before the complete crash). The black screen when changing between one and two monitors also appears without the patch. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Michel, this patch seems to work quite well, but still showing some strange behaviour. To sum up, with the new patch : - with one or two screens used, when the screens goes off after some time of inactivity, they can be woken up by moving the mouse. - when two screens are used, from time to time, the screen connected via the VGA port of the graphics card does not goes off. (Its light dims, the screen goes black and then shows the login page again, the dvi-connected screen staying off until I move the mouse). With only one screen used (the dvi one), this behaviour does not appear until now. - Using the ubuntu screen selector, from time to time, when I change from two screens to one screen, the screen goes black only showing the mouse arrow. I have to go to tty1 then press ctrl alt f7 to see the normal screen again. Once, doing this, even the keyboard and the mouse stopped responding. - During the make process of the driver (with the patch), I still get the same warning : radeon_drm_queue.c: In function ‘radeon_drm_queue_alloc’: radeon_drm_queue.c:95:9: warning: return makes integer from pointer without a cast [-Wint-conversion] return NULL; -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
It's a DELL Dimension E520. Is that the full computer model ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695158/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695162/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695157/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695155/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695153/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695159/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695152/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695160/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695147/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695146/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
apport information ** Tags added: apport-collected compiz-0.9 ubuntu ** Description changed: I did a fresh install of ubuntu 16.04 on my old dell computer in which there is an ati radeon X1300 graphics card. Whenever the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. When I kill the Xorg process via ssh with another computer, the screen then comes to life again and I can log back in. When I remove the graphic card from the computer and use the built in graphic card instead, the bug doesn't occur. So I guess it is related to the radeon driver. - Oddly enough, there is no problem waking the screen when I type "xset - -display :0.0 dpms force off" in a terminal. Moreover typing gnome- - screensaver-command -a in a terminal turns my screen off and after - typing this line, the screen can be woken up by moving the mouse or by - hitting a key. I'm confused. + Oddly enough, there is no problem waking the screen when I type "xset -display :0.0 dpms force off" in a terminal. Moreover typing gnome-screensaver-command -a in a terminal turns my screen off and after typing this line, the screen can be woken up by moving the mouse or by hitting a key. I'm confused. + --- + .tmp.unity_support_test.0: + + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: compiz + CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' + CompositorUnredirectFSW: true + CurrentDesktop: Unity + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + DkmsStatus: + virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed + virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed + ExtraDebuggingInterest: No + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7183] (prog-if 00 [VGA controller]) +Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302] +Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303] + InstallationDate: Installed on 2016-04-23 (71 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + MachineType: Dell Inc. Dell DM061 + Package: xorg 1:7.7+13ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 + Tags: xenial ubuntu compiz-0.9 + Uname: Linux 4.4.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/24/2007 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.4.0 + dmi.board.name: 0WG864 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 6 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr: + dmi.product.name: Dell DM061 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 + version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695143/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695148/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] drirc.txt
apport information ** Attachment added: "drirc.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695161/+files/drirc.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695145/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695156/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695150/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695144/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695151/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695149/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1577170/+attachment/4695154/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Summary changed: - [solved] screen cannot be turned back on after being switched off after some time of inactivity + screen cannot be turned back on after being switched off after some time of inactivity -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "gdb output with "new" patch and 1 screen on" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4676222/+files/gdb_new_patch_1_screen.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "gdb output with "old" patch and 2 screens on" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4676221/+files/gdb_old_patch_2_screens.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
I just attached the two gdb backtraces from when it hangs. I must add that during the "make" process of the newly patched radeon driver, I get this warning : radeon_drm_queue.c: In function ‘radeon_drm_queue_alloc’: radeon_drm_queue.c:95:9: warning: return makes integer from pointer without a cast [-Wint-conversion] return NULL; Maybe that explains why the monitor never wakes up after being turned off with the newly patched driver ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
What I have noticed is that when two screens are plugged in the graphic card, and the desktop appears on both screen, and when I then choose to only use the dvi-connected screen via the "display" menu in ubuntu, the vga-connected screen goes off, and the dvi-connected screen only show the mouse on a black screen. To see the desktop again, I have to switch to tty1 (ctrl alt F1) and then ctrl alt F7. I don't know if this could be related to the problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
Thank you Michel for this new fix. Unfortunately, this one does not work on my computer at all. With the previous patch, the problem seemed to have been fixed, but wasn't completely fixed as my computer couldn't be woken up when two screens were used on my radeon card (it works so far with only one screen connected). With the newest patch, even when only one screen is connected to the graphics card, the computer cannot be woken up anymore after the screen goes to sleep. Are those patches so different ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity
Strange, as with the patched driver, the problem reappeared today. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Thanks to the guys in the #radeon channel on irc, I found a way to solve the problem. You have to apply this patch to the source of the video driver (xfree86-video-ati-7.7.0) : https://paste.debian.net/plain/682956 and compile then install it (using --prefix=/usr for the configure process). ** Summary changed: - screen cannot be turned back on after being switched off after some time of inactivity + [solved] screen cannot be turned back on after being switched off after some time of inactivity -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: [solved] screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Description changed: I did a fresh install of ubuntu 16.04 on my old dell computer in which there is an ati radeon X1300 graphics card. Whenever the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. - The same ubuntu 16.04 installed on a laptop with intel graphics card - doesn't show this problem, so I first guessed it was related to the - radeon driver. But as there is no problem waking the screen when I type - "xset -display :0.0 dpms force off" in a terminal, it looks like the - radeon driver is not the culprit. + When I kill the Xorg process via ssh with another computer, the screen + then comes to life again and I can log back in. - Oddly enough, invoking : - gnome-screensaver-command -a - in a terminal turns my screen off and after typing this line, the screen can be woken up by moving the mouse or by hitting a key. I'm confused. It seems not related to gnome-screensaver, but rather to the way ubuntu turns the screen off. + When I remove the graphic card from the computer and use the built in + graphic card instead, the bug doesn't occur. So I guess it is related to + the radeon driver. + + Oddly enough, there is no problem waking the screen when I type "xset + -display :0.0 dpms force off" in a terminal. Moreover typing gnome- + screensaver-command -a in a terminal turns my screen off and after + typing this line, the screen can be woken up by moving the mouse or by + hitting a key. I'm confused. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Package changed: unity (Ubuntu) => xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
EDIT : I just found that letting the screen be turned off when not logged at all (when I boot the computer and don't log in for example) causes no problem. The screen goes black and can be woken up by moving the mouse or by hitting a key. The problem only appear when logged in, whatever the user. ** No longer affects: xserver-xorg-video-ati (Ubuntu) ** No longer affects: gnome-screensaver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Also affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
New information : typing "xset -display :0.0 dpms force off" in the terminal makes my screen to turn off. Then I can wake it up just by moving the mouse. So the problem seems related to the "screen saver" of ubuntu rather than Xorg. ** Package changed: xorg (Ubuntu) => gnome-screensaver (Ubuntu) ** Description changed: I did a fresh install off ubuntu 16.04 on my old dell computer in which there is an ati radeon X1300 graphics card. - Whenever the screen goes off due to inactivity, it cannot be woken up + Whenever the screen goes off due to inactivity, it cannot be woken up by moving the mouse or hit a key. The same ubuntu 16.04 installed on a laptop with intel graphics card - doesn't show this problem, so I guess it is related to the radeon - driver. + doesn't show this problem, so I first guessed it was related to the + radeon driver. But as there is no problem waking the screen when I type + "xset -display :0.0 dpms force off" in a terminal, I think the problem + is rather related to gnome-screensaver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+attachment/4654716/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+attachment/4654715/+files/dmesg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
The problem is not solved with the latest 4.6 kernel. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Is it something I could do to find out a fix ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 573748] Re: [MASTER] fglrx does not build on 2.6.33 kernel and higher
Hello, i was able to install, but unable to run the apk on android 4.2.2 C.O. Le 17/06/2015 13:14, Rolf Leggewie a écrit : lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as Won't Fix. ** Changed in: fglrx-installer (Ubuntu Lucid) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/573748 Title: [MASTER] fglrx does not build on 2.6.33 kernel and higher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/573748/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1388530] Re: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M
Hey, I have just found a workaround by chance: purging xserver-xorg-video- nouveau (without replacing it by a Nvidia driver) from the system removes the freezing issue during shutdown! That's very strange because the driver is loaded with initrd during the boot, meaning rebooting after the removal does not prevent X Server from using the nouveau driver... without the shutdown issue that was directly caused by the same driver. Maybe someone can shed light on this mystery. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1388530 Title: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1388530/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1388530] Re: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M
A trace has recently shown up during a failed shutdown; the following is the OCR translation obtained from a picture (available as attachment), meaning some decoding errors may be still there, especially in the Modules linked in section that I have not checked: wait-for-state stop/waiting * Stopping rsync daemon rsync * speech-dispatcher disabled; edit /etc/default/speech-dispatcher * Stopping uuidd generator uuidd * Asking all remaining processes to terminate... * Killing all remaining processes... ModemManager(1044]: warn Could not acquire the 'org.freedesktop.ModemManageris service name modemManager(1044]: info ModemManager is shut down Deactivating swap... [ 3944.666185] BUG: unable to handle kernel NULL pointer dereference at (null) [ 3944.666206] IP: [ (null)] (null) [ 3944.666219] PGD 0 [ 3944.666225] Oops: 0010 [#1] SMP [ 3944.666234] Modules linked in: ctr ccm rfComm bnep nls_iso88591 snd_hda_codec_realtek snd-hda-codec-geheric snd-hda-codec-hdmi IP6t-REJECT xt_hl iP6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT arc4 xt_t_OG xt_limit xt_tcpudp x We nf-conntracK-IPv4 nf_defrag_ipv4 xt_conntrack intel_rapi rt18723ae ip6table_filter ip6_tables rt18723_common x86_0(g_temp_thermal rti_pci intei_powerclamp uvcvideo nf_conntrack_netbios_ns rt lwif i coretemp nf_conntrack_broadcast nf_nat_ftp mace snd_hda_intel kvm_intel snd_hda_controller nf_nat videobuf2_vmalloc snd_hda_codec Kvm snd_hwdep nf_conntrack_ftp videobuf2_memops videobuf2_core nf_conntrack snd_pcm v412_common 1915 videodev iptable_filter media es snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi crctlOdif_pcIml snd_seq x_tables crc32_pclmul btusb ghash_clmuli_intel ttm aesni_intel snd_seq_device drm_kms_helper bluetooth aes_x86_64 snd_timer irw drm snd gf128mui rtsx lue_helper soundcore memstick 6lowpan_lphc ablk_helper jdydev i2c_algd_bit cryptd mei_me IPc_ich mei shpchp serio_raw parport_pc ppdev msi_wmi sparse_keymap mxm_wmi 1p wmi soc_button_array parport mac hid video hid_generic usbhid b_storage rtsx_pci_sdmac ahci psmouse alx libahci rtsx_pci mdio [ 3944.666555] CPU: 5 PID: 1584 Comm: Xorg Tainted: S I 3.16.0-24-generic #32-Ubuntu [ 3944.666574] Hardware name: Micro-Star International Co., Ltd. GE 30 6.0-24 BIOS El6GCIMS.511 08/27/2013 [ 3944.666596] task! 880437739e90 ti: 880427824000 task.ti: 880427824000 [ 3944.12] RIP: 0010:[] [ (null)] (null) 1 3944.28] RSP: 0018:880427827b60 EFLAGS: 00010246 ( 3944.40] RAX: c0acd040 RBX: 880438c47800 RCX: e0:11) ( 3944.55] RDX: c0abfaa7 RSI: RDI: 880438c47800 [ 3944.70] RBP: 880427827b80 R08: 000O R09: c0abf9a8 [ 3944.86] R10: c0a2cb58 R11: 880438c47a00 R12: 0001 [ 3944.666701] R13: R14: 880435282d30 R15: 8804360d3088 [ 3944.666716] FS: 7f4c73ad99c0() GSOfff88044fb4() knIGS: [ 3944.666733] CS: 0010 DS: ES: CR0: 80050033 [ 394406667451 CR2: CR3: 02c13000 CR4: 001407e0 [ 3944.6667601 Stack: [ 3944.666765] 209e7065 880435282d20 880435282d48 [ 3944.666783] 880427827bd0 c09ed98a 880427827bc0 c0abf9a8 [ 3944.666802] 880438c47800 c0abf810 [ 3944.666820] Call Trace: [ 3944.666838] kc09ef065] ? nouveau_object_dec+0x125/0x2a0 [nouveau] [ 3944.666858] [afffc09ed98a] nouveau_handle_fini+Oxlfa/Ox2a0 [nouveau] [ 3944.666878] [Offfc09ecld3] nouveau_client_fini+Ox53/0x80 [nouveau] [ 3944.666907] [afffc0a6e16f] nouveau_cli_destroy+Ox2f/Ox50 [nouveau] [ 3944.666934] [c0a6e25b] nouveau_drm_postclose+Ox1b/Ox50 [nouveau] [ 3944.666956] [dfffc03fdce4] drm_release+Ox334/0x640 [dm] [ 3944.666970] Wfff821e26b4] __fput+Oxe4/0x240 [ 3944.666981] [afff821e285e] f_put+Oxe/Ox10 [ 3944.666994] l820919c0] task_work_run+Oxd4/Oxf0 [ 3944.6670071 (afff820725c7] do_exit+Ox377/0xab0 [ 3944.667023] kc09eef27] ? nouveau_object_del+0x97/OxbO [nouveau] [ 3944.667039] [82072d83] do_group_exit+Ox43/0xc0 [ 3944.667052] Wfff8208312.b] get_signal_to_deliver+Ox29f/Ox8d0 ( 3944.667067] U82012588] do_signal+0x48/OxbOO ( 3944.6670911 kc0a6e0da] ? nouveau_drm_ioct1+0x8a/Oxa0 [nouveau] [ 3944.667106] (Offf8204bc8] ? do_vfs_ioctl+0x2c8/0x4a0 [ 3944.667120] k820130c9] do_notiy_resume+Ox69/OxbO ( 3944.667133] [afff82787faw] int_signal+0x12/0x17 ( 3944.667144] Code: Bad RIP value. ( 3944.667154] RIP ( (null)] (null) ( 3944.667166] RSP 880427827b60 ( 3944.667174] CR2: Nouveau is clearly involved in the bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1388530 Title: 14.10 freezes during shutdown on
[Ubuntu-x-swat] [Bug 1388530] [NEW] 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M
Public bug reported: I know someone who solved this issue by installing a Nvidia driver. Do you test your Nouveau driver on MSI computers and computers with Nvidia graphics card before rolling out new releases? This is not the first time I'm experiencing a significant flaw with this driver. More information about the issue can be found here: http://ubuntuforums.org/showthread.php?t=2250017 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1388530 Title: 14.10 freezes during shutdown on MSI GE60 with Nvidia Geforce GTX 765M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1388530/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 802589] Re: KEY_CYCLEWINDOWS invalidly mapped to XF86RotateWindows
This is fixed upstream: http://cgit.freedesktop.org/xkeyboard- config/commit/?id=ec875f6f9b7c4028e11d32b071989c682e6502bd -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/802589 Title: KEY_CYCLEWINDOWS invalidly mapped to XF86RotateWindows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/802589/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1235280] [NEW] [i965gm] GPU lockup IPEHR: 0x78080003 while running glmark2
Public bug reported: I was running glmark2 when my screen turned black. Matching syslog lines: [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3f5 ctx 0) at 0x3f515fc [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2 [drm:i915_reset] *ERROR* Failed to reset chip. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Chipset: i965gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 4 16:13:34 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: tp-smapi, 0.41, 3.11.0-11-generic, x86_64: installed DuplicateSignature: [i965gm] GPU lockup IPEHR: 0x78080003 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5] InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 7667WHE MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=ad756e46-16b6-4730-9033-6a4b5ebc963b ro elevator=noop quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.99.903-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [i965gm] GPU lockup IPEHR: 0x78080003 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 7667WHE dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn7667WHE:pvrThinkPadX61s:rvnLENOVO:rn7667WHE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7667WHE dmi.product.version: ThinkPad X61s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Oct 4 16:15:25 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16384 vendor LEN xserver.version: 2:1.14.3-3ubuntu1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze saucy ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1235280 Title: [i965gm] GPU lockup IPEHR: 0x78080003 while running glmark2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1235280/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1235280] Re: [i965gm] GPU lockup IPEHR: 0x78080003 while running glmark2
Here's the glmark output from a second run. (...) [ideas] speed=duration:intel_do_flush_locked failed: Input/output error ** Attachment added: glmark.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1235280/+attachment/3859537/+files/glmark.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1235280 Title: [i965gm] GPU lockup IPEHR: 0x78080003 while running glmark2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1235280/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1075158] Re: Resume from suspend leave black screen
It is working now so it can be closed ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1075158 Title: Resume from suspend leave black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1075158/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1012019] Re: Wacom tablet does not work on first startup
This bug affects me as well. When starting my computer with the tablet plugged in, the led on the tablet doesn't light up, lsusb doesn't list it, and lsmod doesn't list the wacom module. The tablet just does not react. A workaround is to unplug it and plug it again: the tablet gets recognised and then works correctly, is listed under lsusb, and under lsmod the wacom module appears on top of the list. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1012019 Title: Wacom tablet does not work on first startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1012019/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1075158] [NEW] Resume from suspend leave black screen
Public bug reported: It seems that bug #966744 has been fixed but I have still the issue I have a Laptop Fujitsu s761 Kubuntu 12.10 64 bit I am using a i915 card from intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/1075158/+attachment/3424631/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1075158 Title: Resume from suspend leave black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1075158/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1023414] Re: /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined reference to `_XGetRequest' collect2: ld a retourné 1 code d'état d'exécution
** Package changed: ubuntu = libx11 (Ubuntu) ** Changed in: libx11 (Ubuntu) Assignee: (unassigned) = Christophe (kriss-tofephon) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1023414 Title: /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined reference to `_XGetRequest' collect2: ld a retourné 1 code d'état d'exécution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1023414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
Ter Info I just found the problem by me. Crashes occured due to I/0 dropout on asus MB P6X58-E WS. This happened about one time each hour. Pc worked fine during 9 months and sudden it's start freezing. It was not a real freeze. As I still had graphical screen and every program and service loaded into ram continued working until they required hd acces. I'm working with crucial m4 512 gb ssd's. Problem is solved by ugrading crucial m4 firmware to version f At least now pc worked already 3 hours whitout any drop out of sata busses. If persons who are working with ssd drives like me first try to upgrade the firmware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
Since a week now after latest upgrade ubuntu 12.04 also always crashes after a certain amount of time. system asus mb P6X58-E WS,Intel core i7 990x, corsair vengeance 3 x 4GB ddr3 1600mhz. drives 2 sdd corsair crucial 512 GB 2 WD 2002FAEX 2TB. Crash seems to be related with sata. When running win 7 No crash OCCurs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
This problem seems to occur one many modern system's. it's not graphical related. But eigther I/0 related. I think that a change somewhere into D-bus must be the cause All graphic drivers are making a lot of use of hdd and so .. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 64bit completely freezes frequently
I have the same problem. I use a freshly installed Ubuntu 12.04, and when I log under unity (3d) the GUI freezes after some time randomly. It can be when I surf the web with firefox or when I read a pdf file in evince. The mouse still moves on the screen, but nothing happens when I click somewhere. The system goes on working, for example, the music in rythmbox does not hang. I think the problem is due to compiz, as no problem occurs when I log under unity2d. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 64bit completely freezes frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 987498] Re: Unity/compiz freeze but mouse still move
I have the same problem. I use a freshly installed Ubuntu 12.04 64 bits, and when I log under unity (3d) the GUI freezes after some time randomly. It can be when I surf the web with firefox or when I read a pdf file in evince. The mouse still moves on the screen, but nothing happens when I click somewhere. The system goes on working, for example, the music in rythmbox does not stop. All I can do is to Ctrl-Alt-F1 and get a console. I think the problem is due to compiz, as no problem occurs when I log under unity2d. My config: Dell E520, graphics : Radeon X1300 with the radeon free driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/987498 Title: Unity/compiz freeze but mouse still move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/987498/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 64bit completely freezes frequently
I think this could help. The bug just appeared again as I was within a gnome classic (WITH effects) session with my ubuntu 12.04 64 bits. So it looks like it's really a issue of compiz and not really a bug in unity. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 64bit completely freezes frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 987498] Re: Unity/compiz freeze but mouse still move
I think this could help. The bug just appeared again as I was within a gnome classic (WITH effects) with my ubuntu 12.04 64 bits. So it looks like it's really a issue of compiz and not really a bug in unity. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/987498 Title: Unity/compiz freeze but mouse still move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/987498/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 813343] Re: nvidia drivers, second monitor covered by black
Hi Axel, This is not completely true. In Natty, it was possible to activate twinview on 2 external monitors if DFP-0 is disabled. This was done via nvidia-settings. However now, the nvidia-settings seems to crash when the same setup is applied. Like Radu, I also experience this problem. I have a Dell Latitude E6420 with NVS 4200M. I now switched back to Natty until this problem is solved :/ PS: I had the same problem when only connecting 1 external monitor, so twinview on DFP-0 and DFP-1. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/813343 Title: nvidia drivers, second monitor covered by black To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/813343/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 808478] Re: Input detection fails in oneiric
Small focus on what I see as suspect in X11.logs files: Wladimir Mutel log: [ 393.193] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. mine: [12.757] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [12.757] (WW) Disabling Keyboard0 [12.757] (WW) Disabling Mouse0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/808478 Title: Input detection fails in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/808478/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 808478] [NEW] Input detection fails in oneiric
Public bug reported: All inputs plugged at booting are not detected by xorg (need magic keys alt+impr_ecr+r to release keyboard and go tty) note: I use nvidia pilots and it makes an autoconfig. here the logs... I have no usb keyboard at home, this bug turn my laptop nearly unusable. (still tty and mouse only guest session but no way to open visual keyboard from acessibility options in lightdm) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/808478 Title: Input detection fails in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/808478/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 808478] Re: Input detection fails in oneiric
** Attachment added: Xorg log file https://bugs.launchpad.net/bugs/808478/+attachment/2201253/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/808478 Title: Input detection fails in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/808478/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 799085] Re: Xorg freeze
I have downgraded the compiz packages and I haven't had a freeze since then. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/799085 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/799085/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 799085] [NEW] Xorg freeze
Public bug reported: Binary package hint: xorg after an upgrade on 2011-06-12(compiz) xorg started to freeze after some time of usage. The freeze are not always fatal, sometimes going to the console and going back allows to continue working However this works only once. typically what happens is that there is a one flicker of the screen and then it is frozen. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.41.06 Mon Apr 18 14:53:56 PDT 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) Architecture: amd64 Date: Sat Jun 18 10:29:26 2011 DistUpgraded: Log time: 2011-04-09 09:20:36.635495 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: nvidia-current, 270.41.06, 2.6.38-10-generic, x86_64: installed nvidia-current, 270.41.06, 2.6.38-9-generic, x86_64: installed nvidia-current, 270.41.06, 2.6.38-8-generic, x86_64: installed blcr, 0.8.2: added GraphicsCard: nVidia Corporation G84M [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61p [17aa:20d9] InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, Not in use) MachineType: LENOVO 64577WG ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=96c60249-7d4f-4ac6-b98b-42790e0aa109 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UdevDb: Error: [Errno 2] No such file or directory UpgradeStatus: Upgraded to natty on 2011-04-09 (69 days ago) dmi.bios.date: 10/18/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LET56WW (1.26 ) dmi.board.name: 64577WG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LET56WW(1.26):bd10/18/2007:svnLENOVO:pn64577WG:pvrThinkPadT61p:rvnLENOVO:rn64577WG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 64577WG dmi.product.version: ThinkPad T61p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty1 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze natty regression-update running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/799085 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/799085/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 799085] Re: Xorg freeze
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/799085 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/799085/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 753144] Re: focused, or maximized windows blank
On the ubuntu french forum, the nvidia driver 173 solve the problem of some personnes, but not all of them. The white blank windows desepear for all of them, but new bugs appear for some, as a nearly completely black screen (with a little normal zone at the top of the screen). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/753144 Title: focused, or maximized windows blank ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 663846] Re: kde freeze when 3d desktop is active or not active
Similar issue here. Often, applications freeze and I have to kill them (qtcreator for example). Sometimes, it is even worse and the whole system freezes and I need to reboot. After a system freeze, I tried to use CTRL+ALT+Fx then check dmesg and Xorg log but there was nothing strange in those. I'm not sure where else to check if this happens again. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/663846 Title: kde freeze when 3d desktop is active or not active ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 720763] [NEW] package fglrx 2:8.723.1-0ubuntu5 failed to upgrade to 1010: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2
Public bug reported: failed during upgrade to 1010... upgrade interrupted! ProblemType: Package DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.723.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Thu Feb 17 15:38:40 2011 ErrorMessage: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2 MachineType: Dell Inc. Studio XPS 1640 ProcCmdLine: root=UUID=95824ad6-c196-4627-803a-8bc7e3bd22d3 ro quiet splash SourcePackage: fglrx-installer Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2 dmi.bios.date: 12/12/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/12/2008:svnDellInc.:pnStudioXPS1640:pvrA053:rvnDellInc.:rn0U785D:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Studio XPS 1640 dmi.product.version: A053 dmi.sys.vendor: Dell Inc. glxinfo: Error: couldn't find RGB GLX visual or fbconfig name of display: :0.0 system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-28-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/720763 Title: package fglrx 2:8.723.1-0ubuntu5 failed to upgrade to 1010: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 720763] Re: package fglrx 2:8.723.1-0ubuntu5 failed to upgrade to 1010: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/720763 Title: package fglrx 2:8.723.1-0ubuntu5 failed to upgrade to 1010: ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 2 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 644740] Re: [GM45] GPU Hang when enabling KDE desktop effects
Same here, I confirm that the GPU hang can also happen with desktop effects disabled (although way less often). -- [GM45] GPU Hang when enabling KDE desktop effects https://bugs.launchpad.net/bugs/644740 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 644740] Re: [GM45] GPU Hang when enabling KDE desktop effects
Here is the debug output you requested. ** Attachment added: debug output https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/644740/+attachment/1669561/+files/i915_debug.log.gz -- [GM45] GPU Hang when enabling KDE desktop effects https://bugs.launchpad.net/bugs/644740 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 641091] Re: erratic mouse behaviour after resume
Note that I have the exact same issue on a E4310. This is not specific to E6410. Also, it was working fine a few days ago and was broken by a recent package update in Maverick (I don't know which one exactly). -- erratic mouse behaviour after resume https://bugs.launchpad.net/bugs/641091 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-mouse in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 641091] Re: erratic mouse behaviour after resume
This is a kernel issue. The last kernel to work is: 2.6.35-20-generic The breakage was introduced in v2.6.35-21-generic. I hope this helps. ** Package changed: xserver-xorg-input-mouse (Ubuntu) = linux (Ubuntu) -- erratic mouse behaviour after resume https://bugs.launchpad.net/bugs/641091 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-mouse in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580985] Re: DPI of monitor incorrectly set
Architecture: amd64 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes MachineType: LENOVO 9461DXG Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=76a2ac5d-a68d-4595-8a11-e60177aff67e ro quiet splash ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Tags: lucid lucid Uname: Linux 2.6.32-23-generic x86_64 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video XorgConf: dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461DXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461DXG:pvrThinkPadR60:rvnLENOVO:rn9461DXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461DXG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-23-generic ** Tags added: apport-collected -- DPI of monitor incorrectly set https://bugs.launchpad.net/bugs/580985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580985] Dependencies.txt
apport information ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51563989/Dependencies.txt -- DPI of monitor incorrectly set https://bugs.launchpad.net/bugs/580985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580985] DkmsStatus.txt
apport information ** Attachment added: DkmsStatus.txt http://launchpadlibrarian.net/51563990/DkmsStatus.txt -- DPI of monitor incorrectly set https://bugs.launchpad.net/bugs/580985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580985] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/51563987/BootDmesg.txt -- DPI of monitor incorrectly set https://bugs.launchpad.net/bugs/580985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580985] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/51563988/CurrentDmesg.txt -- DPI of monitor incorrectly set https://bugs.launchpad.net/bugs/580985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
