error after upgrading from 41 to 42 /etc/selinux/targeted/contexts/files/file_contexts.bin: Old compiled fcontext format, skipp

Do an su command would show this and also saw in some other dnf operations. Found https://discussion.fedoraproject.org/t/curious-error-old-compiled-fc ontext-format-skipping/154135 Had a number of messages, but seems the .bin files are compiled with some Old format? I had messages about the

Re: Post-F42-Upgrade Error Messages

Jeffrey Walton: > > Maybe related to > > ? Sam Varshavchik: > Yes, that's what that's all about. And by about F50, give or take a release, > I expect that we'll get rid of the rest of ALL thise yucky different > directories altogether

Re: Post-F42-Upgrade Error Messages

Jeffrey Walton writes: On Mon, Apr 28, 2025 at 7:58 AM Tim Evans wrote: > > >>> Running trigger-post-uninstall scriptlet: > filesystem-0:3.18-36.fc42.x86_64 /usr/sbin cannot be merged, Found > /usr/sbin/dm_dso_reg_tool Maybe related to

Re: Post-F42-Upgrade Error Messages

On Mon, Apr 28, 2025 at 7:58 AM Tim Evans wrote: > > Since doing F41->F42 upgrades on a couple of my systems, I'm getting > error messages (on both) like these when doing dnf upgrades. They > reference different specific reasons, however, for the failure to merge. > >

Post-F42-Upgrade Error Messages

Since doing F41->F42 upgrades on a couple of my systems, I'm getting error messages (on both) like these when doing dnf upgrades. They reference different specific reasons, however, for the failure to merge. >>> Running trigger-post-uninstall scriptlet: filesystem-0:3.18-36.

Re: DNF Error Messages

> On 3 Apr 2025, at 22:33, Stephen Morris wrote: > > How do I find what it is talking about and how do I get them rectified? It is a known issue with some rpms that should eventually be fixed. The messages can be ignored. Barry -- ___ users mailing

DNF Error Messages

Hi, I did a DNF upgrade this morning, which was the first upgrade for about a week, and got the following errors from post-install scripts DNF runs. How do I find what it is talking about and how do I get them rectified? >>> Running trigger-install scriptlet: systemd-0:256.12-1.fc41.x86_64 >>>

Re: DNF Upgrade Error Messages

On Sun, Feb 2, 2025 at 5:41 PM Stephen Morris wrote: > > I did a dnf upgrade this morning and received the following messages. > Where do I look to determine what the errors are talking about? `journalctl -f` will probably do the trick. > >>> Running trigger-install scriptlet: systemd-0:256

DNF Upgrade Error Messages

Hi,     I did a dnf upgrade this morning and received the following messages. Where do I look to determine what the errors are talking about? Running trigger-install scriptlet: systemd-0:256.11-1.fc41.x86_64 Finished trigger-install scriptlet: systemd-0:256.11-1.fc41.x86_64 Scriptlet output: F

Re: DNF Upgrade Error

On Fri, 2025-01-10 at 08:55 +1100, Stephen Morris wrote: > I've attached the contents of all my repos. As a result of doing that > I've noticed that I have a fedora-rawhide.repo, which I am not aware > of having been created, and I have no need of packages from there. I can see it's not enabled, s

Re: DNF Upgrade Error

On 9/1/25 17:23, Tim via users wrote: On Thu, 2025-01-09 at 09:20 +1100, Stephen Morris wrote: so I changed the option to send the mail as html and text, which is the mail client will select which on to use. I didn't want to have to flip flop between sending options depending on where I was send

Re: DNF Upgrade Error

On 9/1/25 09:38, Jeffrey Walton wrote: On Wed, Jan 8, 2025 at 4:44 PM Stephen Morris wrote: Hi, With this mornings update, when DNF tried to download dnsmasq-0:2.90-4.fc41.x86_64 and firefox-0:134.0-1.fc41.x86_64, DNF got a 404 error from the mirror that looks to by my ISP's mirror

Re: DNF Upgrade Error

On Thu, 2025-01-09 at 09:20 +1100, Stephen Morris wrote: > so I changed the option to send the mail as html and text, which is > the mail client will select which on to use. > I didn't want to have to flip flop between sending options depending > on where I was sending the mail to. The reason you'

