No graphical interface after upgrading sddm from 0.15.0-1 to 0.16.0-1

sddm
intel

(Johannes Eibensteiner) #32

Thanks a lot for posting this issue, I got the update some days ago together with the new xorg…
I’ve spent hours searching the error in xorg after I had no graphical interface and suspected the intel driver causing the issue…
Now I found out that downgrading sddm solved the problem :slight_smile:
Thanks for that, I wouldn’t have thougt about this!!


(kepszlok) #33

Any news in this sddm topic? I still don’t know what coud be wrong…


(Neofytos Kolokotronis) #34

Am not exactly sure if it is related, but I had an ugly black screen issue on testing today that after a lot of frustration I managed to workaround. Maybe something similar helps here?

While looking around the net for advice, some people recommended deleting sddm cache (hidden folder) also:

$ sudo rm -r /var/lib/sddm/*

(kepszlok) #35

None of those worked for me. Sadly.


(Neofytos Kolokotronis) #36

:slightly_frowning_face: Just to be sure, I rebooted after enabling autologin.

Btw, make sure you run journalctl for the PID with sudo to get proper output for sddm. Mine mentioned “sddm-helper exit with 7”.


(kepszlok) #37

Exactly how? What’s the command you are running?


(Neofytos Kolokotronis) #38

You get the PID (in my case 889) by running

[tetris4@lappy ~]$ systemctl status sddm
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-11-27 10:46:00 CET; 24min ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
 Main PID: 889 (sddm)
    Tasks: 7 (limit: 4915)
   CGroup: /system.slice/sddm.service
           ├─889 /usr/bin/sddm
           └─907 /usr/lib/xorg-server/Xorg -nolisten tcp -auth /var/run/sddm/{413de687-f49b-488a-a731-e9a05c4886fa} -background none -noreset -displayfd 18 -seat seat0 vt7

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

You then use this with journalctl to get the complete output. Remember to use sudo:

[tetris4@lappy ~]$ sudo journalctl _PID=889
-- Logs begin at Sun 2017-11-26 18:23:36 CET, end at Mon 2017-11-27 11:12:03 CET. --
Nov 27 10:46:02 lappy sddm[889]: Initializing...
Nov 27 10:46:02 lappy sddm[889]: Logind interface found
Nov 27 10:46:02 lappy sddm[889]: Starting...
Nov 27 10:46:02 lappy sddm[889]: Adding new display on vt 7 ...
Nov 27 10:46:02 lappy sddm[889]: Loading theme configuration from ""
Nov 27 10:46:02 lappy sddm[889]: Display server starting...
Nov 27 10:46:02 lappy sddm[889]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{413de687-f49b-488a-a731-e9a05c4886fa} -background none -noreset -displayfd 18 -seat seat0 vt7
Nov 27 10:46:06 lappy sddm[889]: Setting default cursor
Nov 27 10:46:06 lappy sddm[889]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Nov 27 10:46:06 lappy sddm[889]: Display server started.
Nov 27 10:46:06 lappy sddm[889]: Socket server starting...
Nov 27 10:46:06 lappy sddm[889]: Socket server started.
Nov 27 10:46:06 lappy sddm[889]: Loading theme configuration from "/usr/share/sddm/themes/heritage/theme.conf"
Nov 27 10:46:06 lappy sddm[889]: Greeter starting...
Nov 27 10:46:06 lappy sddm[889]: Adding cookie to "/var/run/sddm/{413de687-f49b-488a-a731-e9a05c4886fa}"
Nov 27 10:46:07 lappy sddm[889]: Greeter session started successfully
Nov 27 10:46:08 lappy sddm[889]: Message received from greeter: Connect
Nov 27 10:46:30 lappy sddm[889]: Message received from greeter: Login
Nov 27 10:46:30 lappy sddm[889]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 27 10:46:30 lappy sddm[889]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 27 10:46:30 lappy sddm[889]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
Nov 27 10:46:30 lappy sddm[889]: Authenticated successfully
Nov 27 10:46:31 lappy sddm[889]: Auth: sddm-helper exited successfully
Nov 27 10:46:31 lappy sddm[889]: Greeter stopped.
Nov 27 10:46:31 lappy sddm[889]: Session started

This above is the normal output of course. In my case, when sddm was failing I got:

-- Logs begin at Sun 2017-11-26 10:35:05 CET, end at Sun 2017-11-26 12:49:23 CET. --
Nov 26 12:45:22 lappy sddm[836]: Initializing...
Nov 26 12:45:22 lappy sddm[836]: Logind interface found
Nov 26 12:45:22 lappy sddm[836]: Starting...
Nov 26 12:45:22 lappy sddm[836]: Adding new display on vt 7 ...
Nov 26 12:45:22 lappy sddm[836]: Loading theme configuration from ""
Nov 26 12:45:22 lappy sddm[836]: Display server starting...
Nov 26 12:45:22 lappy sddm[836]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{a7a09388-4472-4380-8eeb-2a7819ca699b} -background none -noreset -displayfd 18 -seat seat0 vt7
Nov 26 12:45:26 lappy sddm[836]: Setting default cursor
Nov 26 12:45:26 lappy sddm[836]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Nov 26 12:45:26 lappy sddm[836]: Display server started.
Nov 26 12:45:26 lappy sddm[836]: Socket server starting...
Nov 26 12:45:26 lappy sddm[836]: Socket server started.
Nov 26 12:45:26 lappy sddm[836]: Loading theme configuration from "/usr/share/sddm/themes/heritage/theme.conf"
Nov 26 12:45:26 lappy sddm[836]: Greeter starting...
Nov 26 12:45:26 lappy sddm[836]: Adding cookie to "/var/run/sddm/{a7a09388-4472-4380-8eeb-2a7819ca699b}"
Nov 26 12:45:27 lappy sddm[836]: Greeter session started successfully
Nov 26 12:45:28 lappy sddm[836]: Message received from greeter: Connect
Nov 26 12:45:29 lappy sddm[836]: Auth: sddm-helper exited with 7
Nov 26 12:45:29 lappy sddm[836]: Greeter stopped.

For more info on troubleshooting with systemd check Arch’s wiki.


(kepszlok) #39

Hmm. Intresting, but i did get nothing below “Starting…”


(Neofytos Kolokotronis) #40

That’s strange. If downgrading to v15 fixes the problem for you, maybe you will have to wait for this to be fixed upstream.


(kepszlok) #41

I did not have sddm v15 in cache, so i can not test it.


(tom) #42

no problem :smiley:
you can get it here https://rsync.chakralinux.org/packages/core/x86_64/sddm-0.15.0-1-x86_64.pkg.tar.xz


(kepszlok) #43

Thanx!

Downgrading to 0.15 - sddm works fine
Upgrading from 0.15 to 0.16 - sddm are not working
Downgrading again to 0.15 - sddm works fine

So yes, 0.15 are OK here.


(varanus) #44

I have encountered the same issue, upgrading chakra and even by installing the latest ISO.
The pc is a laptop with an Samsung SSD and an Nvidia card. Initially I thought that the black screen was because of the graphics card and after some time of searching I found that downgrading to version 0.15 solved the issue.

I have had the same issue on my second pc (most important is that is my business laptop). This one has chakra for at least 2 years now, updating continuously without any issues.

I would like to point out that for me chakra is the more stable linux distro used in my 10 years linux experience.


(Neofytos Kolokotronis) #45

@brikler mentioned that the upgrade to Plasma 5.11.4 that just landed in stable fixed this issue for him. I don’t really understand how that would help, but can you guys check and report back if this is true after you upgrade?
Edit: Seems it doesn’t, see the following post.

If it doesn’t, I will suggest to the rest of the team to downgrade this back to v15 and release an announcement, as it is affecting many users. Reaching a black screen after your first upgrade when installing with our latest ISO will give an ugly first impression.
Edit: There is also a patch available in the link below we could try.

There are some workarounds posted on the upstream thread, but this needs to be resolved with a new release for sddm:


(tom) #46

i was wrong :frowning:
for me can sddm start plasma mostly but not always sometimes i see the well known black screen.

i would down grad sddm.


(kepszlok) #47

Yeah, it’s not helping, i checked it on my both installation.

So we shoud switch back to 0.15 until a fixed 0.16 comes up.


(brli) #48

For a quick fix on most of the platform: add your graphic driver modules (mostly i915, radeon or nouveau for FOSS one) to MODULES="" array under /etc/mkinitcpio.conf and regenerate the initramfs.
(which is IMO the main reason why I can’t reproduce this issue on mine.)

For others: I’ve bump the package to upstream git head, it might work better.


(Neofytos Kolokotronis) #49

Just to clarify, @brli has pushed a new update to sddm which is built from the latest available git commit (0.16.0+137+cc00330-1) that includes the patch mentioned in the upstream thread.

Can those experiencing this issue please try it (simply upgrade to this version, it is available in core) and see if it changes anything?


(kepszlok) #50

Aaaaa, thats’s fixed it!!! Finally. :slight_smile:


(system) closed #51

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.