20
[Question] Fedora KDE defaults to console mode if I don't turn on the display during boot-up (lemmy.world)
submitted 1 year ago by to c/linux@lemmy.ml
15 comments fedilink hide all child comments
 

Any way to force the desktop to load regardless? I know, typing startx isn't hard, but I would like not to. Tnx!

all 16 comments

sorted by: hot top controversial new old
[–] 3 points 1 year ago (1 child)

Had the same problem on fedora (no issue on bazzite, nobara, or arch). First time it was xwayland that kept crashing without a display present for some reason, second time I never solved since I was distro hopping the fedora family of distros but it seemed to be a problem with SDDM

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 3 points 1 year ago (5 children)

    That seems strange. What's in the log?

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] [S] 2 points 1 year ago (4 children)

    I'll check them tomorrow. Should I look for some specific messages? Or the general KDE init process?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago (3 children)

    Boot log/kernel/dmesg, X/Wayland/kde primarily. Been a long time since I've had to troubleshoot something like this so I don't know the new kids on the block. Maybe upstart or dracut? Whatever manages the boot process now

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 1 year ago (2 children)

    I checked the logs and can't find anything interesting. I am not that knowlagable so you'll have to forgive me. I used journalctl -b -k to get the log from the current boot and piped it into grep for searching. There is no mention of kde, x11, xorg or wayland. Ok, editing this while typing. SDDM is segfaulting. I have no idea what that is, but another comment mentioned it. The message reads sddm-greeter-qt(1387): segfault ar 1b .... libLayerShellQtInterface.so.6.4.1... Guess that's the issue?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Yeah that might be it. Sddm is a display manager, you might be using it for your login screen.

    You might be able to work around it by just setting the service to restart automatically, so that it comes up properly once a display is attached. But if you can, I would try reproducing it on a fresh and fully updated install, and open a bug report to the maintainers if you can. Linux developers generally try to make really sure their programs don't crash like that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 5 points 1 year ago (6 children)

    It still starts the KDE session, but it's probably on another term output. Hit ALT+F1 and see if it shows, but it depends on the distro, so it could F1, F6, F7...etc

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] [S] 1 point 1 year ago (5 children)

    F1 is just a blank conosle with a blinking curses and you can't type anything into it. F2/3/4 open a new terminal from where I can log in, but none seem to have a KDE session running. Gotta check out the other F keys. Just in case none of the work, is there a solution you know of?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 1 year ago (4 children)

    I'm guessing it's similar to this: https://discuss.kde.org/t/plasma-doesnt-start-when-external-monitors-are-plugged-in/17350

    You're probably on a laptop and have multiple GPUs enabled at the same time. If not, you're defining Nvidia drivers with something trying to be smart about when to enable the actual outputs or not.

    You can either make sure to have the display turned on, or make it super clear to the drivers to always enable a display regardless of whether it detects a display.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 1 year ago (3 children)

    I should have provided more details about my setup, but I was kinda hoping that it turns out to be trivial. I am on a desktop PC, AMD gpu, Mesa drivers, one 1440p monitor. Nothing special about the setup. I'll have a look at the URL you provided and try a few things tomorrow.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [+] -1 points 1 year ago (3 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 1 year ago (2 children)

    Ehm, what? I am pretty sure you are in the wrong post.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • load more comments (-1 replies)