Skip to content
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.

Sign up for GitHub

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

Jump to bottom

X11 input broke #22290

Closed
ikervagyok opened this issue Jan 30, 2017 · 6 comments
Closed

X11 input broke #22290

ikervagyok opened this issue Jan 30, 2017 · 6 comments
Labels
0.kind: regression Something that worked before working no longer
Milestone
17.03

Comments

@ikervagyok
Copy link
Contributor

ikervagyok commented Jan 30, 2017 •
edited

Issue description

between 8a104aa..63f609b (current master) my x11-input broke, no easy way to log in/examine (behind a corporate firewall...)

Steps to reproduce

nixos-rebuild boot; reboot

Technical details

  • System: (NixOS: 8a104aa)
  • Nix version: (1.11.6)
  • Nixpkgs version: (17.03.git.63f609b1a4)
@ikervagyok
Copy link
Contributor Author

maybe this is causing it: 82bcfef
will look into it later.

@ikervagyok
Copy link
Contributor Author

confirmed, reverting 82bcfef caused this issue to go away.
tested both with services.xserver.libinput.enable = true and false

@ikervagyok ikervagyok mentioned this issue Jan 31, 2017
Merged
1 task
@fpletz fpletz added the 0.kind: regression Something that worked before working no longer label Jan 31, 2017
@fpletz fpletz added this to the 17.03 milestone Jan 31, 2017
@fpletz
Copy link
Member

fpletz commented Jan 31, 2017

I can also confirm this. I'll have another look at the code to see if we can fix this before reverting.

Thanks for the report and the investigative work!

@MP2E
Copy link

MP2E commented Jan 31, 2017

Exact same issue is happening on my end, thank you for looking in to it!

@mdorman
Copy link
Contributor

mdorman commented Feb 1, 2017

This seems like a revert-first-fix-later sort of bug.

@fpletz
Copy link
Member

fpletz commented Feb 1, 2017

Agreed, I couldn't find out what's wrong with that commit. 😞

@vcunat vcunat mentioned this issue Feb 1, 2017
Closed
@fpletz fpletz closed this as completed in 24f3abd Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.kind: regression Something that worked before working no longer
Projects
None yet
Milestone
17.03
Development

No branches or pull requests
4 participants
@fpletz @MP2E @mdorman @ikervagyok