Arch Linux

micsnare

Member

Registered: 2013-08-25

Posts: 57

[SOLVED] Unable to login due to problems with SDDM and Xorg

Dear archers,

I was told to create a new thread, although my problem seem to be pretty similar to this thread:
https://bbs.archlinux.org/viewtopic.php?id=253614

After an update, last week (didn’t have much time to look into this issue then) I’m unable to login into my arch over SDDM anymore.
Although the sddm process is running, it seems to me it’s more of a problem with the xorg server.

I can login to my system over the various TTYs, I just don’t get my plasma loaded.

I’ve collected the following logs that I seemed to be useful......

the output of the sddm.log
http://ix.io/2gHG

the ouput of the systemctl status sddm
http://ix.io/2gHI

the output of the Xorg.0.log
http://ix.io/2gHH

An interesting fact is that if I run “echo $DISPLAY” it returns nothing.....just a blank line, so it seems that the display variable is not set. Is this normal?

Also, I’ve tried running the command “/usr/bin/startplasma-x11” and it returns:
$DISPLAY is not set or cannot connect to the X server.

Does anyone have any clue or suggestion what the cause is and how to fix it?
If you need any more log output, then please let me know, and I will try to upload it. Thanks!

I’m pretty desperate at the moment

thanks a lot,
theresa

Last edited by micsnare (2020-04-05 16:34:39)

micsnare

Member

Registered: 2013-08-25

Posts: 57

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

Btw, please don’t bash me.... I’ve done lots of googling before even coming here. But it seems the threads I’ve found are all very very old, or the recommended solutions do not work for me.

From my understanding you don’t need an .xinitrc if you’re using SDDM, is this correct? At least I haven’t had one before this all happened.

It seems I cannot find anything on the error code that I see in the systemctl output of the sddm service
“Auth: sddm-helper exited with 11”

I find information on any other error code, but not 11.

EDIT: I currently don’t have any *.lock files in ~./.config or ~./.cache

Last edited by micsnare (2020-04-05 07:33:57)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,657

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

You have some kind of xorg config, what are their contents?  And post a complete journal from reproduction of the issue

sudo journalctl -b

FWIW Nothing about $DISPLAY not being set is surprising, if you are on a TTY and hence not a graphical session $DISPLAY won't be set. That variable is set by xorg when it has started up.

micsnare

Member

Registered: 2013-08-25

Posts: 57

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

Dear V1del,

thanks for getting back to me so quickly and for your answers. What you said about $DISPLAY not being set makes total sense, d’oh I should have thought of this before. Silly me!

As for the xorg config that I have configured, please find the link below:
# 20-intel.conf
http://ix.io/2gIQ

# 30-touchpad.conf
http://ix.io/2gIR

# xinitrc
http://ix.io/jmE

As for the journald output, please find it here:
http://ix.io/2gIS

Thanks a lot for your help and your fast response. I really hope I can get this working again with your help!

All the best,
theresa

micsnare

Member

Registered: 2013-08-25

Posts: 57

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

interestingly enough, it seems to work when I simply type “startx” when I’m in one of the tty shells.

any idea?

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

Weird, the post I made suggesting a new thread included instructions to get journal output. Why did you add it only after being asked the 2nd time (by videl) ?

journal output makes clear you don't have microcde loading configured, please do that , see https://wiki.archlinux.org/index.php/Microcode , reboot and
post fresh journal .

Some other comments

Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: Machine check events logged
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: TSC 0 ADDR fef1cf00 MISC 3880018086 
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1586085873 SOCKET 0 APIC 0 microcode 30
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: Machine check events logged
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff00 MISC 43880018086 
Apr 05 13:24:36 herex kernel: mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1586085873 SOCKET 0 APIC 0 microcode 30

not good, but only occurs once in the log.

Apr 05 13:24:36 herex kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1], AE_NOT_FOUND (20190816/dswload2-159)
Apr 05 13:24:36 herex kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Apr 05 13:24:36 herex kernel: ACPI: Skipping parse of AML opcode: Scope (0x0010)

Could be harmless

The 20-intel.conf looks very standard, maybe you don't want to use DRI 3 for some reason ?

The .xinitrc looks fine.

Last edited by Lone_Wolf (2020-04-05 13:57:22)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

ralvez

Member

From: Canada

Registered: 2005-12-06

Posts: 1,694

Website

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

Yup, I have the same problem as of today.
I cannot find the root problem, to be honest, but I'll keep trying and post if I find something that helps.
In my case "startx" returns "command not found" though ... ???

R.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,657

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

You have an evdi device that is going absolutely crazy, do you intentionally use that resp do you actively use a displaylink device?

Why do you explicitly use DRI2 ? I assume that to be one of the main reasons for the actual issue. If you have an actually valid reason for explicitly using that please elaborate on why you are using that.

