Gotcha bug for SXCR 53 and 54
A few folks have come across an issue after using live upgrade to go to build 54 of nevada, so to save some hassles for when it comes out as an SXCR, I thought I’d post this. It also seems that some folks hit it with 53.
It looks like after such a live upgrade the mountpoints for /tmp and /var/run are created with 0700 permissions. The /tmp permisssion will prevent a non-root login in gnome. The /var/run will cause more subtle issues with stuff that wants to access in there. One example of this would be from rhythmbox.
** (rhythmbox:1439): WARNING **: hal_initialize failed: Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied
The actual issue is the permissions of the mount points, and you can’t fix these in any way that will be persistant across reboots (as they are tmpfs’s) unless you unmount the filesystems. You could try booting with “-m milestone=none” and fixing the underlying moountpoints, or you could try the following. If you don’t have anything using those mountpoints yet, you’ll get away with it.
# umount /tmp # umount /var/run # chmod 1777 /tmp # chmod 755 /var/run # mount /tmp # mount /var/run
This has been logged as
6497684 Unable to login due to live upgrade setting incorrect permissions on /tmp and /var/run
Which, unfortunately is not available externally (being logged against live-upgrade.
Of course the preventative thing to do would be to mount the alternate boot environment and fix the permissions before booting it.