http://bugzilla.opensuse.org/show_bug.cgi?id=1017683 Bug ID: 1017683 Summary: /var/run should not be separate filesystem from /run Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: jiivee@iki.fi QA Contact: jsrain@suse.com Found By: --- Blocker: --- Tumbleweed installation allows (like all other Suse versions) to create /tmp, /run, /var/lock and /var/run as separate tmpfs filesystems. Recently (sometime on last November) Tumbleweed behaviour changed so that many things don't work or are very slow, if /run and /var/run are separate. See <https://forums.opensuse.org/showthread.php/521509-X-broke-gt-after-new-intall-KDE-is-slow> for more info. Solution for experienced problems was to remove entry for /var/run from /etc/fstab and leave bind mounting /var/run to /run for systemd boot process. If using btrfs, there is no sense creating /var/run as subvolume, as it either is not used (overridden by bind mount) or it hides bind mount causing all sorts of problems described of which some were described in separate forum post, see link above. -- You are receiving this mail because: You are on the CC list for the bug.