Announcement

Collapse
No announcement yet.

SDDM Black Screen but ?Working Somewhat

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SDDM Black Screen but ?Working Somewhat

    Hello all,

    This is my first time posting on the Kubuntu forums, as I just recently made a long-awaited transition to the wonderful world of KDE

    I recently bought a System76 Oryx Pro V4, which came pre-installed with Pop!_OS. After purchasing the laptop, which came pre-installed with a 256 GB SSD, I added a 2 TB Seagate FireCuda SSHD (hybrid SSD + HDD) to expand the storage. After this, I wiped Pop and installed Kubuntu 18.04 on the system. Following the instructions at https://askubuntu.com/questions/1034...drives-ssd-hdd, I moved the home folder to the 2nd drive (the FireCuda). This process completed successfully, and after some NVIDIA driver updates was able to reboot without issue. So I was left with an intact system that was booting 2 full disk encrypted hard drives.

    However, after updating my kernel version from 4.15.0-20 to 4.15.0-32, after unlocking the disk at the initial prompt, the session booted to a black screen without any visual information (including cursor). I could still switch to the other TTY's, and could manually login and run startx from there - successfully reaching my desktop without issues. If I use "Advanced Options" in the GRUB menu to bot into the old kernel version, I can unlock the disk and am presented with the normal login GUI. This continues to happen after the upgrade to kernel version 4.15.0-33.

    On a hunch I tried typing in my password at the black screen and pressing enter (same thing I do when the login GUI is shown). Much to my surprise, the system successfully logged in, displaying the KDE logo on a black background as usual before successfully starting the desktop. This makes me believe that the source of the problem is SDDM. It appears that SDDM is running (confirmed when I switch to another TTY and run top, which shows the sddm process running) but not displaying any graphical information. I have tried purge uninstalling and reinstalling sddm/NVIDIA drivers, booting with nomodeset enabled, and deleting the .Xauthority file. I have no issue accessing my home folder on the 2nd drive. There is no config file to edit in /etc or /usr/lib/sddm, and the file in /var/log/sddm.log is empty. I have tried looking up all the help articles I can find with no avail. This is my SDDM SOS - I need your help!

    System information:
    • Make/Model: System76 Oryx Pro laptop (4th generation)
    • CPU: Intel i7-8750H 4.1 GHz
    • GPU: NVIDIA GTX 1060/ Intel integrated graphics
    • RAM: 16 GB
    • Internal Drives: 256 GB M.2 SSD (manufacturer) + 2 TB Seagate FireCuda SSHD
    • OS: Kubuntu 18.04.1
    • KDE Plasma Version: 5.12.6
    • Grub Version: 2.02-2ubuntu8.3
    • SDDM Package Version: 0.17.0-1ubuntu7
    • NVIDIA Package Version (from System76 PPA): 396.24-0ubuntu1~pop1

    #2
    Originally posted by tbirdc1212 View Post
    ... believe that the source of the problem is SDDM ... /var/log/sddm.log is empty...
    On my 18.04, SDDM logs into syslog. I last booted on Saturday, so the SDDM entries have been aged to /var/log/syslog.3.gz. If you are in the adm group*, you can read the files, otherwise I suggest copying them somewhere with sudo and making them readable with chmod. Then I suggest:
    Code:
    grep SDDM syslog{,.1}
    zgrep SDDM syslog.*.gz
    You might see something, but maybe SDDM is oblivious to the problem. If you want to see the SDDM log entries in the log context, kate or gvim can open the .gz files; gvim gave me syntax highlighting without asking.

    * in konsole, the groups command will tell you
    Regards, John Little

    Comment


      #3
      Thank you for your quick reply jlittle! In the syslog files you mentioned, I searched for SDDM. From the log output, SDDM appears to be starting with each boot and performing the early initializing steps without issue. The only errors that I noticed for the process are included below:

      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: Connected to the daemon.
      Aug 26 16:58:10 [username]-OryxPro sddm[1047]: Message received from greeter: Connect
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffc98c7d1b0), parent's thread is QThread(0x558a7b1cf8c0), current thread is QThread(0x558a7b236520)
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: message repeated 3 times: [ QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffc98c7d1b0), parent's thread is QThread(0x558a7b1cf8c0), current thread is QThread(0x558a7b236520)]
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffc98c7d1b0), parent's thread is QThread(0x558a7b1cf8c0), current thread is QThread(0x558a7b236520)
      Aug 26 16:58:10 [username]-OryxPro dbus-daemon[1088]: [session uid=118 pid=1086] AppArmor D-Bus mediation is enabled
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffc98c7d1b0), parent's thread is QThread(0x558a7b1cf8c0), current thread is QThread(0x558a7b236520)
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
      Aug 26 16:58:10 [username]-OryxPro sddm-greeter[1080]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"

      These seem to be fairly generic errors, so I'm not entirely sure where to go from here. Any suggestions on how to further diagnose would be greatly appreciated!

      Comment


        #4
        Originally posted by tbirdc1212 View Post
        These seem to be fairly generic errors
        Yes, my logs have them. Here are all the SDDM lines from my logs:
        Code:
        Aug 25 18:28:00 myriam sddm[1175]: Initializing...
        Aug 25 18:28:00 myriam sddm[1175]: Logind interface found
        Aug 25 18:28:00 myriam sddm[1175]: Starting...
        Aug 25 18:28:00 myriam sddm[1175]: Adding new display on vt 1 ...
        Aug 25 18:28:00 myriam sddm[1175]: Loading theme configuration from ""
        Aug 25 18:28:00 myriam sddm[1175]: Display server starting...
        Aug 25 18:28:00 myriam sddm[1175]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{865825ea-a05e-4bc8-8ba7-756a2d075211} -background none -noreset -displayfd 18 -seat seat0 vt1
        Aug 25 18:28:01 myriam sddm[1175]: Setting default cursor
        Aug 25 18:28:01 myriam sddm[1175]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
        Aug 25 18:28:01 myriam sddm[1175]: Display server started.
        Aug 25 18:28:01 myriam sddm[1175]: Socket server starting...
        Aug 25 18:28:01 myriam sddm[1175]: Socket server started.
        Aug 25 18:28:01 myriam sddm[1175]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
        Aug 25 18:28:01 myriam sddm[1175]: Greeter starting...
        Aug 25 18:28:01 myriam sddm[1175]: Adding cookie to "/var/run/sddm/{865825ea-a05e-4bc8-8ba7-756a2d075211}"
        Aug 25 18:28:01 myriam sddm-helper[1451]: [PAM] Starting...
        Aug 25 18:28:01 myriam sddm-helper[1451]: [PAM] Authenticating...
        Aug 25 18:28:01 myriam sddm-helper[1451]: [PAM] returning.
        Aug 25 18:28:01 myriam systemd[1]: Created slice User Slice of sddm.
        Aug 25 18:28:01 myriam systemd[1]: Started Session 1 of user sddm.
        Aug 25 18:28:01 myriam sddm[1175]: Greeter session started successfully
        Aug 25 18:28:01 myriam sddm-greeter[1466]: High-DPI autoscaling not Enabled
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Reading from "/usr/share/xsessions/plasma.desktop"
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Connected to the daemon.
        Aug 25 18:28:01 myriam sddm[1175]: Message received from greeter: Connect
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
        Aug 25 18:28:01 myriam sddm-greeter[1466]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffd7e7cb870), parent's thread is QThread(0x55ba1fb768a0), current thread is QThread(0x55ba1fca4f90)
        Aug 25 18:28:01 myriam sddm-greeter[1466]: message repeated 3 times: [ QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffd7e7cb870), parent's thread is QThread(0x55ba1fb768a0), current thread is QThread(0x55ba1fca4f90)]
        Aug 25 18:28:01 myriam sddm-greeter[1466]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
        Aug 25 18:28:01 myriam sddm-greeter[1466]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffd7e7cb870), parent's thread is QThread(0x55ba1fb768a0), current thread is QThread(0x55ba1fca4f90)
        Aug 25 18:28:01 myriam sddm-greeter[1466]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is SDDM::GreeterApp(0x7ffd7e7cb870), parent's thread is QThread(0x55ba1fb768a0), current thread is QThread(0x55ba1fca4f90)
        Aug 25 18:28:01 myriam sddm-greeter[1466]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"
        Aug 25 18:28:01 myriam dbus-daemon[801]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.31' (uid=118 pid=1466 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-nhFdzy" label="unconfined")
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Adding view for "HDMI-2" QRect(0,0 1920x1080)
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Message received from daemon: Capabilities
        Aug 25 18:28:01 myriam sddm-greeter[1466]: Message received from daemon: HostName
        Aug 25 18:28:24 myriam sddm-greeter[1466]: Time engine Clock skew signaled
        Aug 25 18:28:50 myriam sddm-greeter[1466]: Reading from "/usr/share/xsessions/plasma.desktop"
        Aug 25 18:28:50 myriam sddm[1175]: Message received from greeter: Login
        Aug 25 18:28:50 myriam sddm[1175]: Reading from "/usr/share/xsessions/plasma.desktop"
        Aug 25 18:28:50 myriam sddm[1175]: Reading from "/usr/share/xsessions/plasma.desktop"
        Aug 25 18:28:50 myriam sddm[1175]: Session "plasma.desktop" selected, command: "/usr/bin/startkde"
        Aug 25 18:28:50 myriam sddm-helper[1532]: [PAM] Starting...
        Aug 25 18:28:50 myriam sddm-helper[1532]: [PAM] Authenticating...
        Aug 25 18:28:50 myriam sddm-helper[1532]: [PAM] Preparing to converse...
        Aug 25 18:28:50 myriam sddm-helper[1532]: [PAM] Conversation with 1 messages
        Aug 25 18:28:50 myriam sddm-helper[1532]: [PAM] returning.
        Aug 25 18:28:50 myriam sddm[1175]: Authenticated successfully
        Aug 25 18:28:50 myriam sddm-greeter[1466]: Message received from daemon: LoginSucceeded
        Aug 25 18:28:50 myriam sddm-greeter[1466]: qrc:///QtQuick/VirtualKeyboard/content/components/SelectionControl.qml:80: TypeError: Cannot read property 'cursorRectIntersectsClipRect' of null
        Aug 25 18:28:50 myriam sddm-greeter[1466]: qrc:///QtQuick/VirtualKeyboard/content/components/SelectionControl.qml:48: TypeError: Cannot read property 'anchorRectIntersectsClipRect' of null
        Aug 25 18:28:50 myriam sddm-helper[1451]: [PAM] Closing session
        Aug 25 18:28:50 myriam sddm-helper[1451]: [PAM] Ended.
        Aug 25 18:28:50 myriam sddm[1175]: Auth: sddm-helper exited successfully
        Aug 25 18:28:50 myriam sddm[1175]: Greeter stopped.
        Aug 25 18:28:50 myriam sddm-helper[1532]: Starting: "/etc/sddm/Xsession \"/usr/bin/startkde\""
        Aug 25 18:28:50 myriam sddm-helper[1555]: Adding cookie to "/home/john/.Xauthority"
        Aug 25 18:28:50 myriam systemd[1]: Removed slice User Slice of sddm.
        Aug 25 18:28:50 myriam sddm[1175]: Session started
        Aug 25 18:28:52 myriam sddm[1175]: Checking for pam module
        Aug 25 18:28:52 myriam sddm[1175]: Got pam-login
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd: Waiting for hash on 15-
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd: waitingForEnvironment on: 3
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd: client connected
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd: client disconnected
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: Checking for pam module
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: Got pam-login param
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: Waiting for hash on 15-
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: waitingForEnvironment on: 3
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: client connected
        Aug 25 18:28:52 myriam sddm[1175]: kwalletd5: client disconnected
        Regards, John Little

        Comment


          #5
          Originally posted by tbirdc1212 View Post

          System information:
          • .
            .
          • GPU: NVIDIA GTX 1060/ Intel integrated graphics
            .
            .
            .
          • NVIDIA Package Version (from System76 PPA): 396.24-0ubuntu1~pop1
          That Nvidia hardware may require the "nomodeset" kernel boot option.

          Comment

          Working...
          X