Hello! I have just recently joined the Kubuntu environment by installing 22.04 LTS onto a brand new build and am going through the motions to make it my personal computer. However, I've run into an strange problem that I have been unable to find a solution to on this forum or on the wider internet.
Problem
I started with a fresh install of Kubuntu 22.04 LTS, with the most notable option during installation being to include third party drivers. Since then, I have been unable to see the Login greeter whenever I turn my computer on. I see my BIOS screen, followed by a booting screen whilst background processes get ready. My screen just hangs around on the booting screen until about a minute later when I get a single error message that says the following:
After that, no matter how long I wait, the login greeter to prompt for my username and password will never appear.
Current Workaround
I am able to switch terminals after a certain point of Plymouth being active using Ctrl + Alt + F2. Once I do that I see the command line login which, upon entering the details, sends me into bash. From there, I use "startx" to load up the desktop environment and everything works smoothly after that.
Interestingly, I can switch back to the original terminal (Ctrl + Alt + F1) and either see a blank output with an underscore flashing in the top-left or the "hdaudio" error described before (if it was displayed in that terminal).
Auxiliary Information
I have taken a quick, uninformed browse at the output of "journalctl -b", but I have not found much that has assisted with diagnosis. My initial thought was that "sddm" (which I assume handles the login greeter) was failing, but "journalctl -b | grep -e 'sddm' -e 'Simple'" seems to imply otherwise:
From what I can see of the rest of the journalctl output, nothing is particularly out of the ordinary; it is as if it should be appearing, but nothing happens. But if any more details are required, I am happy to put up some more.
Of note in my PC build is the fact that I have no graphics card installed. Instead, I am using the integrated graphics on my Intel Core i5-13600K (Intel UHD Graphics 770). I thought this might have had an impact such as "nomodeset" being erroneously enabled, but I do not see any evidence of this in journalctl. As such, I assume it is using this graphics card without issue.
What have I done so far?
Initially, I experienced this problem after I installed Kubuntu 22.04 without third party plugins. Shortly after some investigation and experimentation, I did a fresh install over the top of the same drive, this time with the third party plugins. Both times I experienced similar symptoms with the login greeter. The former installation did cause "nomodeset" to be enabled in GRUB, but this is no longer an issue.
I have ensured that all updates on Kubuntu are accounted for. This includes updates via Discover and via APT ("update" and "upgrade", I do not believe I have done "dist-upgrade"). This fixed a previous issue where the phrase "mtd device must be supplied (device name is empty)" would appear alongside the previous "hdaudio" error, but otherwise results in similar symptoms.
I tried following some steps as listed in this Reddit post which described similar symptoms, but still had a similar experience to when I started. Specifically, I did the following:
Even after a reboot, I still experienced the same symptoms.
I have attempted using "sudo service restart sddm" to restart SDDM in the second terminal, but this had no effect on tty1.
"sudo telinit 3" did switch tty1 to the command-line login from the previously uninteractive screen, but otherwise just left me with the workaround I already had.
I have started up with the "quiet splash" removed from GRUB and get logs which appear similar to those of journalctl's. However, it will get to a similar point (including logging the "hdaudio" error) and stop logging messages, requiring me to use the same workaround.
Summary
Currently, the login greeter does not appear when booting up and I cannot find a clear indication of something going wrong with SDDM which I believe should handle this process.
Updates
Problem
I started with a fresh install of Kubuntu 22.04 LTS, with the most notable option during installation being to include third party drivers. Since then, I have been unable to see the Login greeter whenever I turn my computer on. I see my BIOS screen, followed by a booting screen whilst background processes get ready. My screen just hangs around on the booting screen until about a minute later when I get a single error message that says the following:
Code:
hdaudio hdaudioC0D2: Unable to configure, disabling
Current Workaround
I am able to switch terminals after a certain point of Plymouth being active using Ctrl + Alt + F2. Once I do that I see the command line login which, upon entering the details, sends me into bash. From there, I use "startx" to load up the desktop environment and everything works smoothly after that.
Interestingly, I can switch back to the original terminal (Ctrl + Alt + F1) and either see a blank output with an underscore flashing in the top-left or the "hdaudio" error described before (if it was displayed in that terminal).
Auxiliary Information
I have taken a quick, uninformed browse at the output of "journalctl -b", but I have not found much that has assisted with diagnosis. My initial thought was that "sddm" (which I assume handles the login greeter) was failing, but "journalctl -b | grep -e 'sddm' -e 'Simple'" seems to imply otherwise:
Code:
Dec 24 15:02:07 MYPC systemd[1]: Starting Simple Desktop Display Manager... Dec 24 15:02:07 MYPC systemd[1]: Started Simple Desktop Display Manager. Dec 24 15:02:07 MYPC sddm[972]: Initializing... Dec 24 15:02:07 MYPC sddm[972]: Starting... Dec 24 15:02:07 MYPC sddm[972]: Logind interface found
Of note in my PC build is the fact that I have no graphics card installed. Instead, I am using the integrated graphics on my Intel Core i5-13600K (Intel UHD Graphics 770). I thought this might have had an impact such as "nomodeset" being erroneously enabled, but I do not see any evidence of this in journalctl. As such, I assume it is using this graphics card without issue.
What have I done so far?
Initially, I experienced this problem after I installed Kubuntu 22.04 without third party plugins. Shortly after some investigation and experimentation, I did a fresh install over the top of the same drive, this time with the third party plugins. Both times I experienced similar symptoms with the login greeter. The former installation did cause "nomodeset" to be enabled in GRUB, but this is no longer an issue.
I have ensured that all updates on Kubuntu are accounted for. This includes updates via Discover and via APT ("update" and "upgrade", I do not believe I have done "dist-upgrade"). This fixed a previous issue where the phrase "mtd device must be supplied (device name is empty)" would appear alongside the previous "hdaudio" error, but otherwise results in similar symptoms.
I tried following some steps as listed in this Reddit post which described similar symptoms, but still had a similar experience to when I started. Specifically, I did the following:
Code:
sudo apt update
sudo apt full-upgrade
# 0 to upgrade
sudo apt --fix-missing install && sudo apt --fix-broken install
# Nothing happened
sudo apt install --reinstall --install-recommends sddm
sudo apt install --reinstall --install-recommends kde-config-sddm
sudo dpkg-reconfigure sddm
sudo dpkg-reconfigure kde-config-sddm
sudo apt install --reinstall --install-recommends openbox-kde-session
sudo apt install --reinstall --install-recommends obconf-qt
I have attempted using "sudo service restart sddm" to restart SDDM in the second terminal, but this had no effect on tty1.
"sudo telinit 3" did switch tty1 to the command-line login from the previously uninteractive screen, but otherwise just left me with the workaround I already had.
I have started up with the "quiet splash" removed from GRUB and get logs which appear similar to those of journalctl's. However, it will get to a similar point (including logging the "hdaudio" error) and stop logging messages, requiring me to use the same workaround.
Summary
Currently, the login greeter does not appear when booting up and I cannot find a clear indication of something going wrong with SDDM which I believe should handle this process.
- Is there anything amiss that I should be aware of?
- What other avenues are there to diagnose or debug this situation?
- What should I expect to happen from the login process (both in the UI and in journalctl)?
Updates
- 2022-12-25: Added in the fact I have done a fresh installation previously as an attempt to resolve the issue.
Comment