Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43353 - tmp mounted with wrong permissions

Attached to Project: Arch Linux
Opened by Peter Wood (peter_wood) - Tuesday, 06 January 2015, 07:39 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 06 January 2015, 13:36 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
On three of my computers, the permissions of tmp are set incorrectly after start / reboot (not always, but very often)

Additional info:
I have no entry for /tmp in /etc/fstab, so according to systemd presets, it should tmpfs should be mounted on /tmp with the following permissions 1777. However, ever second start/reboot /tmp does not have the executable bit set for owner, group, or others, which among other things prevents me from starting X, and I have to reboot, or issue mount -a, which causes the permissions to be set correctly.
Just to make sure: /tmp gets mounted. It shows up in the list produceced by 'mount' without arguments
systemctl show tmp.mount claims that tmp was successfully mounted
No errors in journalctl
/tmp directory is empty before mount
Is it possibly a timing issue? Login, and start of X happen, before mounting of tmpfs is completed?

Steps to reproduce:

This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 06 January 2015, 13:36 GMT
Reason for closing:  None
Comment by Dave Reisner (falconindy) - Tuesday, 06 January 2015, 13:29 GMT
Please use the forums for support. I can't see any packaging bug here, and there's a lot of seemingly contradictory information in your post. It's likely some site-local misconfiguration on your part.

Loading...