[SOLVED] cannot access desktop after upgrade, downgrading systemd ...

gxt25 · 2017-07-05 06:04:31

Hello,

After pacman -Syu yesterday I was unable to log in to my desktop (Mate). Lightdm would come up with the logon screen, but after entering credentials would always get

Could not connect to session bus: Failed to connect to socket /tmp/dbus-PY80yBaj2u: Connection refused

I tried booting to the previous kernel to no avail and separately tried downgrading dbus also to no avail. I booted back into the current kernal (4.11.7-1-ARCH x86_64 (64 bit)) and (re)upgraded dbus to the latest version. I then downgraded systemd from systemd-233-7 down to systemd-232-8 and after a reboot was able to connect to the desktop once again.

https://pastebin.com/ZYiqhGuu

My actions here were largely trial and error with a dose of google. Does this look like a bug in systemd? Has anyone encountered this? I read thru some similar but not exactly the same threads but the solutions in those threads (such as downgrading dbus) did not work in my case (since the symptoms were not 100% anyway this is not surprising). Not sure what to do next, since downgrading systemd hardly seems like a permanent solution.

Thanks in advance.

In case it becomes relevant, inxi -F yields:

Kernel: 4.11.7-1-ARCH x86_64 (64 bit)
           Desktop: MATE 1.18.0  Distro: Arch Linux
Machine:   Device: desktop Mobo: ASUSTeK model: SABERTOOTH P67 v: Rev 1.xx
           BIOS: American Megatrends v: 1502 date: 03/02/2011
CPU:       Quad core Intel Core i7-2600 (-HT-MCP-) cache: 8192 KB 
           clock speeds: max: 3800 MHz 1: 2080 MHz 2: 2050 MHz 3: 1972 MHz
           4: 1692 MHz 5: 1640 MHz 6: 2070 MHz 7: 1890 MHz 8: 1616 MHz
Graphics:  Card: NVIDIA GK104 [GeForce GTX 660 Ti]
           Display Server: N/A drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           tty size: 80x20
Audio:     Card-1 NVIDIA GK104 HDMI Audio Controller driver: snd_hda_intel
           Card-2 Intel 6 Series/C200 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.11.7-1-ARCH
Network:   Card: Intel 82579V Gigabit Network Connection driver: e1000e
           IF: eno1 state: up speed: 1000 Mbps duplex: full
           mac: f4:6d:04:af:c0:16
Drives:    HDD Total Size: 2000.4GB (34.1% used)
           ID-1: /dev/sda model: SAMSUNG_HD204UI size: 2000.4GB
Partition: ID-1: / size: 52G used: 14G (28%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 1.8T used: 622G (37%) fs: ext4 dev: /dev/sda2
Sensors:   System Temperatures: cpu: 38.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 182 Uptime: 27 min Memory: 1230.6/7965.0MB
           Init: systemd Client: Shell (bash) inxi: 2.3.23

Last edited by gxt25 (2017-07-06 15:41:28)

evil.genius · 2017-07-05 17:18:30

There's another thread, but no solution yet. https://bbs.archlinux.org/viewtopic.php?id=227895

WorMzy · 2017-07-05 18:10:16

I'm not sure that thread is relevant, evil.genius. gxt25, are you calling 'dbus-launch' anywhere in your initialization scripts? That has not been supported for a while now. Your dbus session path should be pointing at /run/user/$UID/bus, not /tmp/dbus-xxxx. Check your initialization scripts and make sure you aren't using dbus-launch anywhere.

evil.genius · 2017-07-05 19:00:54

It looks to me that in both cases the desktop is unable to connect to dbus because systemd is failing to set up the user. I suspect gxt25 will find that /run/user/$UID is empty.

gxt25 · 2017-07-06 06:08:47

WorMzy wrote:

gxt25, are you calling 'dbus-launch' anywhere in your initialization scripts? That has not been supported for a while now. Your dbus session path should be pointing at /run/user/$UID/bus, not /tmp/dbus-xxxx. Check your initialization scripts and make sure you aren't using dbus-launch anywhere.

I'm sorry, can you refresh my memory? Which files and where should I check this? I don't recall setting up anything manually to use dbus-launch, but there are a few fuzzy patches in my memory from the initial install process where I may have set something or other.

/run/user/$UID is not currently empty, but I am running on the downgraded systemd - I failed to check that path with the newer (possibly faulty) systemd version running.

It seems every file under the subdirectories under /etc/systemd/system/ is a symlink to /usr/lib/systemd/system/ Is this right? E.G.

/etc/systemd/system/numlock.service -> /usr/lib/systemd/system/numlock.service

Last edited by gxt25 (2017-07-06 06:19:14)

gxt25 · 2017-07-06 06:18:03

Also,

xdg-open my_file.ods

gives

** (soffice:9268): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NZ12N71CRP: Connection refused

. This is with the older version of systemd running. So it seems something somewhere is configured to point to /tmp/dbus-XXXX instead of /run/user/$UID/bus. Did I screw up a config file somewhere along the way?

seth · 2017-07-06 12:48:08

You can ignore the at-spi issues for the moment (unless you rely on the a11y features, of course)
If they're the only ones pointing /tmp/dbus-<funkyhash> and downgrading systemd "fixes" it, it's very likely https://bbs.archlinux.org/viewtopic.php?id=227895

=> Look up your journal for similar aborts of the user systemd process.

gxt25 · 2017-07-06 15:27:23

seth wrote:

You can ignore the at-spi issues for the moment (unless you rely on the a11y features, of course)
If they're the only ones pointing /tmp/dbus-<funkyhash> and downgrading systemd "fixes" it, it's very likely https://bbs.archlinux.org/viewtopic.php?id=227895
=> Look up your journal for similar aborts of the user systemd process.

I will look into the secondary issues when I get the time. Thank you for the pointers. As for accessing the desktop with the latest systemd, https://bbs.archlinux.org/viewtopic.php?id=227895 solves it for me. Thanks!

/etc/enviroment

had

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
EDITOR="/usr/bin/vim
VISUAL="/usr/bin/vim

I do remember creating this file and I did not put those quotes there when I did so. Something modified this file. Removing those quotes and then

pacman -Syu

results in everything working again. Thanks again. Marking this thread solved.

Arch Linux

#1 2017-07-05 06:04:31

[SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#2 2017-07-05 17:18:30

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#3 2017-07-05 18:10:16

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#4 2017-07-05 19:00:54

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#5 2017-07-06 06:08:47

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#6 2017-07-06 06:18:03

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#7 2017-07-06 12:48:08

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

#8 2017-07-06 15:27:23

Re: [SOLVED] cannot access desktop after upgrade, downgrading systemd ...

Board footer