On 2/7/23 19:20, David Rosenstrauch wrote:
I run a similar setup. But logs look different on my end
Feb 06 10:16:02 titan systemd[1]: Starting Light Display Manager...
...
Feb 06 10:16:02 titan systemd[1]: Started Light Display Manager.
Feb 06 10:16:02 titan systemd[1]: Reached target User and Group Name Lookups.
Feb 06 10:16:02 titan systemd[1]: Starting Accounts Service...
...
Feb 06 10:16:02 titan systemd[1]: Started Accounts Service.
...
Feb 06 10:16:03 titan lightdm[733]: pam_unix(lightdm-greeter:session): session
opened for user lightdm(uid=975) by (uid=0)
The issue seems to be that "Accounts Service". When I look at what's running
on my machine with the keyword "account" I see this:
# ps aux | grep -i account
root 666 0.0 0.0 237396 236 ? Ssl Feb06 0:00
/usr/lib/accounts-daemon
# pacman -Qo /usr/lib/accounts-daemon
/usr/lib/accounts-daemon is owned by accountsservice 22.08.8-2
Perhaps that "accountsservice" package somehow got uninstalled on your
machine? A quick search turned up this page, which would seem to also suggest
that:
https://dev.to/nabbisen/fix-lightdm-error-the-name-org-freedesktop-accounts-was-not-provided-by-any-service-files-512b
Thanks David,
Had already found the accountsservice posts -- unfortunately that isn't the
issue here. (installed it, rebooted, checked with linux and linux-LTS, no
difference -- uninstalled it)
There is some distinct permission or auth change in the package updates
from the last 3-4 days that is preventing an xorg connection resulting in
"Connection Refused". I captured the full startx output in case that helps:
$ startx
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux valkyrie 6.1.9-arch1-2 #1 SMP PREEMPT_DYNAMIC
Fri, 03 Feb 2023 18:49:53 +0000 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux
root=UUID=515ef9dc-769f-4548-9a08-3a92fa83d86b rw iommu=soft amd_iommu_dump=
quiet audit=0
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Feb 7 21:02:15 2023
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
It appears I'm not the only one. Soon after posting to the AUR project for
the nvidia-390xx drivers, another confirmed x broke for him as well. See
latest comments at:
https://aur.archlinux.org/pkgbase/nvidia-390xx-utils
So it has to be some change that the nvidia-390xx driver isn't playing nice
with. Like I said earlier, my Intel graphic box is happy as a clam.
Also, xorg itself is happy with the nvidia-390xx driver, loads it fine, no
errors in Xorg.0.log and X seems to fully start before being shutdown by the
"Connection Refused" error.
Nothing else has changed on this box. It's a server doing mail, web, dns,
dhcpd4, etc... that just sits there doing its thing. Simple OLD AMD 8-core
with 32G and 4T in 4 RAID1 partitions. That how I know NOTHING changed on the
box -- other than pacman updates on 2/7 and then I rebuilt the nvidia-390xx
driver packages (no difference, same issue)
The server aspect also makes it a bit difficult to take offline for
rollback and testing that takes the server down. (I have another Arch server
doing backup dns and dhcpd for the local LAN and a backup mail host at the
office, but even so, I'm a bit reluctant to purposefully take it off line
unless the electric company does it for me...)
So I'm a bit stumped on where to dig to find whatever changed? I mean do I
strace the startx call -- would that be useful?
--
David C. Rankin, J.D.,P.E.
