keyboard doesn't work after screensaver shuts down the monitor

Bug #586528 reported by Juan Montoya
110
This bug affects 21 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Invalid
Critical
Unassigned
xscreensaver (Ubuntu)
Invalid
Critical
Unassigned

Bug Description

Binary package hint: gnome-screensaver

The keyboard doesn't work when I return to work on the computer after a few minutes, long enough for the screen to go blank.

To reproduce:
Don't touch the keyboard nor mouse for a while.
After the first 5 minutes, the screensaver kicks in (matrix).
On minute 10, the screen goes blank.
Wait a few more minutes.
Move the mouse or press a key to keep working.

Just type something in the window you have already opened you'll notice that the active window does not receive any keyboard input, and you can't even press alt-tab to switch to another window.

Of course, i expect the keyboard to work as usual but it does not.

Here, when the keyboard doesn't work, you can switch to another window using the mouse and the keyboard will return to normal.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-screensaver 2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu May 27 14:47:06 2010
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=es_PE.utf8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
WindowManager: gnome-wm

Revision history for this message
Juan Montoya (th3pr0ph3t) wrote :
Revision history for this message
Ivan (grothag) wrote :

I can confirm this. Ubuntu 10.04 2.6.32-22-generic x86_64 GNU/Linux.

Revision history for this message
Pekka Vanhoja (pekka-vanhoja-gmail) wrote :

I'm having the same issue.

Dell D630
Ubuntu 10.04
linux-image-generic 2.6.32.24.25
x86_32

Revision history for this message
Robert Hrovat (robi-hipnos) wrote :

Same here. Everytime the screensaver starts, keyboard doesn't work until I click between i.e. desktop and then again in other application.

Ubuntu 10.04, 32 bit

Revision history for this message
Jens Landgré (jens-landgre-gmail) wrote :

Me too.

Dell Latitude E6500
Ubuntu 10.04, 64 bit

Revision history for this message
Pekka Vanhoja (pekka-vanhoja-gmail) wrote :

For me the issue was gone by updating to Ubuntu 10.10.

Revision history for this message
Jens Landgré (jens-landgre-gmail) wrote :

I have now upgraded to Ubuntu 10.10 and the issue remains for me, unfortunately.
Have also tried to change screensaver to xscreensaver but the behavior was the same, so I wonder if this bug is really related with gnome-screensaver. It is probably deeper down somewhere.

Revision history for this message
dexMilano (corrado-dex) wrote :

Confirmed on e4300 with 10.04.

Tested also with external keyboard.

The only workaround I tried is to minimize windows and reopen soon after.
After this everything seems ok

very annoying.

dex

Revision history for this message
Saddam (qupl) wrote :

Confirmed on desktop with Ubuntu 10.04 32-bit, kernel 2.6.34.

Revision history for this message
yesint (yesint4) wrote :

For me this only happens with Qt applications like QtCreator of VirtualBox in 10.10. Normal Gnome apps respond to keyboard as usually, but all Qt apps need to be minimized and restored to get keyboard input again. Extremely annoying!

Revision history for this message
Saddam (qupl) wrote :

Maybe. Most often this occurs for me with browser Opera (Qt).

Revision history for this message
Soh Wei Sin (wssoh85) wrote :

I having same problem, but it is on Ubuntu 9.10 which was previously upgrade from 9.04.

Linux 2.6.31-22-generic #70-Ubuntu x86_64 GNU/Linux

It happens for eclipse ide and firefox

Revision history for this message
mrsirrisrm (m-keane) wrote :

This happens for me with 10.10, 64 bit (dual boot with Win 7), which has been upgraded with each release from (i think) 9.04. Gnome 2.32.0, Linux kernel 2.6.35-27-generic. Seems to happen whether Qt applications are running or not, although I haven't tested that extensively. I have to click on another window or change desktops using the mouse, this brings the keyboard back.

Revision history for this message
Roman Kogan (romwell32) wrote :

This bug affects me still as of Ubuntu 10.10 (keyboard focus is lost when screensaver exits; application has focus, but not keyboard docus). Alt+Tab works to switch out and back in, restoring keyboard focus. Seems to happen with all applications, but I did not test this claim thoroughly. I use Opera browser and have it running most of the time.

Revision history for this message
Hans-Helmut Bühmann (h-buehmann) wrote :

Tested with 10.04 LTS

Steps to reproduce:

Use compiz as Window manager (normal visual effects), not metacity (disabled visual effects)
Move the mouse-pointer outside the window of your focused application, e.g to the top of the screen.
Wait, until the screen-saver is blank
Disable the screen-saver only using the keyboard
-> The keyboard is not working anymore.

Tested with firefox, gedit, eclipse as application. For eclipse it is not necessary to move the mouse pointer out of the window, so it may be related to the widgets the application uses.

