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

sddm
intel

(Jean-Baptiste Louvet) #1
System information, pacman configuration, and pacman log

System information

Linux jbl-pc 4.12.4-1-CHAKRA #1 SMP PREEMPT Tue Aug 1 18:19:44 CEST 2017 x86_64 GNU/Linux

Hardware information

cpu:                                                            
                       Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2657 MHz
                       Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2315 MHz
                       Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2472 MHz
                       Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2559 MHz
keyboard:
                       Dell QuietKey Keyboard
  /dev/input/event7    AT Translated Set 2 keyboard
mouse:
                       Microsoft SideWinder™ Mouse
  /dev/input/mice      AlpsPS/2 ALPS DualPoint Stick
  /dev/input/mice      AlpsPS/2 ALPS DualPoint TouchPad
graphics card:
                       Intel VGA compatible controller
sound:
                       Intel Audio device
                       Intel Audio device
storage:
                       Intel Mobile 82801 SATA RAID Controller
network:
  eno1                 Intel Ethernet controller
  wlp2s0               Intel WLAN controller
network interface:
  wlp2s0               Ethernet network interface
  lo                   Loopback network interface
  eno1                 Ethernet network interface
disk:
  /dev/sda             LITEON LCH-256V2
partition:
  /dev/sda1            Partition
  /dev/sda2            Partition
  /dev/sda3            Partition
usb controller:
                       Intel USB Controller
                       Intel USB Controller
bios:
                       BIOS
bridge:
                       Intel PCI bridge
                       Intel Host bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel ISA bridge
hub:
                       Dell USB2134
                       Linux 4.12.4-1-CHAKRA xhci-hcd xHCI Host Controller
                       Genesys Logic USB Hub 2.0
                       Dell USB5534
                       Linux 4.12.4-1-CHAKRA ehci_hcd EHCI Host Controller
                       Hub
                       Linux 4.12.4-1-CHAKRA xhci-hcd xHCI Host Controller
                       Dell Hub
memory:
                       Main Memory
bluetooth:
                       Bluetooth Device
unknown:
                       FPU
                       DMA controller
                       PIC
                       Keyboard controller
                       Intel SMBus
                       Intel Signal processing controller
                       Intel Communication controller
                       O2 Micro SD Host controller
  /dev/input/event13   SunplusIT Integrated_Webcam_HD
                       Elan Microelectronics Touchscreen

/etc/pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
HoldPkg     = pacman glibc pacman-helpme
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options (CheckSpace enabled by default for safety; color enabled by default 'cause it's fancy)
#UseSyslog
Color
TotalDownload
CheckSpace
VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Never
LocalFileSigLevel = Never
#RemoteFileSigLevel = Required


#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

#[testing]
#Include = /etc/pacman.d/mirrorlist

[lib32]
Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[desktop]
Include = /etc/pacman.d/mirrorlist

[gtk]
Include = /etc/pacman.d/mirrorlist

#[unstable]
#Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

/etc/pacman.d/mirrorlist

# Chakra Linux repository mirrorlist # 

#Australia
#Server = http://mirror.aarnet.edu.au/pub/chakra/$repo/x86_64 

# Brazil 
#Server = http://chakra.c3sl.ufpr.br/$repo/x86_64 

# China 
#Server = http://mirrors.ustc.edu.cn/chakra/$repo/x86_64 
#Server = http://mirror.bjtu.edu.cn/chakra/$repo/x86_64 
#Server = http://mirrors.tuna.tsinghua.edu.cn/chakra/$repo/x86_64  

# Colombia 
#Server = http://mirror.edatel.net.co/chakra/$repo/x86_64 

# France 
Server = http://ftp.ciril.fr/pub/linux/chakra/$repo/x86_64 
Server = http://www-ftp.lip6.fr/pub/linux/distributions/chakra/$repo/x86_64 

# Germany 
#Server = http://ftp.halifax.rwth-aachen.de/chakra/$repo/x86_64 
#Server = http://rsync.chakraos.org/packages/$repo/x86_64

# Greece 
#Server = http://ftp.cc.uoc.gr/mirrors/linux/chakra/$repo/x86_64 

# Italy 
#Server =  http://chakra.mirror.garr.it/mirrors/chakra/$repo/x86_64  

