!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

201 Members
55 Servers

Load older messages


SenderMessageTime
8 Jan 2026
@sandro:supersandro.deSandro 🐧yap, done since yesterday 😂 https://github.com/KDE/plasma-login-manager/commit/d45612943e698cef15feb2ca43e60c9322b0c0be04:43:08
@sandro:supersandro.deSandro 🐧

Plasma Login Manager is being released with Plasma 6.6 and is already
being integrated into Fedora KDE and KDE Linux. It's long since stopped
being a prototype, so let's stop saying it is so people who look at
this project aren't confused anymore.

04:44:08
@jtelscott:frei.chat@jtelscott:frei.chat 08:30:18
@jtelscott:frei.chat@jtelscott:frei.chat removed their display name jtelscott.08:30:21
@jtelscott:frei.chat@jtelscott:frei.chat left the room.08:30:22
@sandro:supersandro.deSandro 🐧Someone knows a way to automatically disable monitors when they are turned off?21:38:55
@k900:0upti.meK900In most cases the system just doesn't know21:53:57
@sandro:supersandro.deSandro 🐧hmmm, sad22:43:55
11 Jan 2026
@9hp71n:matrix.orgghpzin changed their display name from ghpzin (moved to @ghpzin:envs.net) to ghpzin.15:04:59
@ghpzin:envs.net@ghpzin:envs.net left the room.16:16:15
13 Jan 2026
@jopejoe1:matrix.orgjopejoe1 (4094@epvpn) changed their display name from jopejoe1 (4094@39c3) to jopejoe1 (4094@epvpn).08:26:22
@k900:0upti.meK900Plasma 6.6 beta cooking16:37:21
@k900:0upti.meK900OK I think I have everything building now17:45:17
@k900:0upti.meK900The next step is to see if it actually runs17:45:31
@k900:0upti.meK900And after that we can think about wiring up plasma-login-manager17:45:40
@k900:0upti.meK900OK plasma-login-manager works20:40:47
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/pull/47979720:40:48
@k900:0upti.meK900Have fun20:40:51
@emilazy:matrix.orgemilythey made a greenfield login manager that supports X…?20:44:10
@k900:0upti.meK900No20:44:43
@k900:0upti.meK900They forked SDDM20:44:45
@k900:0upti.meK900 And it only supports X sessions 20:44:53
@emilazy:matrix.orgemily
    # don't install generic nixos display manager unit
    systemd.services.display-manager.enable = false;

I don't think this is safe because we rely on conflicts/ordering stuff with it

20:45:29
@emilazy:matrix.orgemily maybe ElvishJerricco knows for sure though 20:45:34
@emilazy:matrix.orgemilyfor example20:45:56
@emilazy:matrix.orgemily
    # We can't just rely on 'Conflicts=autovt@tty1.service' because
    # 'switch-to-configuration switch' will start 'autovt@tty1.service'
    # and kill the display manager.
    systemd.targets.getty.wants =
      lib.mkIf (!(config.systemd.services.display-manager.enable or false))
        [
          "autovt@tty1.service"
        ];
20:45:58
@emilazy:matrix.orgemilyI think you'll need to at least make it an alias or whatever20:46:28
@k900:0upti.meK900Ughhhhhhhhhhh20:46:31
@elvishjerricco:matrix.orgElvishJerriccough20:46:41
@elvishjerricco:matrix.orgElvishJerricco ideally, the way that would work is that every display manager would provide their own service and alias themselves as display-manager.service and display-manager.service wouldn't actually exist 20:47:04

Show newer messages


Back to Room ListRoom Version: 9