Re: DNF Upgrade Error

On Thu, 2025-01-09 at 09:20 +1100, Stephen Morris wrote: > On 9/1/25 09:11, Patrick O'Callaghan wrote: > > On Thu, 2025-01-09 at 08:43 +1100, Stephen Morris wrote: > > > I'm resending this message with the information as attachments as > > > embedding the messages in the mail caused the mail

Re: DNF Upgrade Error

On Wed, Jan 8, 2025 at 4:44 PM Stephen Morris wrote: > > Hi, > With this mornings update, when DNF tried to download > dnsmasq-0:2.90-4.fc41.x86_64 and firefox-0:134.0-1.fc41.x86_64, DNF got a 404 > error from the mirror that looks to by my ISP's mirror, and after gett

Re: DNF Upgrade Error

On 9/1/25 09:11, Patrick O'Callaghan wrote: On Thu, 2025-01-09 at 08:43 +1100, Stephen Morris wrote: I'm resending this message with the information as attachments as embedding the messages in the mail caused the mail to be moderator held because it was longer than 60KB. It's still one e

Re: DNF Upgrade Error

On Thu, 2025-01-09 at 08:43 +1100, Stephen Morris wrote: > I'm resending this message with the information as attachments as > embedding the messages in the mail caused the mail to be moderator held > because it was longer than 60KB. > It's still one email message and it's the total size t

DNF Upgrade Error

Hi,     With this mornings update, when DNF tried to download dnsmasq-0:2.90-4.fc41.x86_64 and firefox-0:134.0-1.fc41.x86_64, DNF got a 404 error from the mirror that looks to by my ISP's mirror, and after getting that error it did not appear to try to download those packages from any

Re: VirtualBox no longer working? Loads but gets error message.

On Sun, Dec 22, 2024, 10:44 Fernando Cassia wrote: > > > On Fri, Dec 20, 2024, 14:14 Samuel Sieb wrote: > >> On 12/19/24 3:33 PM, Michael D. Setzer II via users wrote: >> > Used it a couple weeks ago, but now get this error message went >> > trying to start

Re: VirtualBox no longer working? Loads but gets error message.

On Sat, Dec 21, 2024, 19:22 Allan via users wrote: > > > Just create a VirtualBox.conf file in /etc/modprobe.d/ > > With this line inside: > blacklist kvm-intel > > and the problem should be fixed > Thanks Allan. Appreciate it FC -- ___ users mailin

Re: VirtualBox no longer working? Loads but gets error message.

On Fri, Dec 20, 2024, 14:14 Samuel Sieb wrote: > On 12/19/24 3:33 PM, Michael D. Setzer II via users wrote: > > Used it a couple weeks ago, but now get this error message went > > trying to start. > > > > VirtualBox can't operate in VMX root mode. > > P

Re: VirtualBox no longer working? Loads but gets error message.

På Fri, 20 Dec 2024 19:25:46 +1000 "Michael D. Setzer II via users" skrev: > On 19 Dec 2024 at 23:50, Samuel Sieb wrote: > > Date sent:Thu, 19 Dec 2024 23:50:29 -0800 > Subject: Re: VirtualBox no longer working? Loads but >

Re: VirtualBox no longer working? Loads but gets error message.

On Fri, 2024-12-20 at 09:43 -0800, Doug Herr wrote: > On Thu, Dec 19, 2024, at 9:03 PM, Samuel Sieb wrote: > [snip] > > Why can't you use kvm? > > I also use VirtualBox. Have installed and experimented with KVM a number of > times. It worked, but it did not do anything that VirtualBox was not doi

Re: VirtualBox no longer working? Loads but gets error message.

