Skip to content

Missing input devices when using LightDM #3843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
schauveau opened this issue Mar 9, 2019 · 2 comments
Closed

Missing input devices when using LightDM #3843

schauveau opened this issue Mar 9, 2019 · 2 comments

Comments

@schauveau
Copy link

I am using sway compiled from git master on Debian and I noticed that my Fn+Brightness keys were not reporting any events when Sway is started by LightDM (via a custom desktop file in /usr/share/wayland-sessions/ ). Everything works fine when Sway is manually started from a VT.

So I eventually figured out that Sway via LigthDM is missing 3 input devices including the one that reports brightness key events. However, those missing input devices exist and can be tested using evtest or libinput. I also noticed that the missing input devices (and the brightness key events) become visible after switching back and forth to another VT.

I suspect a race condition between LightDM and Sway (because of ibus?)

I am using a SSD so Sway starts quite fast. Adding a sleep 1 before sway appears to solve the problem for me.

System information:

  • debian buster
  • ligthdm 1.26.0-3
  • sway version 1.0-rc1-145-g19df2e59 (Mar 6 2019, branch 'master')
@ddevault
Copy link
Contributor

ddevault commented Mar 9, 2019

Report this bug with lightdm please.

@ddevault ddevault closed this as completed Mar 9, 2019
@schauveau
Copy link
Author

canonical/lightdm#63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants