rights messed up after moving installation

[lee]

Hi,

I have experienced some trouble with moving my Fedora installation to
different partitions.  For the move, I prepared the target partitions,
created file systems on them and booted the emergency.target.  Then I
used "rsync --archive -H --progress -x <src> <dst>" to copy /var and /.

I thought using the "--archive" option of rsync is supposed to transfer
all attributes?

Then I bind mounted /proc, /sys and /dev to the appropriate directories
on the new root file system and chrooted into it.  From there, I mounted
the new file systems, adjusted /etc/fstab and installed grub2 and
created a new grub2.cf. grub2-mkconfig had some trouble with creating
files in /var/lock, yet it created the new configuration, and I was able
to boot into the moved installation.

For some reason, /var couldn't be mounted, and I ran "restorecon -v -R"
on it, which reset a lot (probably all) files.  After rebooting, /var
could be mounted, but I was unable to log in:  I got the login prompt
and after entering my password, I got logged out again immediately.

So I booted the emergency.target again and mounted all file systems
except /home.  After running "restorecon -v -R /", I rebooted and am now
able to log in.

Some rights are still messed up, though.  The "users" command doesn't
produce any output, and pulseaudio doesn't run anymore.  There are
messages in /var/log/messages about this:


Nov  5 21:50:38 yun dbus-daemon[807]: dbus[807]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov  5 21:50:38 yun dbus[807]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov  5 21:50:38 yun dbus-daemon[807]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Nov  5 21:50:38 yun dbus-daemon[807]: ** Message: entering main loop
Nov  5 21:50:52 yun systemd-logind[775]: New session 1 of user lee.
Nov  5 21:51:08 yun dbus-daemon[807]: ** Message: No devices in use, exit
Nov  5 21:51:27 yun dbus-daemon[807]: dbus[807]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov  5 21:51:27 yun dbus[807]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov  5 21:51:27 yun dbus-daemon[807]: dbus[807]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov  5 21:51:27 yun dbus[807]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov  5 21:51:27 yun dbus-daemon[807]: dbus[807]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=1000 pid=1278 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.bluez.Manager" member="ListAdapters" error name
="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=685 comm="/usr/sbin/bluetoothd -n ")
Nov  5 21:51:27 yun dbus[807]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=1000 pid=1278 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.bluez.Manager" member="ListAdapters" error name="(unset)" request
ed_reply="0" destination="org.bluez" (uid=0 pid=685 comm="/usr/sbin/bluetoothd -n ")
Nov  5 21:51:27 yun pulseaudio[1278]: [pulseaudio] bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.AccessDenied


When I run "aplay -l" as normal user, it says "no soundcards found".
When I run it as root, it does list the soundcard.  The needed modules
are loaded, and when root tries to play some sound with aplay, it says
that pulseaudio refuses the connection.  Since pulseaudio isn't running,
that isn't surprising :)

Surprising is that when the normal user plays something with aplay,
aplay says it's playing and there is no sound.


So some --- or a lot of --- rights may be messed up now.  That the
"users" command doesn't give any output indicates that things might be
messed up pretty badly.  How do I fix this?

I still have the original I made the copy from, so if there is a way to
"transfer" rights by reading them from the original and applying them to
the copy, that might be a way to fix it.  Please tell me I don't need to
re-install ...