after suspend resum touchpad doesn't work

Bug #84133 reported by stefab
16
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: acpi-support

After suspend on, ram on resume, laptop touchpad doesn't work anymore.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

stefab, can you please attach the output of the following commands?

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to attach, there will be too much output to include inline in the report. Also please be sure to run with sudo, these commands need root privileges to obtain required information.

Thanks!

Changed in acpi-support:
status: Unconfirmed → Needs Info
Revision history for this message
stefab (bluefuture) wrote :

Next time ask to users only information really need for solve the specific bug because the full dmidecode has info about cpu id and pc serial numbers that IMHO are sensitive data that newbies can expose in this public framework.
I can help you solving this bug if you could give me some more info of what is locking synaptic from resume because it is no more in /proc/bus/input/devices.

Revision history for this message
stefab (bluefuture) wrote :

Next time ask to users only information really need for solve the specific bug because the full dmidecode has info about cpu id and pc serial numbers that IMHO are sensitive data that newbies can expose in this public framework.
I can help you solving this bug if you could give me some more info of what is locking synaptic from resume because it is no more in /proc/bus/input/devices.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Marked as confirmed based on (partial) availability of requested logs.

stefab, would it be possible for you to run the lspci commands under sudo? The attached logs indicate permission denied errors - to get useful data, lspci needs root privileges. Thanks!

Also, it isn't necessary to compress the logs; in fact, one attachment per command makes it easier to access for devs to access the information.

Re sensitive information - the output of these commands is a standard ACPI debugging request. If you believe the information is sensitive and should not be requested, you could consider raising it on sounder, it is certainly out of scope for the bug report. Thanks, ii!

Changed in acpi-support:
status: Needs Info → Confirmed
Revision history for this message
stefab (bluefuture) wrote :
Revision history for this message
stefab (bluefuture) wrote :
Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
Revision history for this message
Ben Collins (ben-collins) wrote :

Confirmed bugs need to be assigned to ubuntu-kernel-team.

Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
importance: Undecided → Medium
Revision history for this message
Markus Kienast (elias1884) wrote :

all tab-scrolling things don't work anymore after resume, pointing works.

Sony Vaio VGN S560P

By the way, I believe launchpad needs a more advanced Hardware Database. One that is linked with the user profiles. I would upload my dmidecode, lshw or whatever once to my profile and the bug fixing crew could access that information then.

They could for example use an interface and say, what system components do the bug reporters have in common.

That way they could more easily track down faulty hardware. I can't see why you the bug-fixers have to download all the lshw files etc. by hand to investigate. what do we have computers for?

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Closing (marking as invalid) due to lack of activity - last user update was 17 months ago (June 2007).

Changed in linux:
status: Incomplete → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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