Revision history for this message
Torsten Spindler (tspindler) wrote :

Does the work around of minimizing and maximizing the applications always work?

Revision history for this message
IsraeLins (israelins85) wrote :

Yes. For me.

Revision history for this message
Dmitriy Balakin (0x0000.ru) wrote :

For me too.

Revision history for this message
spidernik84 (alexander-rilik) wrote :

Confirming as well. Alt tabbing solves the problem each time. As Roman Kogan, I'm running opera.
Ubuntu lts 10.04.2 x64.

Revision history for this message
Jens Landgré (jens-landgre-gmail) wrote :

For me this bug has been resolved by upgrading to 11.04. This is very fortunate since I was affected by the bug about 5 times/day, making it pretty anoying.

Changed in gnome-screensaver (Ubuntu):
status: New → Incomplete
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed
Revision history for this message
Václav Haisman (vzeman79) wrote :

I am experiencing this in 15.04 Vivid. I use XFCE and xscreensaver and xflock4.

tags: added: vivid
Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Critical
Changed in xscreensaver (Ubuntu):
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Václav Haisman

Please:

1. Create a new report by following the instructions at <https://help.ubuntu.com/community/ReportingBugs#Reporting_non-crash_hardware_and_desktop_application_bugs>.

2. Send the new report link to the mail in my profile. So I can figure out if it's the same issue or a different one, and manage the report for you.

Thank you.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

If any of the original reporters in 2011 is still experiencing this bug, please set its status back to "confirmed". Thank you.

Changed in gnome-screensaver (Ubuntu):
status: Confirmed → Incomplete
Changed in xscreensaver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Václav Haisman (vzeman79) wrote :

For cross reference: #1483868.

Revision history for this message
Václav Haisman (vzeman79) wrote :

I have one more bit of information to add. I have just logged in and clicked into and Emacs X11 window. The cursor in Emacs moved to the place I have clicked onto but it stayed unfilled which means the Emacs X11 window does not have focus. So, it seems like this whole issue has something to do with focus.

Tejal (tejalravih)
Changed in xscreensaver (Ubuntu):
assignee: nobody → Tejal (tejalravih)
chaya (chaya-d-14)
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → chaya (chaya-d-14)
Changed in gnome-screensaver (Ubuntu):
assignee: chaya (chaya-d-14) → Rishabh Ksheerasagar (rishi-ksheerasagar)
assignee: Rishabh Ksheerasagar (rishi-ksheerasagar) → nobody
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Rishabh Ksheerasagar (rishi-ksheerasagar)
Changed in xscreensaver (Ubuntu):
assignee: Tejal (tejalravih) → gaurav singh (gauravkumarsingh322)
assignee: gaurav singh (gauravkumarsingh322) → nobody
assignee: nobody → gaurav singh (gauravkumarsingh322)
Changed in xscreensaver (Ubuntu):
assignee: gaurav singh (gauravkumarsingh322) → Veereshwari (kumbiveereshwari)
Changed in xscreensaver (Ubuntu):
assignee: Veereshwari (kumbiveereshwari) → gaurav singh (gauravkumarsingh322)
Changed in gnome-screensaver (Ubuntu):
assignee: Rishabh Ksheerasagar (rishi-ksheerasagar) → Veereshwari (kumbiveereshwari)
Revision history for this message
Mario Sangiorgio (mariosangiorgio) wrote :

I'm experiencing the same issues but unlike some of the people who commented in this thread it doesn't look to be an issue related to focus. Even if I change window or minimize and reopen the current one no keystroke gets detected.

Revision history for this message
Mario Sangiorgio (mariosangiorgio) wrote :

It's worth nothing that when the keyboards stops working I cannot even drop into the console using CTRL+ALT+F2, which is quite bad. Please let me know if I should open a new bug or if this one covers it.