That much about surrounding system level weirdness that should be ironed out, Your actual issue that leads to things "not working" is the following:

Apr 05 13:24:45 herex kernel: QSGRenderThread[936]: segfault at 24 ip 00007f20df4807be sp 00007f20c8aeb4a0 error 6 in iris_dri.so[7f20de9df000+dba000]
Apr 05 13:24:45 herex kernel: Code: 7e 30 44 01 ff 81 ff ff ff 00 00 0f 87 b3 17 00 00 49 01 c7 4c 89 7e 38 48 85 c0 0f 84 24 02 00 00 83 ea 01 81 ca 00 00 09 78 <89> 10 48 8d 50 04 45 85 ed 74 74 41 8d 75 ff 48 8d 74 f0 0c 66 0f
Apr 05 13:24:45 herex kernel: audit: type=1701 audit(1586085885.649:44): auid=4294967295 uid=977 gid=977 ses=4294967295 pid=783 comm="QSGRenderThread" exe="/usr/bin/sddm-greeter" sig=11 res=1

so you get a crash in the new intel graphics driver, which I'd suspect to be normal as I'd assume that it being new it will not work anymore in a DRI2 context (which is why I'm asking that second question)

You might also want to post more information about that coredump: https://wiki.archlinux.org/index.php/Co … _core_dump

From the information we have so far, my suggestion in order of being more future proof with modern developments would be:

1. Regardless of any of this, follow lone_wolf's advice and set up your microcodes

2. Remove that 20-intel.conf and xf86-video-intel (xf86-video-intel is generally in development limbo and largely considered deprecated for chips as new as yours, and especially on KDE there a a wide array of known issues with it which never got fixed)

3. If you can't do that due to actual systemic necessity with the evdi driver (that does in so far not make sense as the xorg log shows that the evdi driver tries modesetting either way and doesn't care about your intel config and I still think you should not rely on xf86-video-intel regardless) or because it didn't help sufficiently - switch the mesa implementation to use the older OpenGL driver: https://wiki.archlinux.org/index.php/In … ver_(i965)

@ralvez look through the mentioned logs for similar messages as identified here and post the logs asked for here should the course of action not become apparent. FWIW startx is part of xorg-xinit.

Last edited by V1del (2020-04-05 15:37:59)

micsnare

Member

Registered: 2013-08-25

Posts: 57

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

Good news, I have finally fixed the problem and found out what the root cause was.
It seems the last arch-update didn't like my existing xorg config

@V1del as you have rightly suggested it seemed using DRI2 with my intel driver seemed to be the main issue why SDDM couldn't properly load anymore.

Yes, I do actively use displaylink-manager to access my dockingstation/port-replicator (otherwise there would be no sense in using it/having it installed) to access external monitors, et cetera.

I have now changed enabled the config again and changed it to using DRI 3

Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "DRI" "3"             # DRI3 is now default 
      EndSection


Section "Screen"
Identifier "My Screen"
Device "Intel"
EndSection 

To be honest, I would have never guessed this to be the problem. So, thanks V1del and Lone_Wolf for helping troubleshoot this.

I can tell you it's a nightmare trying to troubleshoot something only on your mobile device, unfortunately I don't have a 2nd laptop or desktop.

I'm aware that the evdi-device is going crazy, unfortunately it doesn't work as well with the displaylink driver......this has been a nightmare to troubleshoot in the past as well. But once it's working, it does the job.

The two coredumps were only caused by me starting systemsettings5....however, this is fixed, when using DRI 3. No more coredumps

@Lone_Wolf thanks very much! I will now look into setting up microcode loading.

Again, THANKS everyone for helping out and getting this fixed. I think I've learned a lot, and next time I'll be smarter and hopefully can fix similar issues myself.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,657

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

I'd still highly reccommend to not use xf86-video-intel at all, it has many weird quirks regardless of configuration, but if you have a reason for keeping it and this fix is sufficient, then you do you.

Last edited by V1del (2020-04-05 16:46:34)

micsnare

Member

Registered: 2013-08-25

Posts: 57

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

@V1del quite frankly you’re right, the xf86-video-intel driver is not ideal, and I will definitely get rid of it and replace it with the mesa opengl driver.
however, since i heavily rely on the evdi/displaylink driver as well, i will probably look into this in the summer as I currently have to focus on a lot of exams and assignments at uni....because i don’t know what the side-effects and dependencies will be when i switch to mesa.

rnp

Member

From: Munich, Germany

Registered: 2013-05-06

Posts: 4

Re: [SOLVED] Unable to login due to problems with SDDM and Xorg

To confirm V1del's recommendations:  I had a very similar problem described initially by @micsnare, and by removing the package xf86-video-intel and related configuration file(s), it was solved. In my case, I had the intel microcode already installed.