Re: Authentification error in kdm, gdm after rsync cloning an OS... console fine.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



thank you very much for that tip !  I'll report back.

On Thu, Jan 9, 2020 at 5:03 PM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 2020-01-10 07:52, linux guy wrote:
> Hello wonderful Fedora people.  ;)
>
> I cloned an operating system using rsync using the following, basically: 
>
> sudo rsync -aHxv --numeric-ids --progress root@brix:/* /mnt/drive --exclude=/dev --exclude=/proc --exclude=/sys --exclude=/tmp --exclude=/boot
>
> It worked fantastically well.  I'll post the nity gritty details in another thread once I confirm a few things.
>
> Everything works perfectly, except that I can't log into a session with kdm or gdm because of an authentication error.   I can log into a console session without any issues.
>
> I have never been able to log into a session using gdm.  The session displays the user names, it allows me to input a password and then the screen flashes and it returns me to the gdm screen.
>
> I am able to log into a kdm session.  When I first do I received several SELinux errors and I am asked for the root password anytime I tried to do anything.  Other than that everything worked well.
>
> The message is "Authentification is required to access the PC/SC daemon"
>
> One of the SELinux erros was something about unix_chkpwd map /etc/ld.so.cache and it gave me an option to fix it.  I ran that command and the SELinux errors seemed to have stopped.
>
> Furthermore when I run passwd <username> and try to reset a password, I get: Authentication Token Manipulation error.
>
> What is going wrong and how do I fix it ?

Based on what you've said, and what you've done it would be advisable to run

"fixfiles onboot"  from the command line as root and reboot to restore all the selinux contexts.


--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux