RE: DMESG Messages after Sudo DNF Upgrade

[Stephen Morris]

*From:* Stephen Morris

*Sent:* Wednesday, 11 June 2025 at 09:28 UTC+10

*To:* [e-mail]

*Subject:* RE: DMESG Messages after Sudo DNF Upgrade
> *From:* Roger Heflin
>
> *Sent:* Wednesday, 11 June 2025 at 09:11 UTC+10
>
> *To:* Community support for Fedora users
>
> *Cc:* [e-mail]
>
> *Subject:* RE: DMESG Messages after Sudo DNF Upgrade
> > On Tue, Jun 10, 2025 at 6:04 PM Stephen Morris
> >  wrote:
> > > From:[e-mail]
> > >
> > > Sent: Wednesday, 11 June 2025 at 00:54 UTC+10
> > >
> > > To: Community support for Fedora users
> > >
> > > Cc:[e-mail]
> > >
> > > Subject: RE: DMESG Messages after Sudo DNF Upgrade
> > >
> > > Hi
> > >
> > > On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
> > >   With the systemd message below, are they known issues that are
> > >
> > > already in hand, or do I need to raise a bug report?
> > >
> > > No, but your machine is using I guess an old version of livesys.
> > >
> > > The current one in F42 is provided by the livesys-scripts RPM
> > > that defines properly the service as a systemd unit file,
> > >
> > > I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see
> > > rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the
> > > livesys-scripts F42 RPM.
> > >
> > > Thanks Francis. Livesys could be old, this instance of Fedora started life as F38, and has been upgraded to F42 through all the intermediate versions when they were announced as being stable available versions. If livesys is the issue, that raises the question of why was it not upgraded when the upgrades to each new version was done?
> > > Just relative to livesys as well, I ran sudo rpm -qf /etc/rc.d/init.d/livesys and that came back with the message that "file /etc/rc.d/init.d/livesys is not owned by any package".
> >
> > livesys is used on the livecd boot ISOs (I believe) and may not
> > actually be owned by anything, but get copied across when installing
> > from a livecd.  Several of my systems have given those messages from
> > time to time and I have just ignored them for the most part.

If the systemd warnings are because livesys hasn't been updated, and 
with the specified file not being owned by any package, how do I upgrade 
livesys given that standard system version upgrades haven't refreshed it?

regards,
Steve
> > The nvidia errors is because you upgrade to a new nvidia driver and
> > probably did not reboot.  So the loaded nvidia driver is a slightly
> > older version than the nvidia part being loaded in X/Wayland and it
> > reports this issue.
>
> Thanks Roger, I thought that might be the issue. I don't normally see 
> those messages in dmesg as I don't normally issue that command after 
> an update, it was just this time I say those messages because I was 
> trying to see why I was getting an "access denied" error on a /run 
> path, but I couldn't find anything.
>
> regards,
> Steve