# Russia 
#Server = http://mirror.yandex.ru/mirrors/chakra/$repo/x86_64 

# Switzerland 
#Server = http://archlinux.puzzle.ch/kdemod/$repo/x86_64  

#Taiwan 
#Server = http://free.nchc.org.tw/chakra/$repo/x86_64 
#Server = http://ftp.yzu.edu.tw/Linux/chakra/$repo/x86_64 

# United States
#Server = http://chakra.hostingxtreme.com/$repo/x86_64 
#Server = http://mirror.rit.edu/chakra/$repo/x86_64
#Server = http://mirror.dacentec.com/chakra/$repo/x86_64

/var/log/pacman.log

[2017-10-10 10:10] [PACMAN] Running 'pacman -Syu'
[2017-10-10 10:10] [PACMAN] synchronizing package lists
[2017-10-10 10:10] [PACMAN] starting full system upgrade
[2017-10-11 11:17] [PACMAN] Running 'pacman -Syu'
[2017-10-11 11:17] [PACMAN] synchronizing package lists
[2017-10-11 11:17] [PACMAN] starting full system upgrade
[2017-10-12 09:27] [PACMAN] Running 'pacman -Syu'
[2017-10-12 09:27] [PACMAN] synchronizing package lists
[2017-10-12 09:27] [PACMAN] starting full system upgrade
[2017-10-12 17:25] [PACMAN] Running 'pacman -Syu'
[2017-10-12 17:25] [PACMAN] synchronizing package lists
[2017-10-12 17:25] [PACMAN] starting full system upgrade
[2017-10-13 09:44] [PACMAN] Running 'pacman -Syu'
[2017-10-13 09:44] [PACMAN] synchronizing package lists
[2017-10-13 09:44] [PACMAN] starting full system upgrade
[2017-10-13 09:44] [ALPM] transaction started
[2017-10-13 09:44] [ALPM] upgraded firefox-kde (56.0-1 -> 56.0.1-2)
[2017-10-13 09:44] [ALPM] upgraded firefox-i18n-fr (56.0-1 -> 56.0.1-1)
[2017-10-13 09:44] [ALPM] upgraded krita (3.3.0-1 -> 3.3.1-1)
[2017-10-13 09:44] [ALPM] transaction completed
[2017-10-16 10:20] [PACMAN] Running 'pacman -Syu'
[2017-10-16 10:20] [PACMAN] synchronizing package lists
[2017-10-16 10:20] [PACMAN] starting full system upgrade
[2017-10-16 10:51] [ALPM] transaction started
[2017-10-16 10:51] [ALPM] upgraded ffmpeg (3.2.7-1 -> 3.2.8-1)
[2017-10-16 10:51] [ALPM] upgraded firefox-kde (56.0.1-2 -> 56.0.1-3)
[2017-10-16 10:51] [ALPM] upgraded k3b (17.08.1-1 -> 17.08.1-2)
[2017-10-16 10:51] [ALPM] upgraded sddm (0.15.0-1 -> 0.16.0-1)
[2017-10-16 10:51] [ALPM-SCRIPTLET] Enabling systemd service
[2017-10-16 10:51] [ALPM] upgraded system-config-printer (1.5.8-1 -> 1.5.9-1)
[2017-10-16 10:51] [ALPM] upgraded ttf-noto (20170406-1 -> 20171010-1)
[2017-10-16 10:51] [ALPM-SCRIPTLET] Updating font cache... Done.
[2017-10-16 10:51] [ALPM] transaction completed
[2017-10-17 08:30] [PACMAN] Running 'pacman -Syu'
[2017-10-17 08:30] [PACMAN] synchronizing package lists
[2017-10-17 08:30] [PACMAN] starting full system upgrade
[2017-10-17 09:44] [PACMAN] Running 'pacman -R xf86-video-intel'
[2017-10-17 09:44] [ALPM] transaction started
[2017-10-17 09:44] [ALPM] removed xf86-video-intel (2.99.917+770+gcb6ba2d-1)
[2017-10-17 09:44] [ALPM] transaction completed
[2017-10-17 09:45] [PACMAN] Running 'pacman -S xf86-video-intel'
[2017-10-17 09:45] [ALPM] transaction started
[2017-10-17 09:45] [ALPM] installed xf86-video-intel (2.99.917+770+gcb6ba2d-1)
[2017-10-17 09:45] [ALPM-SCRIPTLET] >>> This driver uses SNA as the default acceleration method. You can
[2017-10-17 09:45] [ALPM-SCRIPTLET]     fall back to UXA if you run into trouble or test experimental
[2017-10-17 09:45] [ALPM-SCRIPTLET]     Glamor acceleration. To do so, save a file with the following 
[2017-10-17 09:45] [ALPM-SCRIPTLET]     content as /etc/X11/xorg.conf.d/20-intel.conf :
[2017-10-17 09:45] [ALPM-SCRIPTLET]       Section "Device"
[2017-10-17 09:45] [ALPM-SCRIPTLET]         Identifier  "Intel Graphics"
[2017-10-17 09:45] [ALPM-SCRIPTLET]         Driver      "intel"
[2017-10-17 09:45] [ALPM-SCRIPTLET]         Option      "AccelMethod"  "sna"
[2017-10-17 09:45] [ALPM-SCRIPTLET]         #Option      "AccelMethod"  "uxa"
[2017-10-17 09:45] [ALPM-SCRIPTLET]         #Option      "AccelMethod"  "glamor"
[2017-10-17 09:45] [ALPM-SCRIPTLET]       EndSection
[2017-10-17 09:45] [ALPM] transaction completed
[2017-10-17 10:13] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/sddm-0.15.0-1-x86_64.pkg.tar.xz'
[2017-10-17 10:13] [ALPM] transaction started
[2017-10-17 10:13] [ALPM] downgraded sddm (0.16.0-1 -> 0.15.0-1)
[2017-10-17 10:13] [ALPM-SCRIPTLET] Enabling systemd service
[2017-10-17 10:13] [ALPM] transaction completed

