GNOME Bugzilla – Bug 427905
Do not detect mouse action on second screen of Dual Desktop settings
Last modified: 2010-02-27 13:08:01 UTC
Please describe the problem: Every time i work on a dual deskop. My screen saver activates itself if i do not use keyboard or go on the first screen with the mouse. The systeme do not detect the mouse activity on my secondary screen. Steps to reproduce: 1. Reads a documents and only use the mouse for X minutes (X is the time for your screen saver to come when no activities) 2. 3. Actual results: Screen-saver or wethever action I asked to launch when no activiteis for X minutes. Expected results: nothing (mouse activity detected) Does this happen every time? yes Other information: ubuntu 7.04 Beta (Feisty Fawn) Dual desktop mode kernel : 2.6.20-14-generic (i686 GNU/Linux) Gnome : 2.18.x Graphic Card : Ati X700
*** Bug 449043 has been marked as a duplicate of this bug. ***
*** Bug 437300 has been marked as a duplicate of this bug. ***
Confirming because of the duplicates.
*** Bug 480230 has been marked as a duplicate of this bug. ***
*** Bug 463149 has been marked as a duplicate of this bug. ***
*** Bug 529531 has been marked as a duplicate of this bug. ***
*** Bug 537666 has been marked as a duplicate of this bug. ***
*** Bug 555086 has been marked as a duplicate of this bug. ***
I think this should be fixed in trunk now that we're using the IDLETIME xsync counter. Can anyone please confirm this? Thanks.
Could this work in 2.24 ?
The problem still exists with Ubuntu 8.10 with Gnome 2.24. What further information is need to provide a solution for this issue. Please advise, as this issue is becoming a problem.
Is the IDLETIME xsync counter fix mentioned above in Gnome 2.24 (gnome-screensaver 2.24.0) or not? If it is, the fix did not work.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
This is ridiculous. So the developer who claims he may have fixed the bug refuses to tell us in which version it may be fixed, users have confirmed that it's still broken in more recent versions than originally reported, and you're going to close it? "I've found an excuse for not trying to fix this three-year-old bug" does not count as "resolved" in my book. If you claim it's fixed, tell us in which version we can test the fix. Otherwise leave it open.
Heya. Thanks Curt, my bad. I didn't read carefully enough. Do you still have this issue then? In which version?
Sorry about the rant. You can probably understand the frustration of those of us waiting years for a fix on this issue. Anyway, as you can see from the log for this bug report, it was definitely present in 2.18 and 2.24, and probably all versions in between. I can try to set up a 2.28 system (Ubuntu 9.10) on which to test, but it will be a fair amount of work, and I'd rather avoid doing it if the IDLETIME xsync counter fix is in 2.24. If it is, we know that that change did not fix the bug.
The code to use IDLETIME was introduced in 2.25, which is why you need to test it on something > 2.24.
(In reply to comment #16) > Sorry about the rant. You can probably understand the frustration of those of > us waiting years for a fix on this issue. > Yep. But you were right :) Again: Sorry. I am closing this bug as per comment #17. If you happen to experience this issue with >2.24, please reopen. Otherwise feel free to set to VERIFIED.