Closing as expired since the original reporter hasn't responded to the
information request.
For everyone else commenting on this bug, while your symptoms may sound
similar to this one, in truth they're probably all unrelated underlying
issues. They are very likely to be hardware-, kernel-, or
Confirming this bug with 64bit Gutsy on laptop Acer Aspire 5100 with AMD
Turion 64x2.
Happens after long idle time, i.e. both screensaver (15 minutes) and APM (45
minutes) has kicked in.
Screen is locked and I can't log back in since keyboard is completely
unresponsive. Mouse still works.
When
Confirming this bug with 32bit Feisty on a Dell Inspiron 6400 with a
Core Duo processor. My previous laptop (Toshiba Satellite Pro L10 with a
Celeron M processor) had no such problems from Dapper to Feisty. The
only other difference between the two is that I'm using the low-latency
kernel on my
Willem,
Do you still have this problem in Feisty or with the latest Gutsy live CD?
** Changed in: xserver-xorg-input-keyboard (Ubuntu)
Sourcepackagename: None = xserver-xorg-input-keyboard
Assignee: (unassigned) = Pascal De Vuyst
Status: Confirmed = Incomplete
--
Random keyboard
The problem is solved adding the option notsc to the kernel boot
parameters.
Sadly, this didn't work for me.
The boot option I'm using
title Ubuntu, kernel 2.6.17-10-generic
root(hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic
It worked! Thanks a lot magoscuro!!!
--
Random keyboard failure in X
https://launchpad.net/bugs/58884
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The problem is solved adding the option notsc to the kernel boot
parameters.
The problem occurs on Core 2 Duo ( merom ) procesors using 64 bits
distributions.
The solution was posted on the Gentoo forum,
http://forums.gentoo.org/viewtopic-t-513939.html
In this aspect gentoo comunity is far
Well, thank you for your contribution. However, please do not diss ubuntu
on a bug tracker.
On 11/8/06, magoscuro [EMAIL PROTECTED] wrote:
The problem is solved adding the option notsc to the kernel boot
parameters.
The problem occurs on Core 2 Duo ( merom ) procesors using 64 bits
Same Problem Here,
I test edgy and gentoo 2006.1 with Xorg 7.1, both 64 bits.
The problem occurs only in 64 bits mode, with nvidia, vesa and nv drivers, I've
also try deactivating acpi ( noalpi noacpi). But nothing help.
Buttons don't respond in Gnome and Kde, and I get repeated letters when
I
This doesn't seem to be a problem with Ubuntu/Kubuntu, but something
related to Xorg7.1 I guess. I've tried amd64 final versions of
Ubuntu/Kubuntu and I am getting the exact same problem with both.
Trying to get rid of this problem, I've finally ended installing Gentoo
2006.1 amd64 on my system.
I'm having this problem repeatedly with Ubuntu 6.06, fully up to date.
It's most common in the mornings when I get into work; for the last 5
days or so I've had to kill X each morning. It's happened a couple of
times when I've been idle for a while also, and may be related to either
xscreensaver
This does not seem related to this bug. Sorry. Please either create a new
bug, or find one that matches your description.
On 10/26/06, John Tobin [EMAIL PROTECTED] wrote:
I'm having this problem repeatedly with Ubuntu 6.06, fully up to date.
It's most common in the mornings when I get into
I'm having the same problem with KUbuntu Breezy Badger, but I don't get
the unbind key errors in Xorg logs when it happens.
When it occures
(1) I cannot ctrl-alt-fn to switch virtual terminals
(2) Only one of my lock keys works (f-lock) - scroll lock, num lock and caps
lock don't. By 'works' I
** Tags added: xorg
** Tags removed: x
--
Random keyboard failure in X
https://launchpad.net/bugs/58884
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bad news, after running for a day without any problems it started
crashing again with the same old I830WaitLpRing message. So the latest
git version of the driver still seems to have the same problem.
--
Random keyboard failure in X
https://launchpad.net/bugs/58884
--
ubuntu-bugs mailing list
So interesting fact here, if I use the x86 architecture, it works great,
no failures whatsoever, although if the wirless radio is on it fails to
boot. But thats besides the point. The point is, when I used the
64bit, i had random keyboard/mous/x failures and with the 386, i do not.
--
Random
Obviously this is a problem.
** Changed in: Ubuntu
Status: Needs Info = Confirmed
** Description changed:
When I am logged into X (edgy), at some point the keyboard will
completely stop responding in X. On the console it still works however:
I can switch using ctrl+alt+n to a
I fetched the latest i810 driver from the x.org git repository, compiled and
installed it.
Now I am testing that version. So far I have not experienced any crashed nor
any keyboard or mouse failures. So this version looks good (64bit), but I am
still testing it.
The x.org git repository:
git
Same problem here using beta release for Kubuntu 6.10 (codenamed Edgy
Eft) 64 bit edition on a Dell Inspiron 9400:
Screen UltraSharp Wide Screen WUXGA (1920 x
1200) Display with TrueLife
Motherboard Dell 0YD479
Chipset Intel
In fact my dell notebook is also an intel core2 duo 64bit system.
Additionally to the keyboard and mouse lockups, my X11-Sessions thend to
crash from time to time. I have spent some hours analysing the log files
but the only thing I found is the following message from X11 which
appears after the
I have the same problem with Edgy Beta 1 kubuntu. I am using the 64bit
version with a core2duo. The problem only occurs when I am in kde, and
I also have a dell. I cannot use anything with the keyboard and the
mouse semi-works as stated above.
--
Random keyboard failure in X
I experienced similar problems with my new DELL XPS m1210 Notebook and
edgy (Knot 3). However in my case not even the CTRL-ALT-BACKSPACE
resp. CTRL-ALT-N keystroke works. Some times the keyboard starts
working again after some minutes but in the majority of cases it will
not resume work.
Can you retry after upgrading?
There's a change in Metacity which could fix it.
I believe I've seen it too. in my case shading/unshading the window by
clicking on the window title solved it, you may have to change yours
windows preferences.
** Changed in: Ubuntu
Status: Unconfirmed =
23 matches
Mail list logo
