Sddm fails to launch

Help
1

Ever since the recent change to nvidia discussed here, sddm fails to launch. I wonder if I need to add an additional specification for my driver. This is my config, which had been working. My card is a GeForce MX330.

{ config, lib, pkgs, ... }:
{

  hardware.graphics = {
    enable = true;
  };

  services.xserver.videoDrivers = ["nvidia"];

  hardware.nvidia = {
    modesetting.enable = true;
    open = false;

    nvidiaSettings = true;

    prime = {
      sync.enable = true;
      intelBusId = "PCI:0:2:0";
      nvidiaBusId = "PCI:1:0:0";
    };

  };
}
1 Like
2

Couple things:

  • Can you confirm the bus IDs are correct by running nix run github:eclairevoyant/pcids?
  • What’s the error when starting SDDM if any?
3

The utility confirms the PCI ids. I don’t get an error message. I get a blank screen with a mouse cursor, then back to the console where it left off, without any error message.

I don’t know if this is relevant, but since it never happened to me before I’ll mention it: after I couldn’t launch, I booted into the prior generation. Sddm launched fine, but plasma would not start. Actually, my system was locked because I couldn’t switch to tty. I had to reboot, switch to tty, do a rebuild, reboot, and everything was back to normal. A little harrowing that I couldn’t reboot straight-away into the prior generation, but I expect that part is plasma related, not nvidia related.

I appreciate your help.

4

Do a journalctl --boot -1 after a reboot in which you can’t sign in.

5

I got the same issue on unstable recently with an AMD card. sddm-greeter-qt crashes. I have just returned to a previous version at the moment as I have a number of issues stemming from recent updates so I don’t have any more info or a fix for you…

6

That sounds the same but my card is Intel. I’m holding off upgrading until I have time to deal with it.

7

Should be easy to at least tell what’s going wrong if either of you boot it in a broken state once, and then share the logs of journalctl --boot -1 (i.e., the previous boot). Without knowing what’s going wrong it’s not that certain that it’ll be magically fixed.

8

I saw the earlier message and will do this really soon. Just need to work with and not on my computer for a while. I’ve got some deadlines. Thanks.

1 Like
9

Had a minute to do this. Should I attach the full journal or post it? It’s very long, but I may miss the important bits. Things seem to get a little hairy around line 1500 with

Sep 03 12:37:28 nixos kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Sep 03 12:37:28 nixos systemd[1]: systemd-rfkill.service: Deactivated successfully.
Sep 03 12:37:28 nixos kernel: snd_hda_codec_hdmi ehdaudio0D2: HDMI: audio coding type 0 not expected
Sep 03 12:37:29 nixos sddm-greeter-qt6[1371]: No shell integration named "layer-shell" found
Sep 03 12:37:29 nixos sddm-greeter-qt6[1371]: Loading shell integration failed.
Sep 03 12:37:29 nixos sddm-greeter-qt6[1371]: Attempted to load the following shells QList("layer-shell")
Sep 03 12:37:29 nixos sddm-helper-start-wayland[1358]: "Fontconfig error: \"/etc/fonts/fonts.conf\", line 5: not well-formed (invalid token)\nFontconfig error: Cannot load config file from /etc/fonts/fonts.conf\n"
Sep 03 12:37:29 nixos sddm-greeter-qt6[1371]: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 03 12:37:29 nixos sddm-greeter-qt6[1371]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                              
                                              Available platform plugins are: offscreen, minimalegl, eglfs, linuxfb, xcb, vnc, vkkhrdisplay, minimal, wayland-egl, wayland.
Sep 03 12:37:29 nixos systemd-coredump[1435]: Process 1371 (sddm-greeter-qt) of user 175 terminated abnormally with signal 6/ABRT, processing...
Sep 03 12:37:29 nixos systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Sep 03 12:37:29 nixos systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 03 12:37:29 nixos systemd[1]: Started Process Core Dump (PID 1435/UID 0).
Sep 03 12:37:29 nixos systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.

It could be wayland-related, and nvidia a red herring. (I actually don’t see an option to upload the whole journal.)