| View previous topic :: View next topic |
| Author |
Message |
Checko55
n00b
Joined: 02 Feb 2014
Posts: 32
|
 Posted: Wed Aug 12, 2020 7:56 am Post subject: non-root Xorg issues after switch to elogind |
 |
|
Hello,
I recently switch to elogind using the wiki without any problems.
A few days ago I removed consolekit and did a --depclean where a lot of packages were removed.
After a reboot sddm didn't come up again.
Following a lot of threads and wikis I may have found the problem at least partly.
I had to change permissions on tty0, tty1 and tty7 and now I can start using startx. When I try
to start sddm with xdm nothing happens.
These are some results after logging in using startx as user (which is not my normal way to get to the DE)
| Code: |
groups
wheel audio video users vboxusers user plugdev
|
| Code: |
loginctl list
No sessions.
|
| Code: |
loginctl user-status
Could not get properties: Is a directory
|
| Code: |
ps aux |grep dbus
message+ 3906 0.0 0.0 4272 3000 ? Ss 09:19 0:00 /usr/bin/dbus-daemon --system
user 4942 0.0 0.0 4468 2028 tty1 S 09:20 0:00 dbus-launch --sh-syntax --exit-with-session startplasma-x11
user 4943 0.0 0.0 4396 2956 ? Ss 09:20 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
user 5051 0.0 0.0 223564 20488 ? Sl 09:20 0:00 /usr/bin/gmenudbusmenuproxy
user 19473 0.0 0.0 8960 1808 pts/2 S+ 09:54 0:00 grep --colour=auto dbus
|
| Code: |
grep -r elogind /etc/pam.d/
/etc/pam.d/sddm-greeter:session optional pam_elogind.so
/etc/pam.d/elogind-user:session optional pam_elogind.so
|
Hope that information can help.
Thanks in advance. |
|
| Back to top |
|
 |
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1705
Location: South America
|
| Posted: Wed Aug 12, 2020 2:39 pm Post subject: Re: non-root Xorg issues after switch to elogind |
|
|
| Checko55 wrote: | | Code: |
grep -r elogind /etc/pam.d/
/etc/pam.d/sddm-greeter:session optional pam_elogind.so
/etc/pam.d/elogind-user:session optional pam_elogind.so
|
|
/etc/pam.d/system-auth is missing in that output. Check that sys-auth/pambase has been installed with the elogind USE flag set. |
|
| Back to top |
|
|
Checko55
n00b
Joined: 02 Feb 2014
Posts: 32
|
| Posted: Sat Aug 15, 2020 5:57 am Post subject: |
|
|
Hi,
I've added the line, nothing changed so far.
| Code: |
grep -r elogind /etc/pam.d/
/etc/pam.d/system-auth:session optional pam_elogind.so
/etc/pam.d/sddm-greeter:session optional pam_elogind.so
/etc/pam.d/elogind-user:session optional pam_elogind.so
|
|
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1705
Location: South America
|
| Posted: Sat Aug 15, 2020 2:44 pm Post subject: |
|
|
Post the output of:
| Code: | $ emerge -pv elogind pambase shadow sddm
$ rc-status -a |
|
|
| Back to top |
|
|
Checko55
n00b
Joined: 02 Feb 2014
Posts: 32
|
| Posted: Sun Aug 16, 2020 6:30 am Post subject: |
|
|
| Code: |
emerge -pv elogind pambase shadow sddm
[ebuild R ] sys-auth/elogind-243.7::gentoo USE="acl pam (policykit) -debug -doc (-selinux)" 0 KiB
[ebuild R ] sys-auth/pambase-20200806::gentoo USE="elogind nullok passwdqc sha512 -caps -debug -minimal -mktemp -pam_krb5 -pam_ssh -securetty (-selinux) -systemd" 0 KiB
[ebuild R ] x11-misc/sddm-0.18.1-r3::gentoo USE="elogind pam (-consolekit) -systemd -test" 0 KiB
[ebuild R ] sys-apps/shadow-4.8.1-r2::gentoo USE="acl cracklib nls pam (split-usr) su xattr -audit -bcrypt (-selinux) -skey" 0 KiB
|
| Code: |
rc-status -a
Runlevel: shutdown
killprocs [ stopped ]
savecache [ stopped ]
mount-ro [ stopped ]
Runlevel: sysinit
devfs [ started ]
dmesg [ started ]
kmod-static-nodes [ started ]
opentmpfiles-dev [ started ]
sysfs [ started ]
cgroups [ started ]
udev [ started ]
udev-trigger [ started ]
Runlevel: boot
hwclock [ started ]
modules [ started ]
fsck [ started ]
root [ started ]
mtab [ started ]
procfs [ started ]
binfmt [ started ]
termencoding [ started ]
swap [ started ]
localmount [ started ]
sysctl [ started ]
bootmisc [ started ]
keymaps [ started ]
save-keymaps [ started ]
loopback [ started ]
save-termencoding [ started ]
alsasound [ started ]
hostname [ started ]
elogind [ started ]
opentmpfiles-setup [ started ]
urandom [ started ]
Runlevel: default
sysklogd [ started ]
cronie [ started ]
dbus [ started ]
net.enp5s0 [ started ]
netmount [ started ]
powernowd [ started ]
sshd [ started ]
local [ started ]
Runlevel: nonetwork
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
Dynamic Runlevel: manual
|
|
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1705
Location: South America
|
| Posted: Sun Aug 16, 2020 8:06 pm Post subject: |
|
|
That looks OK. I guess we'll have to investigate some more why loginctl shows no sessions.
1. Post the output of busctl --system, so that we can see if elogind-daemon has connected to the system-wide message bus
2. Leave a dbus-monitor process running in your current terminal, so that we can watch D-Bus activity:
| Code: | | sudo dbus-monitor --system interface=org.freedesktop.login1.Manager >dbus-monitor.log |
3. Change to a different VT using Alt + F<number>, log in, and post the output of loginctl list-sessions, so that we can see if there are still no sessions
4. Exit from that virtual terminal and stop dbus-monitor with Ctrl + C in your original one
5. Post the generated dbus-monitor.log file |
|
| Back to top |
|
|
Checko55
n00b
Joined: 02 Feb 2014
Posts: 32
|
| Posted: Sun Aug 23, 2020 8:24 am Post subject: |
|
|
Hi,
should this be done without any xdm or startx started before and should I then do it "my" usual way to
start xdm and not with startx like I do it at the moment?
thx |
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2179
|
| Posted: Sun Aug 23, 2020 8:45 am Post subject: Re: non-root Xorg issues after switch to elogind |
|
|
| Checko55 wrote: | ...
After a reboot sddm didn't come up again.
Following a lot of threads and wikis I may have found the problem at least partly.
I had to change permissions on tty0, tty1 and tty7 and now I can start using startx. When I try
to start sddm with xdm nothing happens.
.... |
/var/log/sddm.log may have some useful information.
_________________
Greybeard |
|
| Back to top |
|
|
Checko55
n00b
Joined: 02 Feb 2014
Posts: 32
|
| Posted: Sun Aug 23, 2020 3:07 pm Post subject: |
|
|
This is what is written in sddm.log
| Code: |
[15:59:06.287] (II) DAEMON: Initializing...
[15:59:06.290] (II) DAEMON: Starting...
[15:59:06.291] (II) DAEMON: Logind interface found
[15:59:46.402] (WW) DAEMON: Signal received: SIGTERM
[15:59:46.480] (II) DAEMON: Initializing...
[15:59:46.484] (II) DAEMON: Starting...
[15:59:46.484] (II) DAEMON: Logind interface found
[16:00:11.850] (WW) DAEMON: Signal received: SIGTERM
[16:00:11.928] (II) DAEMON: Initializing...
[16:00:11.931] (II) DAEMON: Starting...
[16:00:11.932] (II) DAEMON: Logind interface found
[16:13:41.921] (WW) DAEMON: Signal received: SIGTERM
[15:53:23.869] (II) DAEMON: Initializing...
[15:53:23.873] (II) DAEMON: Starting...
[15:53:23.873] (II) DAEMON: Logind interface found
[17:42:23.368] (WW) DAEMON: Signal received: SIGTERM
[15:30:36.828] (II) DAEMON: Initializing...
[15:30:36.832] (II) DAEMON: Starting...
[15:30:36.832] (II) DAEMON: Logind interface found
[15:31:16.853] (WW) DAEMON: Signal received: SIGTERM
[15:31:16.931] (II) DAEMON: Initializing...
[15:31:16.936] (II) DAEMON: Starting...
[15:31:16.936] (II) DAEMON: Logind interface found
[15:31:38.773] (WW) DAEMON: Signal received: SIGTERM
|
|
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1705
Location: South America
|
| Posted: Sun Aug 23, 2020 3:08 pm Post subject: |
|
|
| Checko55 wrote: | | should this be done without any xdm or startx started before [...] |
For the test of elogind and session creation, don't start SDDM and don't use startx. Use kernel virtual terminals (text user interface). |
|
| Back to top |
|
|
|
Desktop Environments