On 12/20/24 1:25 AM, Michael D. Setzer II wrote: On 19 Dec 2024 at 23:50, Samuel Sieb wrote: On 12/19/24 11:37 PM, Ron Yorston wrote: (I only use VirtualBox occasionally, to run a Windows XP VM which I've never managed to get working with KVM. Otherwise I prefer Virtual Machine Manager.) I'v

Re: VirtualBox no longer working? Loads but gets error message.

On Thu, Dec 19, 2024, at 9:03 PM, Samuel Sieb wrote: [snip] > Why can't you use kvm? I also use VirtualBox. Have installed and experimented with KVM a number of times. It worked, but it did not do anything that VirtualBox was not doing for me already. I am fully used to VirtualBox so it is easie

Re: VirtualBox no longer working? Loads but gets error message.

On 19 Dec 2024 at 21:03, Samuel Sieb wrote: Date sent: Thu, 19 Dec 2024 21:03:23 -0800 Subject:Re: VirtualBox no longer working? Loads but gets error message. To: users@lists.fedoraproject.org From: Samuel Sieb Send reply to

Re: VirtualBox no longer working? Loads but gets error message.

On 12/19/24 3:33 PM, Michael D. Setzer II via users wrote: Used it a couple weeks ago, but now get this error message went trying to start. VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot. (VERR_VMX_IN_VMX_ROOT_MODE). Fo

Re: VirtualBox no longer working? Loads but gets error message.

On 19 Dec 2024 at 23:50, Samuel Sieb wrote: Date sent: Thu, 19 Dec 2024 23:50:29 -0800 Subject:Re: VirtualBox no longer working? Loads but gets error message. To: users@lists.fedoraproject.org From: Samuel Sieb Send reply to

Re: VirtualBox no longer working? Loads but gets error message.

On 12/19/24 11:37 PM, Ron Yorston wrote: The 6.12 kernel has changed the way virtualisation modules are loaded. Some discussion, with workarounds, here: https://www.virtualbox.org/ticket/22248 https://lore.kernel.org/kvm/zwqjusole6swa...@google.com/T/ I was able to get VirtualBox to st

Re: VirtualBox no longer working? Loads but gets error message.

On 19 Dec 2024 at 20:18, Jeffrey Walton wrote: From: Jeffrey Walton Date sent: Thu, 19 Dec 2024 20:18:53 -0500 Subject:Re: VirtualBox no longer working? Loads but gets error message. To: mi...@guam.net, Community support

Re: VirtualBox no longer working? Loads but gets error message.

The 6.12 kernel has changed the way virtualisation modules are loaded. Some discussion, with workarounds, here: https://www.virtualbox.org/ticket/22248 https://lore.kernel.org/kvm/zwqjusole6swa...@google.com/T/ I was able to get VirtualBox to start by unloading the kvm_intel module with th

Re: VirtualBox no longer working? Loads but gets error message.

On Thu, Dec 19, 2024 at 7:00 PM Michael D. Setzer II via users wrote: > > On 20 Dec 2024 at 9:33, Michael D. Setzer II via user wrote: > [...] > > Used it a couple weeks ago, but now get this error message went > > trying to start. > > > > VirtualBox can'

Re: VirtualBox no longer working? Loads but gets error message.

On 20 Dec 2024 at 9:33, Michael D. Setzer II via user wrote: To: users@lists.fedoraproject.org Date sent: Fri, 20 Dec 2024 09:33:06 +1000 Subject:VirtualBox no longer working? Loads but gets error message. Priority: normal Send reply

VirtualBox no longer working? Loads but gets error message.

Used it a couple weeks ago, but now get this error message went trying to start. VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot. (VERR_VMX_IN_VMX_ROOT_MODE). Found a link that talks about fixing on Ubuntu, but options

Re: dnf error on F41 update this morning

On 7/12/24 00:45, Neal Becker wrote: On Thu, Dec 5, 2024 at 7:37 PM Neal Becker wrote: Did you find any problems other than the message? I haven't seen any problems that were noticeable to me, and I've done several updates since the one in question and as yet haven't had a re-occurrenc

Re: dnf error on F41 update this morning

I got the same message again with dnf update this morning. Journalctl shows this: Dec 06 08:44:03 nbecker0 systemd[531438]: Reached target exit.target - Exit the Session. Dec 06 08:44:03 nbecker0 systemd[1]: user@0.service: Deactivated successfully. Dec 06 08:44:03 nbecker0 systemd[1]: Stopped use

Re: dnf error on F41 update this morning

Did you find any problems other than the message? On Thu, Dec 5, 2024 at 4:04 PM Stephen Morris wrote: > On 6/12/24 02:09, Barry Scott wrote: > > > > On 5 Dec 2024, at 13:22, Neal Becker > wrote: > > I didn't check the logs because I'm not sure what log to look for. > > > Try the system journa

Re: dnf error on F41 update this morning

On 6/12/24 02:09, Barry Scott wrote: On 5 Dec 2024, at 13:22, Neal Becker wrote: I didn't check the logs because I'm not sure what log to look for. Try the system journal. But give you should reboot to have systemd update take effect you could just check that all services are running aft

Re: dnf error on F41 update this morning

> On 5 Dec 2024, at 13:22, Neal Becker wrote: > > I didn't check the logs because I'm not sure what log to look for. Try the system journal. But give you should reboot to have systemd update take effect you could just check that all services are running after the reboot. `systemctl --failed`

dnf error on F41 update this morning

>>> Running trigger-install scriptlet: systemd-0:256.9-2.fc41.x86_64c41.x86_64h46_64 >>> Finished trigger-install scriptlet: systemd-0:256.9-2.fc41.x86_64 >>> Scriptlet output: >>> Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument >>> I didn't check the logs

Re: F41 DNF bogus error

> On 23 Nov 2024, at 22:18, Go Canes wrote: > > I have not upgraded to F41 but from what I have seen on the list, it > seems to me that: > 1) dnf5 is implemented in python Dnf4 is python, dnf5 is c++. Barry -- ___ users mailing list -- users@lists