Hello everyone! I had an annoying issue this morning: no graphical interface.

I first tried to see what was pointed out in the system’s journal:

oct. 17 09:48:30 jbl-pc kernel: Error parsing PCC subspaces from PCCT
oct. 17 09:48:30 jbl-pc kernel: mmc0: Unknown controller version (3). You may experience problems.
oct. 17 09:48:30 jbl-pc systemd-udevd[191]: specified group 'cdemu' unknown
oct. 17 09:48:30 jbl-pc kernel: i801_smbus 0000:00:1f.3: Failed to enable SMBus PCI device (-16)
oct. 17 09:48:30 jbl-pc kernel: iwlwifi 0000:02:00.0: capa flags index 3 larger than supported by driver
oct. 17 09:48:31 jbl-pc systemd-udevd[214]: Error calling EVIOCSKEYCODE on device node '/dev/input/event12' (scan code 0x150, key code 190): Invalid argument
oct. 17 09:48:31 jbl-pc avahi-daemon[331]: chroot.c: open() failed: No such file or directory

(Or something like this, i didn’t backup the original logs, and they were overwritten by the reboots I’ve done to fix this).

After trying to see what was going on with iwlwifi and avahi, I concluded that they were probably not the cause of the problem. Then I remembered running an update yesterday, so I checked my pacman’s journal and found this line:

[2017-10-16 10:51] [ALPM] upgraded sddm (0.15.0-1 -> 0.16.0-1)

So I rolledback to ssdm 0.15.0-1:

sudo pacman -U /var/cache/pacman/pkg/sddm-0.15.0-1-x86_64.pkg.tar.xz

Everything went fine, and my graphical interface is back !

Is there any known issue with sddm 0.16 that can be related ?

For the sake of completeness, here’s a dump of journalctl -p err (I’m not sure that it’s relevant, though):

