Resolution -- see below

On Sat, 25 Oct 2025 14:24:04 -0700
Geoffrey Leach <[email protected]> wrote:

> On Sat, 25 Oct 2025 13:25:42 -0700
> Samuel Sieb <[email protected]> wrote:
> 
> > On 10/25/25 12:41 PM, Geoffrey Leach wrote:
> > > Fresh install of Fedora 42 after Windows 11. No problems. Install
> > > and upgrade went smoothly.
> > 
> > What install method did you use?
> > How did you upgrade without logging in?
> > 
> > > Assigned password for root (and user) rejected
> > > Booted to bash, used passwd root to re-assign
> > > new passwd (fribb1ex) accepted
> > > Rebooted
> > > Same problem
> > 
> > Anything in the logs?
> > 
> 
> Install method
>       Download xfce spin from Fedora web
>       Created thumb drive using mediawriter
>       Booted from same after media check OK
> 
> How did you upgrade without logging in?
>       Good question. After the install I went directly to upgrade as
>       root. I can't recall whether a password was requested, but it
> so it (obviously) was accepted. (n any event, the system was
>       powered off overnight.
> 
> Logs
>       Nothing in p0, p1 or p2
>       In p3 there are a bunch of complaints from SELinux preventing
>       unix_chkpwd from read access on file shadow. Running sealert
> -l gives the message: "SELinux not enabled"
> 
> I can't recall SELinux being mentioned during install. FWIW, I used
> automatic partitioning. 
> 
> Not mentioned: this was not an encrypted install.

Resolved (perhaps)

Changed the setting of SELINUX in /etc/selinus/config to permissive.
That appears to have resolved the problem.

-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to