Changed in xscreensaver (Ubuntu):
assignee: gaurav singh (gauravkumarsingh322) → nobody
Changed in gnome-screensaver (Ubuntu):
assignee: Veereshwari S.K (kumbiveereshwari) → nobody
status: Incomplete → Confirmed
Changed in xscreensaver (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Juan Montoya (th3pr0ph3t) wrote : Re: [Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

Unsubscribe

El 7:05PM Vie Oct 16, 2015, Lysenko Denis <email address hidden>
escribió:

> ** Changed in: xscreensaver (Ubuntu)
> Assignee: gaurav singh (gauravkumarsingh322) => (unassigned)
>
> ** Changed in: gnome-screensaver (Ubuntu)
> Assignee: Veereshwari S.K (kumbiveereshwari) => (unassigned)
>
> ** Changed in: gnome-screensaver (Ubuntu)
> Status: Incomplete => Confirmed
>
> ** Changed in: xscreensaver (Ubuntu)
> Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/586528
>
> Title:
> keyboard doesn't work after screensaver shuts down the monitor
>
> Status in gnome-screensaver package in Ubuntu:
> Confirmed
> Status in xscreensaver package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: gnome-screensaver
>
> The keyboard doesn't work when I return to work on the computer after
> a few minutes, long enough for the screen to go blank.
>
> To reproduce:
> Don't touch the keyboard nor mouse for a while.
> After the first 5 minutes, the screensaver kicks in (matrix).
> On minute 10, the screen goes blank.
> Wait a few more minutes.
> Move the mouse or press a key to keep working.
>
> Just type something in the window you have already opened you'll
> notice that the active window does not receive any keyboard input, and
> you can't even press alt-tab to switch to another window.
>
> Of course, i expect the keyboard to work as usual but it does not.
>
> Here, when the keyboard doesn't work, you can switch to another window
> using the mouse and the keyboard will return to normal.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: gnome-screensaver 2.30.0-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-22-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Thu May 27 14:47:06 2010
> GnomeSessionIdleInhibited: No
> GnomeSessionInhibitors: None
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64
> (20100427.1)
> ProcEnviron:
> PATH=(custom, user)
> LANG=es_PE.utf8
> SHELL=/bin/bash
> SourcePackage: gnome-screensaver
> WindowManager: gnome-wm
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions
>

Revision history for this message
Lysenko Denis (pharmasolin) wrote :

Not confirmed in 15.04, here are steps i have done to test:
1. My settings were http://i.imgur.com/CQ7aJzn.png i waited ~10 min, let monitor turn off.
2. Pressed keys on keyboard to wake monitor.
3. I have seen login screen, entered my password, system were ok, keyboard were working in opened mozilla firefox.
----
Another one test:
1. My settings were http://i.imgur.com/0zWkpND.png i waited ~ 5 min, let monitor turn off.
2. Pressed keys on keyboard to wake monitor.
3. I have seen my opened mozilla firefox with opened this bug page in it, now i'm writing this so all works.

Summary it is not a bug now, i'm closing it. If i'm done my testing wrong, please reopen this bug by checking status from "Invalid" to "Confirmed" or "New" and write your steps how you reproducing this bug.

Changed in gnome-screensaver (Ubuntu):
status: Confirmed → Invalid
Changed in xscreensaver (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Václav Haisman (vzeman79) wrote :

I am on 15.04. That it does not happen to you does not mean it does not happen to others.

Changed in gnome-screensaver (Ubuntu):
status: Invalid → Confirmed
Changed in xscreensaver (Ubuntu):
status: Invalid → Confirmed
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Abhishek solanki (abhisheksolanki18)
Changed in xscreensaver (Ubuntu):
assignee: nobody → Abhishek solanki (abhisheksolanki18)
Changed in gnome-screensaver (Ubuntu):
assignee: Abhishek solanki (abhisheksolanki18) → nobody
Changed in xscreensaver (Ubuntu):
assignee: Abhishek solanki (abhisheksolanki18) → nobody
Revision history for this message
Lysenko Denis (pharmasolin) wrote :

@Václav Haisman please provide clear steps for reproduce, otherwise i will close this. Bug creator unsubscribe yesterday. If you will not, i will close this in 2 days.

Revision history for this message
Václav Haisman (vzeman79) wrote :

@Lysenko: 22 people confirmed this. There are 2 duplicates attached to this bug report and then there is #1483868 that I was requested to fill separately. Yet, you want to close this bug. Are you for real? I have nothing more to say, except expletives.

Revision history for this message
Lysenko Denis (pharmasolin) wrote :

@Václav Haisman, this 3 bugs where reported in 2010, i have tested this bug in 15.04 unity DE, there are no bug, if you have bug provide your steps to reproduce otherwise this will be closed on Monday.

P.s. In 5 years in codebase of gnome-screensaver were a lot changes this bug seems to be fixed without marking this bug report as "closed".

Don't argue if you think i'm not right, just provide steps to reproduce it, i will try this, if your steps will cause this bug, i will triagle this bug so devs can fix this. if you dont have valid steps to reproduce, there are no need to write to devs, they wouldn't fix this.

Cheers.

Revision history for this message
Václav Haisman (vzeman79) wrote :

@Lysenko: FFS, there was somebody else commenting on this issues this month. The bug is still the same, there is nothing else to add to this. The reproduction scenario is still the same.

Revision history for this message
Lysenko Denis (pharmasolin) wrote :

You have opened bug report #1483868 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1483868 you had been asked questions to complete your bug report, and to help find out where exactly problem is. Why you ignored it? This bug report will be closed as original reported unsubscribe, and it were reported in unsupported now Ubuntu version. If you want to add something new - modify your bug report, provide more information to help fix it. Thanks.

Changed in gnome-screensaver (Ubuntu):
status: Confirmed → Invalid
Changed in xscreensaver (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.