-- Reboot --
oct. 17 09:48:30 jbl-pc kernel: Error parsing PCC subspaces from PCCT
oct. 17 09:48:30 jbl-pc kernel: mmc0: Unknown controller version (3). You may experience problems.
oct. 17 09:48:30 jbl-pc systemd-udevd[191]: specified group 'cdemu' unknown
oct. 17 09:48:30 jbl-pc kernel: i801_smbus 0000:00:1f.3: Failed to enable SMBus PCI device (-16)
oct. 17 09:48:30 jbl-pc kernel: iwlwifi 0000:02:00.0: capa flags index 3 larger than supported by driver
oct. 17 09:48:31 jbl-pc systemd-udevd[214]: Error calling EVIOCSKEYCODE on device node '/dev/input/event12' (scan code 0x150, key code 190): Invalid argument
oct. 17 09:48:31 jbl-pc avahi-daemon[331]: chroot.c: open() failed: No such file or directory
oct. 17 09:49:49 jbl-pc systemd-coredump[505]: Process 503 (sddm-greeter) of user 1001 dumped core.
                                               
                                               Stack trace of thread 503:
                                               #0  0x00007fd9e7d17a10 raise (libc.so.6)
                                               #1  0x00007fd9e7d1913a abort (libc.so.6)
                                               #2  0x00007fd9e86bddb1 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                                               #3  0x00007fd9e0ed2e0e _ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc (libQt5XcbQpa.so.5)
                                               #4  0x00007fd9e0ed614e _ZN15QXcbIntegrationC1ERK11QStringListRiPPc (libQt5XcbQpa.so.5)
                                               #5  0x00007fd9ea0b968d n/a (/usr/lib/qt5/plugins/platforms/libqxcb.so)
                                               #6  0x00007fd9e8c06f1d _ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPPcS2_ (libQt5Gui.so.5)
                                               #7  0x00007fd9e8c159eb _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
                                               #8  0x00007fd9e8c164fd _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
                                               #9  0x00007fd9e88be847 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5)
                                               #10 0x00007fd9e8c1820f _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5)
                                               #11 0x00007fd9e8c18f24 _ZN15QGuiApplicationC2ERiPPci (libQt5Gui.so.5)
                                               #12 0x0000000000434267 _ZN4SDDM10GreeterAppC2ERiPPc (sddm-greeter)
                                               #13 0x0000000000416d7a main (sddm-greeter)
                                               #14 0x00007fd9e7d04511 __libc_start_main (libc.so.6)
                                               #15 0x0000000000416eea _start (sddm-greeter)
-- Reboot --
oct. 17 10:14:20 jbl-pc kernel: Error parsing PCC subspaces from PCCT
oct. 17 10:14:20 jbl-pc kernel: mmc0: Unknown controller version (3). You may experience problems.
oct. 17 10:14:20 jbl-pc systemd-udevd[188]: specified group 'cdemu' unknown
oct. 17 10:14:20 jbl-pc avahi-daemon[272]: chroot.c: open() failed: No such file or directory
oct. 17 10:14:21 jbl-pc systemd-udevd[207]: Error calling EVIOCSKEYCODE on device node '/dev/input/event8' (scan code 0x150, key code 190): Invalid argument
oct. 17 10:14:21 jbl-pc kernel: i801_smbus 0000:00:1f.3: Failed to enable SMBus PCI device (-16)
oct. 17 10:14:21 jbl-pc kernel: iwlwifi 0000:02:00.0: capa flags index 3 larger than supported by driver
oct. 17 10:14:23 jbl-pc sddm-helper[419]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
oct. 17 10:14:23 jbl-pc sddm-helper[419]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
oct. 17 10:15:07 jbl-pc kup-daemon[577]: Kup n'est pas activé. Activez-le depuis le module de configuration du système. Vous pouvez également l'activer en lançant kcmshell5 kup
oct. 17 10:15:12 jbl-pc akonadi_ical_resource[693]: load error
oct. 17 10:15:12 jbl-pc akonadi_ical_resource[693]: load error
oct. 17 10:15:12 jbl-pc akonadi_ical_resource[693]: akonadi_ical_resource: Error loading file  "/home/jboot/.cache/akonadi_ical_resource_4/akonadi_ical_resource_4"
oct. 17 10:15:30 jbl-pc sddm-helper[1022]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
oct. 17 10:15:30 jbl-pc sddm-helper[1022]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
oct. 17 10:15:31 jbl-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
oct. 17 10:15:48 jbl-pc kernel: Error parsing PCC subspaces from PCCT
oct. 17 10:15:48 jbl-pc kernel: mmc0: Unknown controller version (3). You may experience problems.
oct. 17 10:15:48 jbl-pc systemd-udevd[192]: specified group 'cdemu' unknown
oct. 17 10:15:48 jbl-pc kernel: i801_smbus 0000:00:1f.3: Failed to enable SMBus PCI device (-16)
oct. 17 10:15:48 jbl-pc kernel: iwlwifi 0000:02:00.0: capa flags index 3 larger than supported by driver
oct. 17 10:15:48 jbl-pc avahi-daemon[318]: chroot.c: open() failed: No such file or directory
oct. 17 10:15:49 jbl-pc systemd-udevd[228]: Error calling EVIOCSKEYCODE on device node '/dev/input/event8' (scan code 0x150, key code 190): Invalid argument
oct. 17 10:15:51 jbl-pc sddm-helper[437]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
oct. 17 10:15:51 jbl-pc sddm-helper[437]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
oct. 17 10:15:58 jbl-pc kup-daemon[612]: Kup n'est pas activé. Activez-le depuis le module de configuration du système. Vous pouvez également l'activer en lançant kcmshell5 kup
oct. 17 10:16:03 jbl-pc akonadi_ical_resource[745]: load error
oct. 17 10:16:03 jbl-pc akonadi_ical_resource[745]: load error
oct. 17 10:16:03 jbl-pc akonadi_ical_resource[745]: akonadi_ical_resource: Error loading file  "/home/jboot/.cache/akonadi_ical_resource_4/akonadi_ical_resource_4"

