| Commit message (Collapse) | Author | Age |
|\
| |
| | |
gnome3.mutter: fix crash on startup with nvidia drivers
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently some assembly has not been ported. This commit should fix
it:
https://github.com/gnustep/libobjc2/commit/b952a21abe8b0f9878b1ec5161ea530058512f4a#diff-e49aa4e60f8ccec1be46afc5e6ffcee5
But no release has been made by the gnustep team yet!
|
| | |
|
|\ \
| | |
| | | |
dde-daemon: init at 3.2.24.7
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
mate.python-caja: 1.20.0 -> 1.20.1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/python-caja/versions
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
Necessary for WebDAV over TLS, etc.
|
|\ \ |
|
| |\ \
| | | |
| | | | |
plasma5: 5.13.5 -> 5.14.0
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
gnome3.gdm: Always reset the environment for new sessions
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When GDM launches a new session it will inherit the user's systemd
environment (but only unset variables). If `__NIXOS_SET_ENVIRONMENT_DONE` is set
in the user's systemd environment it will prevent the environment to be set
properly or updated (eg. after having done a system rebuild).
Gnome sessions exports their environment to systemd at startup. If something
is keeping the user's systemd process alive (eg. ssh) launching a new gnome
session after logging out will result in a broken PATH. Specifically the PATH
will be inherited from GDM and never reset.
We patch GDM to never inherit `__NIXOS_SET_ENVIRONMENT_DONE` so new sessions
will always reset their base environment.
fixes https://github.com/NixOS/nixpkgs/issues/48255
For more info about the environment setup:
https://github.com/NixOS/nixpkgs/pull/45784
|
| |\ \ \ \
| | | | | |
| | | | | | |
dde-polkit-agent: init at 0.2.1; dpa-ext-gnomekeyring: init at 0.1.0
|
| | | | | | |
|
| | |/ / / |
|
| | | | | |
|
|\| | | | |
|
| |/ / / |
|
|\| | | |
|
| |\ \ \
| | | | |
| | | | | |
deepin-wm: init at 1.9.32
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
deepin-wallpapers: init at 1.7.5; deepin-desktop-schemas: init at 3.2.18.7
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
SAGA, SAGA LTS release, dependencies and QGIS SAGA plugin
|
| | | | | |
|
|\| | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
deepin.dde-api: init at 3.1.30
|
| | | | | | |
|
| | | |_|/
| | |/| | |
|
| |/ / / |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
Standard library now contains stdenv.lib.versions.majorMinor,
which does the same.
|
| | |
| | |
| | |
| | |
| | | |
It was used by some themes in the past, but it broke them whenever GNOME
was updated, so it should not be used anymore.
|
|\ \ \
| | | |
| | | | |
nixos/xserver: Implement configuration of NVIDIA Optimus via PRIME
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds configuration options which automate the configuration of NVIDIA Optimus using PRIME. This allows using the NVIDIA proprietary driver on Optimus laptops, in order to render using the NVIDIA GPU while outputting to displays connected only to the integrated Intel GPU. It also adds an option for enabling kernel modesetting for the NVIDIA driver (via a kernel command line flag); this is particularly useful together with Optimus/PRIME because it fixes tearing on PRIME-connected screens.
The user still needs to enable the Optimus/PRIME feature and specify the bus IDs of the Intel and NVIDIA GPUs, but this is still much easier for users and more reliable. The implementation handles both the X configuration file as well as getting display managers to run certain necessary `xrandr` commands just after X has started.
Configuration of commands run after X startup is done using a new configuration option `services.xserver.displayManager.setupCommands`. Support for this option is implemented for LightDM, GDM and SDDM; all of these have been tested with this feature including logging into a Plasma session.
Note: support of `setupCommands` for GDM is implemented by making GDM run the session executable via a wrapper; the wrapper will run the `setupCommands` before execing. This seemed like the simplest and most reliable approach, and solves running these commands both for GDM's X server and user X servers (GDM starts separate X servers for itself and user sessions). An alternative approach would be with autostart files but that seems harder to set up and less reliable.
Note that some simple features for X configuration file generation (in `xserver.nix`) are added which are used in the implementation:
- `services.xserver.extraConfig`: Allows adding arbitrary new sections. This is used to add the Device section for the Intel GPU.
- `deviceSection` and `screenSection` within `services.xserver.drivers`. This allows the nvidia configuration module to add additional contents into the `Device` and `Screen` sections of the "nvidia" driver, and not into such sections for other drivers that may be enabled.
|