| Summary: | Weston crashes when opening input device '/dev/input/event11' | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Ryan <supermarioryan> |
| Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | supermarioryan |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Weston log
Output of udevadm info --name=/dev/input/event11 --attribute-walk Patch to improve error debugging Only abort weston startup if seat incomplete Weston log with cool new patches |
||
|
Description
Ryan
2013-05-12 19:16:09 UTC
Created attachment 79208 [details]
Weston log
Created attachment 79209 [details]
Output of udevadm info --name=/dev/input/event11 --attribute-walk
Cheap laptops have accelerometers?
Hi Ryan, thanks for opening this bug report. I'm going to attach a patch that will generate some debug messages in weston-launch about why opening the device failed. Would you be able to apply that patch and then include the output from weston-launch when running with that patch. Created attachment 79577 [details] [review] Patch to improve error debugging I can't at the moment, as the machine at which I get the bug appears to have a small spot of hardware failure. :/ Ryan, oh dear. I've also attached a patch which should allow weston to continue to start provided the seat has both a keyboard and pointer. Created attachment 79579 [details] [review] Only abort weston startup if seat incomplete Laptop decided to work again! :D So, how do I apply a patch? :) Figured out how to do it, nvm Got both patches applied, will build and test :) Well, it works with both the patches! I'll attach the log here Created attachment 79580 [details]
Weston log with cool new patches
I had the same problem, I am also running Arch... The patch worked(my screen is turned 90 degrees, but it works...) and I found a way to stop it from happening. You must unload the acer_wmi module with 'sudo modprobe -r acer_wmi'. That solves it for me :) Kristian has merged a version of this patch so that we will not abort compositor creation if there is a problem opening an input device: commit f9e9d0d434e06b86d527f2b19f0d48a7539114b4 Author: Rob Bradford <rob@linux.intel.com> Date: Mon Jun 3 18:46:13 2013 +0100 udev-seat: Fail input setup only if no devices are found Rather than failing if we cannot open any single device fail the input setup if there are no input devices added. https://bugs.freedesktop.org/show_bug.cgi?id=64506 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.