Sddm hangs on boot
Latest status of the testing repository [23 Oct 2017 - 30 Nov 2017]
Black screen after resuming from suspension after upgrading sddm to 0.16.0+137+cc00330-1
(tom) #3

i have read similar in the *german arch forum and *start early mks should solve this problem.

i suppose you can find this solution in the international arch forum to if the german source isn’t enough :wink:

@jboot
a additional question: do you use a HDD or a SSD?

edit typo


(Jean-Baptiste Louvet) #4

I use a SSD, is that what you mean by SDD?


(tom) #5

thank you.
so is my idea not correct

yes i mean SSD i don’t know why sdd…


(Jean-Baptiste Louvet) #6

Yes, that’s exactly the problem I have! Thank you for the pointer :wink: For the moment I kept the downgrade to sddm 0.15 as solution, as starting early mks feels more like a hack to me. If I change my mind for any reason I’ll upgrade this thead.

Thanks again :slight_smile:


After big upgrade, no plasma
(ericjs) #7

It turns out this was a problem for me too, on an SSD-based installation. Putting “i915” into my mkinitcpio MODULES resolved it as per the “start early mks” article. Is sddm-0.15.0-1-x86_64.pkg.tar.xz available for download from anywhere? The last version in my cache is older than that.


(Jean-Baptiste Louvet) #8

For what I know, Chakra doesn’t have an archive of its packages, as it’s the case for Arch. I rolled back using the cache of my machine. I read on the Arch forum that this problem is affecting people there, has been reported upstream and eventually became an official issue on the sddm project. We can hope it will be soon solved upstream.


(tom) #9

if you not satisfied with this workaround so you can try the older version.


(totte) #10

Yes, from the origin and on at least one mirror.


(ericjs) #12

I’m not sure…I may just keep the workaround. I just want to keep my options open.

@totte, thanks for the link. I think I recall the Chakra site used to have a “Packages” tab (or something like that) that linked to a place that held usually the last two versions of packages (but possibly I misremember). Was that just a link to the same rsync site? Why did we get rid of that?

Also, I’m wondering, as a help to someone in the future who may run into this…is there a clear way to know this is the problem? It seemed to not have any particular error message associated with it (at least that I was able to spot). I think @jboot figured it out because it was the only think recently updated (and perhaps he understands the system better than many). In my case it was one of many updates and it was just lucky I had a second system without the problem and a good facility (the tool Beyond Compare) to compare logs and journal outputs. I can imagine another user in the future not having either of these circumstances having a harder time figuring this out. The best I can come up with is that

journalctl -b | grep sddm-greeter

will not show anything if this problem occurs (at least that was the case for me) and

journalctl -b | grep sddm

only showed a few messages for me during the problem, but many messages when it works.

