You are not logged in.

#1 2017-11-14 17:29:58

rakeshdas
Member
Registered: 2016-01-20
Posts: 11

SDDM won't start, stuck on "Reached target Graphical Interface"

When I attempted to boot my computer this morning, it got stuck on 

[ OK ] Reached target Graphical Interface 

For my graphical interface, I use KDE plasma with SDDM as the login/display manager. When I say stuck, I really mean stuck, I have read other people on the forums with this same issue who have solved it by pressing enter and ctrl+alt+f2 to switch into another tty to fix up the issue, I can't even do that. Although, the terminal cursor on the bottom of my screen blinks very quickly.

So I created an Arch installation USB and booted into the USB, chrooting into my existing Arch installation. after I ran journalctl, I found this error:

 QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.

I searched around on the forums and saw that someone else had this issue as well and they had an Nvidia graphics card, which I also do have and their solution was to reinstall the

nvidia

package. I did so in my chrooted environment and did the proper configurations, outlined here, but no dice. I still get stuck on the same message.

So, does anyone have any other suggestions on how might be able to get my computer to boot?

Last edited by rakeshdas (2017-11-14 18:26:05)

Offline

#2 2017-11-14 17:33:59

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

Please elaborate on what you mean by "get my computer to boot"
You could stop sddm by using Systemd#Change_default_target_to_boot_into to boot to multi-uer.target so sddm would not start.
Then disable sddm.

Offline

#3 2017-11-14 18:02:53

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

Please edit your thread title to reflect the fact that you can boot, you just can't start your graphical environment.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2017-11-14 18:26:27

rakeshdas
Member
Registered: 2016-01-20
Posts: 11

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

jasonwryan wrote:

Please edit your thread title to reflect the fact that you can boot, you just can't start your graphical environment.

Done smile

Offline

#5 2017-11-14 18:27:37

rakeshdas
Member
Registered: 2016-01-20
Posts: 11

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

loqs wrote:

Please elaborate on what you mean by "get my computer to boot"
You could stop sddm by using Systemd#Change_default_target_to_boot_into to boot to multi-uer.target so sddm would not start.
Then disable sddm.

Alright, wouldn't I need a display manager like SDDM to boot into KDE though?

Offline

#6 2017-11-14 18:38:26

dawja
Member
From: New England
Registered: 2014-09-20
Posts: 30

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

Do you have other DMs and WMs that you can try to use to see if it works?

Offline

#7 2017-11-14 18:42:14

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

You don't need a display manager for anything.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#8 2017-11-14 18:49:02

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: SDDM won't start, stuck on "Reached target Graphical Interface"

rakeshdas wrote:

Alright, wouldn't I need a display manager like SDDM to boot into KDE though?

KDE#From_the_console
If you wish the issue with SDDM to be resolved please supply all the information from the journal related to SDDM from a boot where the service fails.
Also what changed since SDDM last started successfully? (package updates / configuration changes)

Offline

Board footer

Powered by FluxBB