DNF Selinux Upgrade Failure

[Stephen Morris]

Hi,
     Doing a sudo dnf upgrade I got the following failure:

[ 29/106] Upgrading snapd-selinux-0:2.66.1-0.fc41.noarch 
                                                                                          100% 
|   1.5 KiB/s |  45.4 KiB |  00m30s
> > > Running post-install scriptlet: snapd-selinux-0:2.66.1-0.fc41.noarch
> > > Finished post-install scriptlet: snapd-selinux-0:2.66.1-0.fc41.noarch
> > > Scriptlet output:
> > > Failed to resolve typeattributeset statement at

/var/lib/selinux/targeted/tmp/modules/200/snappy/cil:223
> > > Failed to resolve AST
> > > semodule:  Failed!

Doing a google search I found an entry 
https://discussion.fedoraproject.org/t/selinux-related-errors-when-updating-... 
that indicates this was an issue in F36 where selinux removed some 
classes and was only an issue where F36 was an upgrade and not a fresh 
install, and that selinux updates needed to be installed in say F35 to 
prevent these messages.
     Given that I got this in F41 which is an upgrade from F40, has a 
similar defect been introduced in Selinux in F41?

During the same dnf upgrade process I also got the following errors 
at the end, what log files is it referring to, or has anybody else 
received these messages and understands what they are?

[106/106] Removing gnome-initial-setup-0:47.1-1.fc41.x86_64 
                                                                                       100% 
|   2.0   B/s | 108.0   B |  00m52s
> > > Running trigger-install scriptlet:

systemd-0:256.8-1.fc41.x86_64c41.x86_64h
> > > Finished trigger-install scriptlet: systemd-0:256.8-1.fc41.x86_64
> > > Scriptlet output:
> > > Failed to start jobs: Failed to enqueue some jobs, see logs for

details: Invalid argument
> > > Running trigger-post-uninstall scriptlet:

systemd-0:256.8-1.fc41.x86_64c41.x86_64h
> > > Finished trigger-post-uninstall scriptlet:

systemd-0:256.8-1.fc41.x86_64
> > > Scriptlet output:
> > > Failed to start jobs: Failed to enqueue some jobs, see logs for

details: Invalid argument
> > >

regards,
Steve

[George N. White III]

On Fri, Nov 29, 2024 at 9:03 PM Stephen Morris 
wrote:
> > > > Failed to start jobs: Failed to enqueue some jobs, see logs for
>
> details: Invalid argument

Start with journalctl, which should tell you more about which jobs didn't
start.  Once you know which
jobs aren't starting you can determine if there are specific logs.  If
multiple jobs are failing you could
have a manually installed module that needs rebuilding or some resource
constraint (no space on
a mass storage device, out of memory, etc.