Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15642 - [xorg-server] touchpad disabled after resume from suspend

Attached to Project: Arch Linux
Opened by Adrian C. (anrxc) - Wednesday, 22 July 2009, 19:04 GMT
Last edited by Allan McRae (Allan) - Friday, 24 July 2009, 01:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Resuming from suspend I am left without a touchpad, restarting X in hope it will reset I am left without both the keyboard and the touchpad. Restarting hal and then starting X enables both devices.

I could tag this report with [hal], but the only X related package I upgraded recently is xorg-server to 1.6.2-1, so I'll tag it with that. I am using the Synaptics driver, and never before saw this happen. My system is up to date as of 22.07.09 with the exception of the kernel package, I am running 2.6.30.1.

Only relevant log on resume is:
(EE) config/hal: couldn't initialise context: (null) ((null))
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 24 July 2009, 01:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  see last comment
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 22 July 2009, 19:09 GMT
donwgrade to previous xorg-server solves the issue? If this is confirmed should be reported to upstream.
Comment by Adrian C. (anrxc) - Wednesday, 22 July 2009, 19:56 GMT
It depends on mesa 7.5 which then depends on dri2proto 2.1 and so on and so on. Downgrade is not an option for me. However...

There is a common bug on many Acer machines where the machine would completely freeze on resume from suspend, caused by the psmouse module. Removing the module prior to suspend and loading it on resume was a workaround for a long time. X or HAL didn't have a problem with that, all input devices would continue to work like the module was not reset, until now it seems. It was a problem for such a long time that I just stopped trying on every new kernel release... now that this happened, just to cover the basics, I commented removal of psmouse from pm-utils. I tried a few clean suspend and hibernation cycles and touchpad worked every time, and more important the psmouse problem seems to be gone, at least for now.

Loading...