At first Instead of my SDDM I would just see an after image of what was last displayed on screen. But if I typed in my password and pressed enter, it would let me in just fine. Then after following some suggestions from users in r/Kubuntu I’ve made a bit of progress. Now when I boot up my computer instead of the SDDM being invisible, it now doesn’t load at all, from there I switch to tty3 then back to tty2 and then log in through the terminal. After that I run startplasma-wayland and then I have access to my desktop. The post where all this went down - https://www.reddit.com/r/Kubuntu/comments/1nvreuo/sddm_not_rendering/

Does anyone know a fix? I would like to be able to see my login screen.

Here’s my specs in case that would help - https://i.imgur.com/XtC43zw.png

And here’s my journalctl output after booting and launching plasma - https://pastebin.com/nnGsWebd

  • A_norny_mousse@feddit.org
    3·
    2 days ago

    Your journal output might be too curated, I don’t see anything that would keep the display manager from starting up.

    Then after following some suggestions from users in r/Kubuntu I’ve made a bit of progress.

    We’d need more info on this, like what exactly did you change and what was that progress and how/when did it turn into regress.

    Journal output for SDDM and related services, and for the relevant timeframe, would be better.

    I suppose SDDM is the default for Kubuntu, and if you had done other possibly relevant things to your setup you’d have told us.

    FWIW, it could be GPU related, but that really just is a wild guess.

    PS: identical post here: https://lemmy.sdf.org/post/43982607

    • Successful_Try543@feddit.org
      2·
      2 days ago

      Your journal output might be too curated, I don’t see anything that would keep the display manager from starting up.

      The only suspicious entry I’ve found was #185:

      sddm[1596]: Failed to read display number from pipe

      FWIW, it could be GPU related, but that really just is a wild guess.

      Skimming search results onto the above error message seems to second your idea.

        • RubberDuckyDJ@lemmy.sdf.orgOP
          1·
          2 days ago

          The issue is I have no idea what any of these errors mean. I’m pretty new to desktop Linux so I’ve just been researching the errors one by one but so far, no dice.

          • A_norny_mousse@feddit.org
            2·
            2 days ago

            Show us! The journalctl output was too restricted, we need to see all of it - at least for the significant timeframe.

              • A_norny_mousse@feddit.org
                1·
                9 hours ago

                Not downloading and reading 181MB of logs. You probably used journalctl without any qualifiers, right?

                What we want is

                1. The current boot showed the erroneous behavior
                2. Make note of the timeframe the erroneous behavior occured

                Compose a journalctl command that takes these aspects into account, i.e.:

                journalctl --boot --since <date_time> --until <date_time>

                Also see:

                -S, --since=, -U, --until=
   Start showing entries on or newer than the specified date, or on
   or older than the specified date, respectively. Date
   specifications should be of the format "2012-10-30 18:17:16". If
   the time part is omitted, "00:00:00" is assumed. If only the
   seconds component is omitted, ":00" is assumed. If the date
   component is omitted, the current day is assumed. Alternatively
   the strings "yesterday", "today", "tomorrow" are understood,
   which refer to 00:00:00 of the day before the current day, the
   current day, or the day after the current day, respectively.
   "now" refers to the current time. Finally, relative times may be
   specified, prefixed with "-" or "+", referring to times before or
   after the current time, respectively. For complete time and date
   specification, see systemd.time(7). Note that --output=short-full
   prints timestamps that follow precisely this format.

                Assuming 1. and 2. are in effect, you can also try this:

                systemctl status -n999 sddm