mouse & keyboard suddenly freezes in 10.04

[zsolt.ruszinyák]

It happens approx. once a week, since my new install of 10.04 on the day of release. When I close the lid (set to "blank screen") and reopen it, the screen goes black. All input methods break down (keyboard, mouse, touchpad, buttons,...) Only a hard restart helps.

 I have experienced another problem, which can be related to this: Sometimes in the middle of my work the screen suddenly shuts down with a fade effect as if the screensaver was being activated, but nothing appears. Moving the mouse solves it, but it usually happens more times consecutively. I only experience these problems in 10.04, not in previous releases.

 Very very weird!
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Package: linux (not installed)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-020634-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: zsolt 1802 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 12
   Simple ctrls : 7
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=8f871f28-223c-431e-9920-af8800140628
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer INC. 1000H
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=b9d16194-66d7-4100-862b-6b43c95c9f40 ro splash quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
StagingDrivers: rt2860sta
Tags: lucid kconfig regression-release needs-upstream-testing staging
Title: [STAGING]
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
dmi.bios.date: 08/01/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1005
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd08/01/2008:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Jeremy Foshee (jeremyfoshee)]

Hi zsolt.ruszinyák,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 584736

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[zsolt.ruszinyák (zsolt-ruszinyak)]

Hello, I've installed the 2.6.34 kernel. However, I'm not sure if using the Maverick daily build is a safe option for me, I have important data in my computer and I'm afraid of messing something up with that, I need reliability at all times. I would at least wait for the beta release to come. Correct me, if I took you wrong... Otherwise I'm willing to participate to the testing in any way...

My computer is Asus EeePC 1000H with a shipped WinXP (removed already)

Thanks!

P.S. Will the "apport-collect -p linux 584736" command have any sense to run without the Maverick daily build?

[Jeremy Foshee (jeremyfoshee)]

zsolt,
    No, you are correct. The development release is still young. Would you mind running the apport command referenced above for me so that we can gather some configuration and logging on this issue?

Thanks!

~JFo

[zsolt.ruszinyák (zsolt-ruszinyak)]

Hello Jeremy, I've done that, just this message pisses me: "UnreportableReason: The running kernel is not an Ubuntu kernel" Is that ok for u anyway or should I do it some other way?

[Jeremy Foshee (jeremyfoshee)]

zsolt,
    Ah, that means you are running this command from the mainline kernel. I am working on the apport hook to allow running the command from these kernels, but it is not yet complete. Unfortunately that message keeps the data from being posted to the bug. It may not be possible, but it would be really great if you could run this from your stock kernel.

Thanks!

~JFo

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

apport information

[zsolt.ruszinyák (zsolt-ruszinyak)]

Today it happened again... I was doing some format converting in the terminal and as I was scrolling the terminal, everything suddenly froze. After some time I switched off the computer (I was afraid it could break something) but it seems to me, that the terminal process (the converting) was interrupted by this too (not mouse & keyboard breakage only), but I'm not sure...

Thanks

Is this a security vulnerability? Probably not, just curious...

[zsolt.ruszinyák (zsolt-ruszinyak)]

Again, as I say, once a week, this time in 2.6.32-23.

[zsolt.ruszinyák (zsolt-ruszinyak)]

I have to say f***! Twice a day is already too much! And yesterday it happened once too. It's starting to be very frequent and really endangers my work...

Is there any temporary workaround I can try?

[zsolt.ruszinyák (zsolt-ruszinyak)]

I'm experiencing also another mouse&keyboard freeze, this time related to Gnome Mplayer: Bug #623003. The behaviour is similar, but at least the pointer keeps on moving, however, no clicking possible. So, same result, I have to reboot...

[Matt 6:27 (goffice)]

I'm getting same effect as zsolt (#25) but only with respect to the mouse. Keyboard continues to work ok, pointer can be moved about the screen, but I cannot click on any button whether embedded in a page or the max, min, close buttons at the top of a window. It appears to happen only when a mozilla program is running (which is 99% of the time), be it Firefox (3.6.18) or T-bird (3.1.11). The freeze typically lasts for less than a minute, but that's too long for reasonable usability IMHO.

Kernel is: 2.6.32-33 generic, Gnome: 2.30.2 - Lucid 10.04. The Importance category of "Medium" seems to vastly understate the level of frustration this bug is visiting upon a lot of savvy users... never mind what it must be doing to newbies or your grandmothers who have no idea what's going on. I wish I had more programming skills to assist, but for now, all I can do is try to ID the issue to assist those smarter than me.

[Matt 6:27 (goffice)]

Update: I've now experienced this freeze without any Mozilla-based programs running, so FF and T-Bird may not be the issue.

[penalvch (penalvch)]

zsolt.ruszinyák, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]