!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

219 Members
59 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
15 Nov 2024
@frontear:matrix.orgfrontearwonder which phantom universe its active on06:59:34
@elvishjerricco:matrix.orgElvishJerricco what about journalctl -u display-manager.service? 06:59:47
@frontear:matrix.orgfrontearhttps://termbin.com/1adj07:00:04
@frontear:matrix.orgfrontear Nov 15 06:55:33 nixos sddm[1424]: Session started true 07:00:16
@frontear:matrix.orgfrontear Nov 15 06:55:33 nixos sddm-helper[1446]: Starting Wayland user session: "/nix/store/7jqkph5y9wxrvhx4jssvcawafvc5gqh8-sddm-unwrapped-0.21.0/share/sddm/scripts/wayland-session" "/nix/store/sig5babhahniz6lswkl9mmjm4rny0285-plasma-workspace- 07:00:25
@frontear:matrix.orgfrontearthonk07:00:29
@frontear:matrix.orgfrontearit seems to have successes pretty much everywhere here07:00:47
@elvishjerricco:matrix.orgElvishJerriccowow07:01:03
@elvishjerricco:matrix.orgElvishJerricco

it is the same bug

Nov 15 06:55:32 nixos sddm[1424]: Session "/nix/store/j4qvics8f23a03nviwnknr40a6hjxl0m-desktops/share/wayland-sessions/plasma.desktop" selected, command: "/nix/store/sig5babhahniz6lswkl9mmjm4rny0285-plasma-workspace-6.2.3/libexec/plasma-dbus-run-session-if-needed /nix/store/sig5babhahniz6lswkl9mmjm4rny0285-plasma-workspace-6.2.3/bin/startplasma-wayland" for VT 1

07:01:11
@frontear:matrix.orgfrontearwoah plasma has the gnome bug too?07:01:20
@frontear:matrix.orgfronteardamn why exactly is getty killing these dms07:01:33
@elvishjerricco:matrix.orgElvishJerricco K900: So sddm is definitely starting on vt2 and it's starting plasma on vt1 07:01:40
@k900:0upti.meK900 (Old)The plasma on vt1 thing is probably normal07:01:59
@k900:0upti.meK900 (Old)Because it's wayland right07:02:04
@frontear:matrix.orgfrontearyes this is wayland07:02:10
@frontear:matrix.orgfrontearor supposed to be anyways, too bad it wont load07:02:20
@elvishjerricco:matrix.orgElvishJerricco
In reply to @frontear:matrix.org
damn why exactly is getty killing these dms
basically, nothing is telling getty not to use tty1 and we have a default dependency on getty@tty1.service. So getty and the DE race to take it first but if getty loses it just uses it anyway and things die
07:02:35
@frontear:matrix.orgfrontearahh race conditions07:02:58
@frontear:matrix.orgfrontearlove that getty just takes it anyways, no wonder its so inconsistent07:03:12
@elvishjerricco:matrix.orgElvishJerricco
In reply to @k900:0upti.me
The plasma on vt1 thing is probably normal
when I tested this stuff before, sddm started on tty7 and immediately gave it up for plasma to use, so plasma was on tty7
07:03:25
@elvishjerricco:matrix.orgElvishJerricco frontear: Other distros typically launch the display manager on tty1 with a Conflicts=getty@tty1.service systemd clause to prevent this issue 07:04:02
@elvishjerricco:matrix.orgElvishJerriccobut we don't put the DM on tty107:04:09
@elvishjerricco:matrix.orgElvishJerriccoand the DM just finds the first available one to put the user's session on07:04:24
@elvishjerricco:matrix.orgElvishJerriccowhich is often tty1 if racing goes poorly07:04:30
@frontear:matrix.orgfrontearyeah i think i do vaguely remember a Conflicts= in arch linux way back when07:05:13
@elvishjerricco:matrix.orgElvishJerriccoSo, TL;DR: Everyone's ISO bugs about it freezing are probably all my GDM bug -_-07:05:39
@elvishjerricco:matrix.orgElvishJerriccofucking nightmare scenario07:05:51
@frontear:matrix.orgfrontearaint that the truth07:06:08
@frontear:matrix.orgfrontearon the bright side at least its no longer a mystery, things have an answer now07:06:27
@elvishjerricco:matrix.orgElvishJerricco I mean the issue is that the original GDM bug is still partly a mystery :P 07:07:16

Show newer messages


Back to Room ListRoom Version: 9