Description of problem:
When i wake up the machine, the "enter" key on the keyboard is held down (in
software) for 10-15 secounds while resuming. Quite annoying if some nautilus
launcer is marked, or if editing some text file.
Version-Release number of selected component (if applicable):
I think every time
Steps to Reproduce:
1.Mark some launcher in nautilus, on desktop etc, edit a text document, have
matlab/maple/terminal or some other text input program open
4.When VT's are OK (bug 312901), notice the 200 open windows you have to close
This also happens on my stationary machine, with kernel
(i just noticed - i tought it crashed on suspend, but when i hit "suspend"
instead of "shutdown" in error a few days ago, and discovered (because i didn't
have a paperclip handy to reset it with - it took a *LONG* time to resume (over
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Yes, this does still happen. Just reproduced it inside matlab, twice, and once
with nautilus. And it is not "the last button pushed" - it is always "enter".
However, it does not seem to show up at the first resume, but from the secound
Kernel version (on laptop, Dell Latitude D520): 220.127.116.11-64.fc7
On my stationary machine (homebuilt Intel P4), I have not seen it since
upgrading to FC8 (now running 18.104.22.168-107.fc8 #1 SMP).
Sorry for being late at submitting the info!
Can you attach output of first and second resume (ie. good and bad resumes) to
this bug as two separate text/plain attachments please.
What output? dmesg?
Sorry Kyrre, yes dmesg please.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.
Sorry, i forgot about it (it got marked as "read" in my mailprog for some
reason, probably me forgetting to unread it until done.)
Anyway, the problem seems to be gone (on both the dell laptop and the homebuilt
stationary machine), so you may close to some sort of fix'ed. Don't know what
version of kernel, tough.