Re: F41 DNF bogus error

Go Canes wrote: > I have not upgraded to F41 but from what I have seen on the list, it > seems to me that: > 1) dnf5 is implemented in python > 2) dnf5 is using "argparse" to parse command line options > 3) dnf5 is using "argparse subparsers" to implement the dnf5 commands It is true that dnf5 par

Re: F41 DNF bogus error

On Sat, 2024-11-23 at 22:22 +, Patrick O'Callaghan wrote: > According to the man page for dnf5 the command has to come first, i.e. > it's 'dnf COMMAND OPTIONS ARGS', so your example would be wrong even if > --skip-unavailable were an option (which apparently it isn't). In fact it's an option o

Re: F41 DNF bogus error

Go Canes wrote: >I wrote: >> # dnf -y --skip-unavailable install pkg1 pkg2 pkg3 >> Unknown argument "--skip-unavailable" for command "dnf5". >First, I agree the "helpful" message could and should be better. > >... options are going to be positional relative to the >commands. Until "install" is

Re: F41 DNF bogus error

Dave Close wrote on 2024/11/24 6:53: # dnf -y install pkg1 pkg2 pkg3 Updating and loading repositories: ... Repositories loaded. Failed to resolve the transaction: No match for argument: pkg3 You can try to add to command line: --skip-unavailable to skip unavailable packages # dnf -y --skip

Re: F41 DNF bogus error

On Sat, 2024-11-23 at 13:53 -0800, Dave Close wrote: > # dnf -y install pkg1 pkg2 pkg3 > Updating and loading repositories: > ... > Repositories loaded. > Failed to resolve the transaction: > No match for argument: pkg3 > You can try to add to command line: > --skip-unavailable to skip unavailab

Re: F41 DNF bogus error

On Sat, Nov 23, 2024 at 4:54 PM Dave Close wrote: > > # dnf -y install pkg1 pkg2 pkg3 > Updating and loading repositories: > ... > Repositories loaded. > Failed to resolve the transaction: > No match for argument: pkg3 > You can try to add to command line: > --skip-unavailable to skip unavailab

F41 DNF bogus error

# dnf -y install pkg1 pkg2 pkg3 Updating and loading repositories: ... Repositories loaded. Failed to resolve the transaction: No match for argument: pkg3 You can try to add to command line: --skip-unavailable to skip unavailable packages # dnf -y --skip-unavailable install pkg1 pkg2 pkg3 Unkno

Re: Python Error From DNF

On 10/23/24 2:56 PM, Stephen Morris wrote: On 24/10/24 08:41, Stephen Morris wrote: Hi,     Since the last couple of updates when I run "sudo dnf upgrade" I get the following python error, is someone able to tell me what it means please? Traceback (most recent call last):  File

Re: Python Error From DNF

On 24/10/24 08:41, Stephen Morris wrote: Hi,     Since the last couple of updates when I run "sudo dnf upgrade" I get the following python error, is someone able to tell me what it means please? Traceback (most recent call last):  File "/usr/lib/python3.12/site-packages/dnf/p

Python Error From DNF

Hi,     Since the last couple of updates when I run "sudo dnf upgrade" I get the following python error, is someone able to tell me what it means please? Traceback (most recent call last):  File "/usr/lib/python3.12/site-packages/dnf/plugin.py", line 108, in _calle

Re: AVC error in cron script - SOLVED?

On Mon, 2024-09-16 at 17:40 +0100, Barry wrote: > > > On 16 Sep 2024, at 10:48, Patrick O'Callaghan wrote: > > > > I suspect the real problem is that the cron line is running as root, > > but Apache wants to run as the apache user. I'll try using 'crontab -u > > apache ...' to see if that makes

Re: AVC error in cron script - SOLVED?

On Mon, Sep 16, 2024 at 12:41 PM Barry wrote: > > > On 16 Sep 2024, at 10:48, Patrick O'Callaghan wrote: > > > > I suspect the real problem is that the cron line is running as root, > > but Apache wants to run as the apache user. I'll try using 'crontab -u > > apache ...' to see if that makes any

Re: AVC error in cron script - SOLVED?

> On 16 Sep 2024, at 10:48, Patrick O'Callaghan wrote: > > I suspect the real problem is that the cron line is running as root, > but Apache wants to run as the apache user. I'll try using 'crontab -u > apache ...' to see if that makes any difference. You said the the apachectl just rund a sys

Re: AVC error in cron script - SOLVED?

On Thu, 2024-09-12 at 10:51 +0100, Patrick O'Callaghan wrote: > On Thu, 2024-09-12 at 12:14 +0930, Tim via users wrote: > > On Wed, 2024-09-11 at 12:19 +0100, Patrick O'Callaghan wrote: > > > Turns out I don't need any of this. If I substitute my original crontab > > > line for one that simply call

Re: AVC error in cron script - SOLVED?

On Thu, 2024-09-12 at 12:14 +0930, Tim via users wrote: > On Wed, 2024-09-11 at 12:19 +0100, Patrick O'Callaghan wrote: > > Turns out I don't need any of this. If I substitute my original crontab > > line for one that simply calls a Shell script which in turn calls > > apachectl, then it all works

Re: AVC error in cron script - SOLVED?

On Wed, 2024-09-11 at 12:19 +0100, Patrick O'Callaghan wrote: > Turns out I don't need any of this. If I substitute my original crontab > line for one that simply calls a Shell script which in turn calls > apachectl, then it all works with no AVC. ENVironment differences? The crontab versus your

Re: AVC error in cron script - SOLVED?

On Tue, 2024-09-10 at 11:55 -0500, Thomas Cameron wrote: > On 9/10/24 5:30 AM, Patrick O'Callaghan wrote: > > I have a cron line that attempts to restart httpd every morning, but > > it's failing with an AVC error: > > > > Sep 10 08:00:00 Bree CROND[723189

Re: AVC error in cron script

On 9/10/24 5:30 AM, Patrick O'Callaghan wrote: I have a cron line that attempts to restart httpd every morning, but it's failing with an AVC error: Sep 10 08:00:00 Bree CROND[723189]: (root) CMD ((echo "$(date): Apache: calling restart") >> /var/log/httpd/my-log &

Re: AVC error in cron script

On Tue, 2024-09-10 at 13:45 +0100, Barry wrote: > > > On 10 Sep 2024, at 11:31, Patrick O'Callaghan wrote: > > > > I have a cron line that attempts to restart httpd every morning, but > > it's failing with an AVC error: > > > > Sep 10 08:00

Re: AVC error in cron script

> On 10 Sep 2024, at 11:31, Patrick O'Callaghan wrote: > > I have a cron line that attempts to restart httpd every morning, but > it's failing with an AVC error: > > Sep 10 08:00:00 Bree CROND[723189]: (root) CMD ((echo "$(date): Apache: > calling restar

AVC error in cron script

I have a cron line that attempts to restart httpd every morning, but it's failing with an AVC error: Sep 10 08:00:00 Bree CROND[723189]: (root) CMD ((echo "$(date): Apache: calling restart") >> /var/log/httpd/my-log && /usr/sbin/apachectl restart) Sep 10 08:00:00

Re: Calibre error

On Sat, 2024-09-07 at 13:44 -0700, Mike Wright wrote: > On 9/6/24 06:28, George N. White III wrote: > > On Fri, Sep 6, 2024 at 12:04 AM Tim via users > > > > wrote: > > > > > On Thu, 2024-09-05 at 13:11 -0400, Jeffrey Walton wrote: > > > > This made my radar today: > > > > < > > > https://jfrog.

Re: Calibre error

On 9/6/24 06:28, George N. White III wrote: On Fri, Sep 6, 2024 at 12:04 AM Tim via users wrote: On Thu, 2024-09-05 at 13:11 -0400, Jeffrey Walton wrote: This made my radar today: < https://jfrog.com/blog/revival-hijack-pypi-hijack-technique-exploited-22k-packages-at-risk/ . It's like Peter

Re: Calibre error

On Fri, Sep 6, 2024 at 12:04 AM Tim via users wrote: > On Thu, 2024-09-05 at 13:11 -0400, Jeffrey Walton wrote: > > This made my radar today: > > < > https://jfrog.com/blog/revival-hijack-pypi-hijack-technique-exploited-22k-packages-at-risk/ > >. > > It's like Peter Gutmann said: "A great many of

Re: Calibre error

On Thu, 2024-09-05 at 13:11 -0400, Jeffrey Walton wrote: > This made my radar today: > . > It's like Peter Gutmann said: "A great many of today’s security > technologies are “secure” only because no-one has

Re: Calibre error

de. > > That doesn't seem to correspond with the man page, which has: > > --require-virtualenvAllow pip to only run in a virtual environment; > exit with an error otherwise. > > However there is no indication that this is the default, and when I run > p

Re: Calibre error

On Thu, Sep 5, 2024 at 9:49 AM Barry wrote: > > > On 5 Sep 2024, at 12:15, Patrick O'Callaghan wrote: > > > > I believe there is an ongoing discussion about how pip should be more > > integrated with packaging systems to avoid this kind of confusion. > > Not sure what you are referring to, all di

Re: Calibre error

accepted solution. > > Also pip was changed to prevent you installing outside a venv without > explicit command option to override. That doesn't seem to correspond with the man page, which has: --require-virtualenv Allow pip to only run in a virtual environment; exit with

Re: Calibre error

> On 5 Sep 2024, at 12:15, Patrick O'Callaghan wrote: > > I believe there is an ongoing discussion about how pip should be more > integrated with packaging systems to avoid this kind of confusion. Not sure what you are referring to, all discussion are long over. The current state is that you

Re: Calibre error

On Thu, 2024-09-05 at 08:04 -0300, George N. White III wrote: > On Tue, Sep 3, 2024 at 3:57 PM Samuel Sieb wrote: > > > On 2024-09-03 04:37, George N. White III wrote: > > > > > > Calibre is available as flatpaks. > > > > The Fedora packaged Calibre works fine. The issue here is a pip > > inst

Re: Calibre error

On Tue, Sep 3, 2024 at 3:57 PM Samuel Sieb wrote: > On 2024-09-03 04:37, George N. White III wrote: > > > > Calibre is available as flatpaks. > > The Fedora packaged Calibre works fine. The issue here is a pip > installed library overriding the system one. > Flatpaks should not be affected by s

Re: Calibre error

On 2024-09-03 04:37, George N. White III wrote: On Mon, Sep 2, 2024 at 7:33 AM Will McDonald > wrote: If you pip install stuff in a Python virtual environment, that can help isolate custom modules further from your normal/system Python runtimes. http

Re: Calibre error

On Tue, 2024-09-03 at 08:37 -0300, George N. White III wrote: > On Mon, Sep 2, 2024 at 7:33 AM Will McDonald wrote: > > > > > If you pip install stuff in a Python virtual environment, that can help > > isolate custom modules further from your normal/system Python runtimes. > > > > https://docs.

Re: Calibre error

On Mon, Sep 2, 2024 at 7:33 AM Will McDonald wrote: > > If you pip install stuff in a Python virtual environment, that can help > isolate custom modules further from your normal/system Python runtimes. > > https://docs.python.org/3/library/venv.html > https://realpython.com/python-virtual-environ

Re: Calibre error

On Mon, 2024-09-02 at 10:40 -0700, Samuel Sieb wrote: > On 9/2/24 2:20 AM, Patrick O'Callaghan wrote: > > On Sun, 2024-09-01 at 15:19 -0700, Samuel Sieb wrote: > > > > However I also have mingw64-libxml2-2.12.7-1.fc40.noarch, which was > > > > installed together with Wine. I assume that's the root

Re: Calibre error

On 9/2/24 2:20 AM, Patrick O'Callaghan wrote: On Sun, 2024-09-01 at 15:19 -0700, Samuel Sieb wrote: However I also have mingw64-libxml2-2.12.7-1.fc40.noarch, which was installed together with Wine. I assume that's the root of the problem, but I can't solve it without uninstalling Wine. That wo

Re: Calibre error

On Mon, 2024-09-02 at 14:07 +0100, Barry Scott wrote: > > > On 2 Sep 2024, at 12:13, Patrick O'Callaghan wrote: > > > > Yes, I'm vaguely aware of that possibility though I've never had to use > > it up to now, i.e. everything has "just worked". > > Usually on Fedora it has just worked in the pa

Re: Calibre error

> On 2 Sep 2024, at 12:13, Patrick O'Callaghan wrote: > > Yes, I'm vaguely aware of that possibility though I've never had to use > it up to now, i.e. everything has "just worked". Usually on Fedora it has just worked in the past. But there are too many edge cases where pip installing a module

Re: Calibre error

On Mon, 2024-09-02 at 11:32 +0100, Will McDonald wrote: > > $ ls .local/lib/python3.12/site-packages/ > > configparser-7.0.0-py3.12.egg  lxml-4.9.4.dist-info   numpy.libs > >   pillow.libs    _webrtcvad.cpython-312-x86_64-linux-gnu.so > > easy-install.pth   numpy

Re: Calibre error

On Mon, 2 Sept 2024 at 10:21, Patrick O'Callaghan wrote: > On Sun, 2024-09-01 at 15:19 -0700, Samuel Sieb wrote: > > > However I also have mingw64-libxml2-2.12.7-1.fc40.noarch, which was > > > installed together with Wine. I assume that's the root of the problem, > > > but I can't solve it withou

Re: Calibre error

On Sun, 2024-09-01 at 15:19 -0700, Samuel Sieb wrote: > > However I also have mingw64-libxml2-2.12.7-1.fc40.noarch, which was > > installed together with Wine. I assume that's the root of the problem, > > but I can't solve it without uninstalling Wine. > > That won't be a problem because those lib

Re: Calibre error

On 9/1/24 3:02 PM, Patrick O'Callaghan wrote: On Sun, 2024-09-01 at 14:35 -0700, Samuel Sieb wrote: On 9/1/24 2:11 PM, Patrick O'Callaghan wrote: On installing the latest version of Calibre (7.17.3) I get this error: RuntimeError: html5-parser and lxml are using different versions

Re: Calibre error

On Sun, 2024-09-01 at 14:35 -0700, Samuel Sieb wrote: > On 9/1/24 2:11 PM, Patrick O'Callaghan wrote: > > On installing the latest version of Calibre (7.17.3) I get this error: > > > > RuntimeError: html5-parser and lxml are using different versions of > > lib

Re: Calibre error

On 9/1/24 2:11 PM, Patrick O'Callaghan wrote: On installing the latest version of Calibre (7.17.3) I get this error: RuntimeError: html5-parser and lxml are using different versions of libxml2. This happens commonly when using pip installed versions of lxml. Use pip install --no-binary

Calibre error

On installing the latest version of Calibre (7.17.3) I get this error: $ calibre Traceback (most recent call last): File "/usr/bin/calibre", line 21, in sys.exit(calibre()) ^ File "/usr/lib64/calibre/calibre/gui_launch.py", line 73, in calibre

Re: F40 Install: Failed to fork off sandboxing environment for executing generators: Protocol error

Hi, > This is on a PowerEdge R720, booting from a virtual DVD ISO. > > > I used a USB stick with Fedora live image on it to install on a R720, > likely it was f37 or f38 as after the first install I did dnf > system-upgrade. > > I think booting an ISO was tried and failed, but its too long ago and

Re: F40 Install: Failed to fork off sandboxing environment for executing generators: Protocol error

> On 21 Jul 2024, at 12:40, Alex wrote: > > This is on a PowerEdge R720, booting from a virtual DVD ISO. I used a USB stick with Fedora live image on it to install on a R720, likely it was f37 or f38 as after the first install I did dnf system-upgrade. I think booting an ISO was tried and fai

F40 Install: Failed to fork off sandboxing environment for executing generators: Protocol error

Hi, I have received the following error very early on in the install of fedora40 server: Failed to fork off sandboxing environment for executing generators: Protocol error [!!] Failed to start up manager. Exiting PID 1... This is on a PowerEdge R720, booting from a virtual DVD ISO. This

Re: Error (19) after reboot RHEL9.2 server: Replica has different database generation ID, remote replica may need to be initialized (RUV error

e supplier server to enable patches > 3. Observe the following error in the replication agreement: > {"state": "red", "ldap_rc": "0", "ldap_rc_text": "Success", "repl_rc": "19", > "repl_rc_text": &qu

Error (19) after reboot RHEL9.2 server: Replica has different database generation ID, remote replica may need to be initialized (RUV error

Hello, colleagues, After moving to RHEL9.2 and 389-ds-base-2.4.5-8.el9_4.x86_64 the following behavior is observed: The system is Supplier-consumer. 1. Patch RHEL9.2 supplier server 2. Reboot the supplier server to enable patches 3. Observe the following error in the replication agreement

Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end??

On 19/05/2024 18:08, Michael D. Setzer II wrote: On 19 May 2024 at 14:50, John Pilkington wrote: Date sent: Sun, 19 May 2024 14:50:55 +0100 Subject:Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end?? To: users

Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end??

On 19 May 2024 at 14:50, John Pilkington wrote: Date sent: Sun, 19 May 2024 14:50:55 +0100 Subject:Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end?? To: users@lists.fedoraproject.org From

Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end??

On 19/05/2024 09:48, Michael D. Setzer II via users wrote: Error: Transaction test error: file /usr/share/gir-1.0/GLib-2.0.gir conflicts between attempted installs of glib2-devel-2.80.2-1.fc40.i686 and glib2-devel-2.80.2-1.fc40.x86_64 # rpm -qa | grep glib2-devel glib2-devel-2.78.6-1.fc39

Updated 3 machines from 39 to 40, but on 4th machine get this error at end??

Error: Transaction test error: file /usr/share/gir-1.0/GLib-2.0.gir conflicts between attempted installs of glib2-devel-2.80.2-1.fc40.i686 and glib2-devel-2.80.2-1.fc40.x86_64 # rpm -qa | grep glib2-devel glib2-devel-2.78.6-1.fc39.x86_64 glib2-devel-2.78.6-1.fc39.i686 Don't know if ot

Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)

I usually keep the old version. From time to time I do a diff check to see if there is something new and research the change. On Sat, May 4, 2024 at 8:06 PM Jeffrey Walton wrote: > > > On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote: > >> Don' know. I have been dnf upgrading this system almos

Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)

On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote: > Don' know. I have been dnf upgrading this system almost since Fedora was > simple digits. .🤔 > I am planning a new build for F40 and definitely clean install it. > There are post-upgrade tasks that should be performed to keep the system tidy.

Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)

; > I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. > > Once in this kernel, I dnf reinstalled it and everything seems to have > > worked fine. > > dnf did not show any error and I had journalctl -f on another terminal > > and did not see any error

Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)

On 5/4/24 1:26 AM, Javier Perez wrote: Ok, I think I solved it. I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. Once in this kernel, I dnf reinstalled it and everything seems to have worked fine. dnf did not show any error and I had journalctl -f on another terminal and

Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)

Ok, I think I solved it. I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. Once in this kernel, I dnf reinstalled it and everything seems to have worked fine. dnf did not show any error and I had journalctl -f on another terminal and did not see any error either. I am going

  1   2   3   4   5   6   7   8   9   10   >