Arch Linux

Description:
After upgrading systemd to 233-1 and rebooting the machine, starting sddm, and authorizing user - desktop environment (particulary plasma) is unable to start showing "Could not sync environment to dbus." error window.

journalctl doesn't notice anything particulary interesting except for this:
systemd[916]: user@994.service: Failed at step KEYRING spawning /usr/lib/systemd/systemd: Disk quota exceeded

It's interesting because i'm not using quota.

My Arch is installed on btrfs filesystem, build on two phisical disks:
# btrfs fi show
Label: 'archlinux' uuid: 75887859-50e0-4bd8-98b2-84e6ad916a29
Total devices 2 FS bytes used 171.24GiB
devid 1 size 123.00GiB used 89.03GiB path /dev/sda2
devid 2 size 123.00GiB used 89.03GiB path /dev/sdb1


# LANG=C df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 246G 174G 71G 72% /

# mount | grep -i " / "
/dev/sda2 on / type btrfs (rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,subvolid=2804,subvol=/rootfs)


Btrfs volume is sliced to basic subvolumes to allow snapshoting with subvolumes:
- rootfs
- homefs
- pacpkg
- snaps
I believe the names are self-describing.

Downgrading btrfs-progs from 4.10-1 to 4.9.1-1 didn't help.
Downgrading systemd and systemd-sysvcompat to 232-8 (with newest btrfs-progs 4.10-1 installed) solved the problem.



Additional info:
* package version(s)
233-1

* config and/or log files etc.
journalctl -b said:
mar 12 10:53:28 xaos systemd[916]: user@994.service: Failed at step KEYRING spawning /usr/lib/systemd/systemd: Disk quota exceeded
mar 12 10:53:28 xaos systemd[1]: Started Session c1 of user sddm.
mar 12 10:53:28 xaos systemd[1]: Failed to start User Manager for UID 994.
mar 12 10:53:28 xaos systemd[1]: user@994.service: Unit entered failed state.
mar 12 10:53:28 xaos systemd[1]: user@994.service: Failed with result 'protocol'.
mar 12 10:53:28 xaos sddm-helper[914]: pam_systemd(sddm-greeter:session): Failed to create session: Start job for unit user@994.service failed with 'failed'

startx (with exec startkde) said:
X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.13-1-lts x86_64
Current Operating System: Linux xaos 4.11.0-rc1-mainline #1 SMP PREEMPT Tue Mar 7 09:55:43 CET 2017 x86_64
Kernel command line: BOOT_IMAGE=../vmlinuz-linux-mainline root=/dev/disk/by-uuid/75887859-50e0-4bd8-98b2-84e6ad916a29 edd=off rw rootflags=subvol=rootfs initrd=../initramfs-linux-mainline.img
Build Date: 03 March 2017 06:00:24PM

Current version of pixman: 0.34.0
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: "/home/dreem/.local/share/xorg/Xorg.0.log", Time: Sat Mar 11 23:46:29 2017
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
Loading stage "initial" 151
startkde: Starting up...
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
startkde: Could not sync environment to dbus.
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.


Steps to reproduce:
Assuming that problem only occurs when using btrfs:
1. update systemd to 233-1
2. reboot