I should also add that I had one successful boot during the problem, so there is a certain amount of luck to this, as it is a timing issue. I can imagine someone with a slightly slower SSD, say, who gets this problem only sporadically.


(Jean-Baptiste Louvet) #13

Thanks :slight_smile: but I think I just had a lot of luck when trying to solve this issue :stuck_out_tongue:

I don’t know if it’s possible to find any logs related to this issue, but I read that this bug can be manually bypassed during boot by logging on tty when the starting procedure stops and then enter the command systemctl restart sddm. If this restarts the graphical interface, it means (I think) that the problem is related to sddm 0.16.


(cidig) #14

I have the same issue when rebooting and I can confirm that systemctl restart sddm solves it but I have to type it everytime I reboot.


(kepszlok) #16

Same here.

Manualy stopping and starting sddm.service or restarting sddm.service works and i get to plasma. But not withouth them.

sddm.servcie are enalbed, and these both status and default target output seems fine to me:

â—Ź sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
Active: active (running) since szo 2017-10-28 12:39:08 CEST; 1min 12s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 486 (sddm)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/sddm.service
└─486 /usr/bin/sddm

okt 28 12:39:08 kepsz-pc systemd[1]: Started Simple Desktop Display Manager.
okt 28 12:39:08 kepsz-pc sddm[486]: Initializing…
okt 28 12:39:08 kepsz-pc sddm[486]: Logind interface found
okt 28 12:39:08 kepsz-pc sddm[486]: Starting…
â—Ź graphical.target - Graphical Interface
Loaded: loaded (/usr/lib/systemd/system/graphical.target; enabled; vendor preset: disabled)
Active: active since szo 2017-10-28 12:39:08 CEST; 1min 19s ago
Docs: man:systemd.special(7)

okt 28 12:39:08 kepsz-pc systemd[1]: Reached target Graphical Interface.

This problem are still there… Any ideas?


(tom) #17

in this case what shows journalctl PID=486 ?


(kepszlok) #18

– No entries –

Btw, i did not have a process with 486 pid. But also got no entries from sddm and sddm.helper processes.

What process shoud be the one with PID=486?


(tom) #19

my sddm state as example

[tom@frija ~]$ systemctl status sddm.service
â—Ź sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
   Active: active (running) since Do 2017-11-02 17:02:12 GMT; 15h ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
 Main PID: 286 (sddm)
    Tasks: 5 (limit: 4915)
   CGroup: /system.slice/sddm.service
           ├─286 /usr/bin/sddm
           └─296 /usr/lib/xorg-server/Xorg -nolisten tcp -auth /var/run/sddm/{7731141d-b3f9-4ac

Nov 02 17:02:14 frija sddm[286]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 02 17:02:14 frija sddm[286]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 02 17:02:14 frija sddm[286]: Session "/usr/share/xsessions/plasma.desktop" selected, comman
Nov 02 17:02:14 frija sddm[286]: Adding cookie to "/var/run/sddm/{7731141d-b3f9-4ac3-9381-5042c
Nov 02 17:02:14 frija sddm-helper[318]: [PAM] Starting...
Nov 02 17:02:14 frija sddm-helper[318]: [PAM] Authenticating...
Nov 02 17:02:14 frija sddm-helper[318]: [PAM] returning.
Nov 02 17:02:14 frija sddm[286]: Authenticated successfully
Nov 02 17:02:14 frija sddm-helper[318]: pam_unix(sddm-autologin:session): session opened for us
Nov 02 17:02:14 frija sddm[286]: Session started

then search the line with “main pid”

 Main PID: 286 (sddm)

ask the journal for related to PID 286

[tom@frija ~]$ journalctl PID=286
-- No entries --

no entries because i haven’t problem :slight_smile:


(Francesco Marinucci) #20

Try to replace your actual configuration file (/etc/sddm.conf) with the new one installed by pacman as /etc/sddm.conf.pacnew.
This fixed the issue for me


(tom) #21

but before you should run diff to compare both files to see the differences


(kepszlok) #22

Saddly, It did changed nothing. But the two files are almost the same, except my autologin config.

old file new file


(Francesco Marinucci) #23

Do you have a 20-intel.conf file inside /etc/X11/xorg.conf.d?
Try to move it elsewhere and reboot