Re: bitmap font error on F38

George, My thanks to you for your detailed descriptions. Here are some findings: On Wed Apr26'23 11:25:02AM, George N. White III wrote: > From: "George N. White III" > Date: Wed, 26 Apr 2023 11:25:02 -0300 > To: Community support for Fedora users > Reply-To: Community support for Fedora users

Re: F38 and NUT -- SOLVED

FINALLY! It occurred to me to try this: [root@seveneves ups]# journalctl -u nut-driver@seveneves-ups Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]: Starting nut-driver@seveneves-ups.service - Network UPS Tools - device driver for NUT device 'seveneves-ups'... Apr 27 09:16:34

Re: F38 and NUT

Once upon a time, Greg Woods said: > Looks like I spoke too soon; I noticed that the nut-monitor service had > stopped running. I restarted it, and: NUT is a bit of a bear to get configured, but as far as the systemd portion, I only have nut.target enabled. It looks like that pulls in all the

Re: F38 and NUT

On Thu, Apr 27, 2023 at 9:38 AM Greg Woods wrote: > > On the positive side, the repetitive error: > Apr 26 12:49:09 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS > [seveneves-ups@localhost] failed - Driver not connected > > is no longer happening > Looks like I spoke too soon; I

Re: How to restart sudo rpmconf -a

On Thu, 27 Apr 2023 01:18:50 -0400 Jeffrey Walton wrote: > Hi Everyone, > > I dnf-system-upgraded my last machine from F37 to F38. I screwed up at > post-upgrade at 'sudo rpmconf -a'. [snip] > How do I restart rpmconf? I don't know if this will work, but you could go into /var/log/dnf.rpm.log

Re: F38 and NUT

Thanks to Jeff and Robert for the hint about the nut-driver-enumerator service. This is indeed new with F37; I looked at the F36 RPM and there is no nut-driver-enumerator.service file. On the F37 system the service file is there but it is disabled by default. I enabled it and rebooted, but it did

Post F38 upgrade/install printing in mirror image from HP P3015

Greetings, I'm stumbling through both an F38 upgrade and a new installation (the latter due to an F38 major upgrade problem). Thankfully, data has been saved and recovered. But problems arise (sort of like knowing how to drive a 2000 model year vehicle and then being confronted with a 2020

Re: Updating grub after dnf-system-upgrade

On Thu, 27 Apr 2023 01:47:58 -0400 Jeffrey Walton wrote: > (I have open questions about systems that claim both BIOS and UEFI, > but I have not been able to find answers. If I need to back up a bit, > then please say so). This may or may not be helpful, but when I make a "universal" boot USB

Re: F38 and NUT

On 4/26/23 18:30, Greg Woods wrote: Since upgrading to F37, I am having problems getting Nut to work properly. The errors I get from the journal are: Apr 26 17:01:42 seveneves.gregandeva.net nut-server[326151]: Can't connect to UPS [seveneves-ups]

Re: Why is updatedb running now?

> On 26 Apr 2023, at 20:51, Tom Horsley wrote: > > I copied /usr/lib/systemd/system/plocate-updatedb.timer to > /etc/systemd/system/plocate-updatedb.timer and changed > RandomizedDelaySec from 12h to 2h which is supposed to mean > it runs sometime between midnight and 2am. > > It did work

[389-users] Re: 389 DS memory growth

Hi Alexander, Memory footprint is larger with valgrind. You may reduce cache tuning to let your instance fit on the server. Disable autoh-tune (nsslapd-cache-autosize=0) and reduce nsslapd-cachememsize and nsslapd-dbcachesize. regards Thierry On 4/27/23 02:05, Nazarenko, Alexander wrote:

Re: Updating grub after dnf-system-upgrade

On 4/26/23 22:47, Jeffrey Walton wrote: I just dnf-upgraded my last system from F37 to F38. One of the post-upgrade task is "Update GRUB bootloader on BIOS systems" (https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/): Systems with the BIOS firmware have the GRUB RPM