[Desktop-packages] [Bug 367808] Re: mouse acceleration values smaller than "1" have no effect in Jaunty
This issue is still present in Ubuntu 12.04.4 at least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/367808 Title: mouse acceleration values smaller than "1" have no effect in Jaunty Status in “x11-xserver-utils” package in Ubuntu: Expired Bug description: e.g. "xset m 1/8 1" or "xset m 1/25 1" should make mouse cursor movement on the screen very slow, but instead mouse cursor acts similar if not exactly same as "xset m 1 1" the bug does not seem to be hardware specific, Ubuntu 9.04 Jaunty Jackalope --- Architecture: i386 CurrentDmesg: [ 14.077953] ppdev: user-space parallel port driver [ 14.120320] [drm] nouveau :01:00.0: Allocating FIFO number 1 [ 14.121307] [drm] nouveau :01:00.0: nouveau_channel_alloc: initialised FIFO 1 [ 22.808018] eth0: no IPv6 routers present [ 51.083535] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory GdmLog: Error: command ['cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427) Package: x11-xserver-utils 7.5+1ubuntu2 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=2f203cee-2fb9-435c-92c1-0dad373bb789 ro quiet splash ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: dmi.bios.date: 09/15/2005 dmi.bios.vendor: Insyde Software Corporation dmi.bios.version: R1.02 dmi.board.vendor: MTC dmi.board.version: A0 dmi.chassis.asset.tag: 12345678 dmi.chassis.type: 10 dmi.chassis.vendor: MTC dmi.chassis.version: A0 dmi.modalias: dmi:bvnInsydeSoftwareCorporation:bvrR1.02:bd09/15/2005:svnMTC:pn:pvrA0:rvnMTC:rn:rvrA0:cvnMTC:ct10:cvrA0: dmi.product.version: A0 dmi.sys.vendor: MTC glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/367808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 958279] Re: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep.
Refering my last post above; Using xscreensaver (without using 'Display Power Management') works fine for me, so if you encounter issues with the xorg screensaver freezing, disabling the 'xset' screensaving features and installing/using xscreensaver instead might be a workaround for you as well: Install package 'xscreensaver'. Add these two lines to "~/.xinitrc" (or whatever gnome/unity/xfce/kde startup script you have): xset -dpms & xset s off & Set this option in "/etc/X11/xorg.conf": Option "DPMS" "false" Configure xscreensaver with cmd 'xscreensaver-demo' and set it to use "Mode: Blank Screen Only" and do NOT enable any "Display Power Management". If you sometimes want to manually start the screen saver, use cmd "xscreensaver-command -activate'. /Mikael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/958279 Title: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep. Status in AMD fglrx video driver: Confirmed Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I have filed a bug report in AMD's bugzilla about this. I would also like to file one here to track that one. --- For quite a while now, I've just turned DPMS off to keep anything from putting the monitor to sleep to work around this problem. When DPMS support is on (which is the default setting), and something attempts to put the display to sleep (in this case, KDE's desktop power management daemon, but I've had this problem with XFCE and GNOME, and under Ubuntu's Unity desktop as well), the monitor cannot come back on when the user returns and moves the mouse or presses a button on the keyboard. The rest of the system is apparently still functional as I've left music playing before, and then when I've returned, the display is asleep and not responding to my attempts to wake it up, but the music is still playing. Steps to reproduce: 1. I am assuming that for the purposes of reproducing this bug that the following is true, even though I've seen it on various distributions and several versions of Catalyst. You are using Ubuntu 11.10 or 12.04 development branch. You are using Catalyst 12.2 with FGLRX 8.95. You are using a RadeonHD 5670. You are using the Unity or KDE desktop environment. (Either one should provoke this problem.) 2. Wait for the display to be turned off/go into sleep mode. NOT dimmed! If you catch it while it is dimmed, but before it is turned off, you will end up back at your desktop. 3. After the display is off/asleep, attempt to move your mouse or press a button on the keyboard. Observe that the system is NOT responding and the monitor is stuck in sleep mode. Actual result: The display fails to resume, anything you left open is trashed, game over man, game over! :) Expected result: The display mode should be resumed properly in the state that it was previously in. The open source radeon driver always manages to do this right. Workaround: Generate a xorg.conf file with this command: sudo amdconfig --initial Open the xorg.conf file: sudo nano /etc/X11/xorg.conf Find this line: (under Section "Monitor") Option "DPMS" "true" change it to read Option "DPMS" "false" Restart the X server. Observe that your desktop is no longer able to put the display to sleep and that AMD's proprietary display driver is contributing to increased global warming and a higher electric bill. (But doesn't screw up the X server and cause all of user's open files to be lost) To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/958279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 958279] Re: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep.
I have this issue as well. Ubuntu 12.04, 3.2.0-53-generic-pae kernel Catalyst Driver Packaging Version 8.96 AMD Radeon HD 7660D (A10 5700 APU) I put this APU in two new builds, totally identical except that one has ASRock FM2A85 and the other ASRock FM2A75. Only the build with the ...A85 mobo is affected. Using 'xset dpms force off' to activate energy star power saving funtions, or 'xset s activate' to blank screen will sooner or later (often sooner) leave me with a running computer where i can not return from the blank screen (and it is not just that I can not see the screen, the keyboard is not responding, i have tried to safely shutdown using keybindings, but it does not work). Does not fix the issue: 'aticonfig --acpi-services=off' Setting this option in xorg.conf does not fix the issue: "Option "DPMS" "false" All these things in combination does prevent the issue: Put in my login script: 'xset -dpms &' 'xset s off &' Put in xorg.conf: "Option "DPMS" "false" But it does not fix the issue, because I only avoid screen freeze because I never enable the screen blanking/saving functions. Right now I am using 'feh -FNY ~/.black.png' as a simple screen-blanking function instead. Regards Mikael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/958279 Title: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep. Status in AMD fglrx video driver: Confirmed Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I have filed a bug report in AMD's bugzilla about this. I would also like to file one here to track that one. --- For quite a while now, I've just turned DPMS off to keep anything from putting the monitor to sleep to work around this problem. When DPMS support is on (which is the default setting), and something attempts to put the display to sleep (in this case, KDE's desktop power management daemon, but I've had this problem with XFCE and GNOME, and under Ubuntu's Unity desktop as well), the monitor cannot come back on when the user returns and moves the mouse or presses a button on the keyboard. The rest of the system is apparently still functional as I've left music playing before, and then when I've returned, the display is asleep and not responding to my attempts to wake it up, but the music is still playing. Steps to reproduce: 1. I am assuming that for the purposes of reproducing this bug that the following is true, even though I've seen it on various distributions and several versions of Catalyst. You are using Ubuntu 11.10 or 12.04 development branch. You are using Catalyst 12.2 with FGLRX 8.95. You are using a RadeonHD 5670. You are using the Unity or KDE desktop environment. (Either one should provoke this problem.) 2. Wait for the display to be turned off/go into sleep mode. NOT dimmed! If you catch it while it is dimmed, but before it is turned off, you will end up back at your desktop. 3. After the display is off/asleep, attempt to move your mouse or press a button on the keyboard. Observe that the system is NOT responding and the monitor is stuck in sleep mode. Actual result: The display fails to resume, anything you left open is trashed, game over man, game over! :) Expected result: The display mode should be resumed properly in the state that it was previously in. The open source radeon driver always manages to do this right. Workaround: Generate a xorg.conf file with this command: sudo amdconfig --initial Open the xorg.conf file: sudo nano /etc/X11/xorg.conf Find this line: (under Section "Monitor") Option "DPMS" "true" change it to read Option "DPMS" "false" Restart the X server. Observe that your desktop is no longer able to put the display to sleep and that AMD's proprietary display driver is contributing to increased global warming and a higher electric bill. (But doesn't screw up the X server and cause all of user's open files to be lost) To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/958279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
