| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\
| |
| | |
remove desktopManagerHandlesLidAndPower
|
| |
| |
| |
| |
| |
| | |
As discussed on https://github.com/NixOS/nixpkgs/pull/9642, the option
is not necessary because all desktop managers already stopped handling
it (and delegated to systemd).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
(version 2) A better implementation of #10039, after #12357.
This time I did more thorough checking.
See commit messages for details.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts most of 89e983786a, as those references are sanitized now.
Fixes #10039, at least most of it.
The `sane` case wasn't fixed, as it calls a *function* in pkgs to get
the default value.
|
|\ \ \ |
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The PR wasn't good enough yet.
This reverts commit b2a37ceeea8c38ec71447f8dae1e6890a8cf982d, reversing
changes made to 7fa9a1abce623aaf18b22f5dca3fc8a44a494e8d.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts most of 89e983786a, as those references are sanitized now.
Fixes #10039, at least most of it.
The `sane` case wasn't fixed, as it calls a *function* in pkgs to get
the default value.
|
| | | | |
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- added numlock on boot switch
- simply add :
services.xserver.displayManager.sddm.autoNumlock = true;
to configuration.nix and sddm will start
with numlock enabled.
|
|/ / /
| | |
| | |
| | | |
Use hardware.opengl.extraPackages instead.
|
|/ /
| |
| |
| |
| |
| | |
- add missing types in module definitions
- add missing 'defaultText' in module definitions
- wrap example with 'literalExample' where necessary in module definitions
|
| | |
|
|\ \
| | |
| | | |
light-locker (lockscreen for lightdm)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- if xserver.tty and/or display are set to null, then don't specify
them, or the -logfile argument in the xserverArgs
- For lightdm, we set default tty and display to null and we determine
those at runtime based on arguments passed. This is necessary because
we run multiple X servers so they can't all be on the same display
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
These options allow setting the start and stop scripts for the display
manager. Making these configurable is necessary to allow some hardware
configurations. Upstream ships empty scripts by default, anyway.
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixed usage of pam_env.so PAM module in lightDM and GDM.
|
| |
| |
| | |
Add 'focus_password yes' if defaultUser is set, to reflect the description of defaultUser.
|
| | |
|
| |
| |
| |
| |
| | |
Emphasize experimental nature slightly less, but say it's only really
tested with Gnome.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
It was complaining about not having write permission to
$HOME/.local/share/user-places.xbel (because .local/share didn't exist
yet).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This seems to have been confusing people, using both xlibs and xorg, etc.
- Avoided renaming local (and different) xlibs binding in gcc*.
- Fixed cases where both xorg and xlibs were used.
Hopefully everything still works as before.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
Or else users may see this unfriendly message:
error: cannot coerce null to a string, at .../nixos/modules/services/x11/display-managers/gdm.nix:107:49
|
| |
|
|
|
|
| |
This also makes it consistent with KDE's inhibit message.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes the option and explicitely sets it for each desktopManager.
Reasoning: Currently,
services.xserver.displayManager.desktopManagerHandlesLidAndPower is set
to true by default. This creates a problem for users without desktop
environments activated, since lid management simply doesn't work
(and they have to be lucky to find this option).
See issue #9671
|
|
|
|
| |
Also no substitution.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
49821433242c4f44cff038a039ead3bc9741fbf1
|
|/ |
|
|
|
|
|
|
|
|
|
| |
This is needed by most window managers. Desktop environments
usually launch dbus-launch if a session hasn't been started yet
so this shouldn't hurt. The worst it can happen is that one
dbus session will be unused in case it's started twice.
The GDM change is backported from recent gdm.
|
|\
| |
| |
| |
| | |
DamienCassou/document-desktopManagerHandlesLidAndPower-in-systemd
Explanation to desktopManagerHandlesLidAndPower
|