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
> 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
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
On Wed, 3 Apr 2024, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also has to
be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EF
On 4/8/24 08:19, Robert McBroom via users wrote:
On 4/3/24 5:45 PM, Stephen Morris wrote:
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah! W
On 4/3/24 5:45 PM, Stephen Morris wrote:
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be expl
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EFI pa
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also has to
be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EFI partition.
--
Michael henne...@mail.cs.nd
On 4/2/24 22:19, Michael Hennebry wrote:
While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso ,
I got the following:
Failed to find a suitable stage1 device:
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type None;
EFI System
While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso ,
I got the following:
Failed to find a suitable stage1 device:
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type None;
EFI System Partition cannot be of type NTFS;
EFI System
> On 13 Mar 2024, at 17:12, Neal Becker wrote:
>
> I need to see the lines before this, and maybe after. Any ideas?
Once I find a time of interest I have use the —since and - before to get a time
bounded slice of logs.
Barry
--
___
users mailing
On 3/13/24 14:42, Joe Zeff wrote:
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has
-A and -B for showing "n" number of lines After or Before the matched
context.
If you need to pass options to grep, consider piping the output of
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff <mailto:j...@zeff.us>> wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
> Failed to start jobs: Failed to enqueue some jobs, see logs for
details:
> Invalid argument
>
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has
-A and -B for showing "n" number of lines After or Before the matched
context.
If you need to pass options to grep, consider piping the output of
journalctl through grep instead.
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument
Should I worry? I don't even know what armadillo is.
Did you lo
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote:
> On 03/12/2024 12:33 PM, Neal Becker wrote:
> > Failed to start jobs: Failed to enqueue some jobs, see logs for details:
> > Invalid argument
> >
> > Should I worry? I don't even know what armadillo is.
>
&g
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look at the logs and if not, why not? Checking Wikipedia,
armadillo is a C++ library for l
Running today's dnf update:
...
Running scriptlet: grub2-common-1:2.06-118.fc39.noarch
32/32
Running scriptlet: armadillo-12.8.0-1.fc39.x86_64
32/32
Failed to start jobs: Failed to en
On 9/25/23 23:46, Kaushal Shriyan wrote:
I am running Red Hat Enterprise Linux release 8.7 (Ootpa) OS in
production environment. I have enabled both epel in /etc/yum.repos.d
directory
There is a proxy server setup in the network. I have whitelisted the
below wildcard URLs as listed as per ep
Hi,
I am running Red Hat Enterprise Linux release 8.7 (Ootpa) OS in production
environment. I have enabled both epel in /etc/yum.repos.d directory
There is a proxy server setup in the network. I have whitelisted the below
wildcard URLs as listed as per epel repo.
https://*.fedoraproject.org
*#
On Thu, 2023-07-27 at 17:36 +, Cătălin George Feștilă wrote:
> I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
> dnf group install tells me : Failed to resolve the transaction :
> Is Deepin Desktop Environment available on Fedora 39 ?
F39 is unreleased software. Y
I test again today with the same command and return more than 0 B, ...
dnf install deepin-desktop
and works well, you can find the result on my blogspot about fedora linux.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an e
On 7/27/23 10:36, Cătălin George Feștilă wrote:
I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
dnf group install tells me : Failed to resolve the transaction :
Is Deepin Desktop Environment available on Fedora 39 ?
Paste the full error message
On Thu, 2023-07-27 at 17:36 +, Cătălin George Feștilă wrote:
> I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
The Chinese spyware?
Well, who knows if that's really true (then, now, or in the future).
But considering it's Chinese heritage, I wouldn't touch it with a ten
fo
If I run :
dnf group list
the deepin-desktop is show with yes on Instaled column.
I try to update or install again but the result is :
...
Deepin Desktop Environment
...
After this operation 0 B will be used (install 0 B, remove 0 B).
Is this ok ...
and the result is nothing happend.
__
I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
dnf group install tells me : Failed to resolve the transaction :
Is Deepin Desktop Environment available on Fedora 39 ?
___
users mailing list -- users@lists.fedoraproject.org
To
On 17 Jul 2023 at 17:29, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 17:29:17 -0400
Subject:works fine - Re: F38 install fails on a Lenovo x120e - Failed
to set
new efi boot traget
From: Robert Moskowitz
To: Community support for Fedora users ,
Roger
working!
On 7/17/23 15:40, Robert Moskowitz wrote:
I was getting ready to try again.
I pulled the CD drive and tried to get into bios setup, but was not
fast enough and it started booting F38!
It got as far as a things like
[Failed] Failed to start systemd-login.service - User Login Management
On 7/17/23 16:07, Michael D. Setzer II wrote:
First computer was a 1963 IBM 1130 with punch cards back in
1975. So started with old machines that still were working.. High
School..
I started with a teletype 55 baudot to a GE MarkV in '66. Best I can
figure out was our school (Euclid OH) w
On 17 Jul 2023 at 11:25, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 11:25:31 -0400
To: Community support for Fedora users
From: Robert Moskowitz
Subject:F38 install fails on a Lenovo x120e - Failed to set
new efi boot
I was getting ready to try again.
I pulled the CD drive and tried to get into bios setup, but was not fast
enough and it started booting F38!
It got as far as a things like
[Failed] Failed to start systemd-login.service - User Login Management.
then a bunch more and hung.
So I am going to
on "Installing boot
> loader".
> >>
> >> If finally came back with a dialog box with an error of:
> >>
> >> The following error occurred while installing the boot loader. The
> >> system will not be bootable. Would you like to ignore this an
re this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number of ver of Fedora on it. It was booting F22 just fine, it seemed
but now it is all gone...
hour with the spindizzy on "Installing boot loader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to s
On Mon, Jul 17, 2023 at 1:56 PM Robert Moskowitz wrote:
>
> I just recalled. There was a /boot/efi partition on the old F22 setup.
>
> But booting up F37 live now.
If you haven't done so, now would be a good time to update the
laptop's firmware. Get on the latest version.
And the kernel docs ha
tinue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number of ver of Fedora on it. It was booting F22 just fine, it seemed
but now it is all gone...
You can ch
came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No
t; If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and continue
> with the installation?
>
> Failed to set new efi boot target. This is most
It has the AMD E-350 duo core CPU which I am pretty sure is x64.
On 7/17/23 12:58, Barry wrote:
On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
What should I do at this point. It IS an old system that has had a number of
ver of Fedora on it. It was booting F22 just fine, it seemed but n
oot
loader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and
continue
with the installation?
Failed to set new efi boot target. This is most likely a ker
> On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
>
> What should I do at this point. It IS an old system that has had a number of
> ver of Fedora on it. It was booting F22 just fine, it seemed but now it is
> all gone...
Is it a 64bit system or 32bit? Fedora needs 64bit now.
Barry
gt;
> If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and
> continue
> with the installation?
>
> Failed to set new efi boot target.
alling the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number
he.service - dnf makecache...
nov 02 21:06:14 systemd[1]: systemd-suspend.service: Main process exited,
code=exited, status=1/FAILURE
nov 02 21:06:14 systemd[1]: systemd-suspend.service: Failed with result
'exit-code'.
nov 02 21:06:14 systemd[1]: Failed to start systemd-suspend.service - S
On Tue, Nov 1, 2022 at 6:14 PM Dario Lesca wrote:
>
> I have resolve this problem follow this Arch Linux howto:
> https://wiki.archlinux.org/title/Power_management#Hybrid-sleep_on_suspend_or_hibernation_request
>
> I have add these lines at the end of /etc/systemd/sleep.conf file
> SuspendMode=sus
=disk
Now suspend work fine every time
Thanks
Dario
Il giorno mer, 14/09/2022 alle 09.25 +0200, Dario Lesca ha scritto:
> When I try suspend with "systemctl suspend" my notebook Fedora 36
> sometime do not suspend with "PM: Some devices failed to suspend, or
> early wa
Il giorno mer, 14/09/2022 alle 22.47 +0100, Patrick O'Callaghan ha
scritto:
> Are you sure it isn't the default?
Yes You're right.
On my system the flag is set to 1 by default:
[lesca@dodo ~]$ cat /sys/power/sync_on_suspend
1
And other flag is set to sync and suspend
[lesca@dodo ~]$ grep -i susp
On Wed, Sep 14, 2022 at 9:14 PM stan via users <
users@lists.fedoraproject.org> wrote:
> grep -i suspend /boot/config* | less
>
> I have
> # CONFIG_SUSPEND is not set
> CONFIG_USB_AUTOSUSPEND_DELAY=2
>
> But my kernel is custom configured, so you should check your kernels.
>
Fresh install on an o
On Wed, 14 Sep 2022 20:30:11 +0200
Dario Lesca wrote:
> Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha scritto:
> > Summary: You have to either issue a sync before suspend, or turn on
> > autosync in the kernel before suspend.
>
> Thanks stan, I will try one of proposed solution
On Wed, 2022-09-14 at 20:30 +0200, Dario Lesca wrote:
> Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha
> scritto:
> > Summary: You have to either issue a sync before suspend, or turn on
> > autosync in the kernel before suspend.
>
> Thanks stan, I will try one of proposed solution.
Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha scritto:
> Summary: You have to either issue a sync before suspend, or turn on
> autosync in the kernel before suspend.
Thanks stan, I will try one of proposed solution.
A little question: why is this not the default behavior?
if a us
On Wed, 14 Sep 2022 09:25:12 +0200
Dario Lesca wrote:
> When I try suspend with "systemctl suspend" my notebook Fedora 36
> sometime do not suspend with "PM: Some devices failed to suspend, or
> early wake event detected" error.
>
> Someone can help me to res
When I try suspend with "systemctl suspend" my notebook Fedora 36
sometime do not suspend with "PM: Some devices failed to suspend, or
early wake event detected" error.
Someone can help me to resolve this issue?
Many thanks
Dario
#
On 04.03.2022 19:56, Samuel Sieb wrote:
On 3/4/22 02:47, Adrian Sevcenco wrote:
Hi! I have a strange situation when trying to update a fedora 30 installation:
dnf is not working because all repositories give: "Failed to synchronize cache for
repo"
and this is in the context o
> > > dnf is not working because all repositories give: "Failed to
> > > synchronize cache for repo"
> > >
> > > and this is in the context of updating earlier a station f29-
> > > >f32-
> > > > f35
> > >
> > > Any ide
On 3/4/22 13:52, Branko Grubić wrote:
On Fri, 2022-03-04 at 12:47 +0200, Adrian Sevcenco wrote:
Hi! I have a strange situation when trying to update a fedora 30
installation:
dnf is not working because all repositories give: "Failed to
synchronize cache for repo"
and this is in the
On Fri, 2022-03-04 at 12:47 +0200, Adrian Sevcenco wrote:
>
> Hi! I have a strange situation when trying to update a fedora 30
> installation:
> dnf is not working because all repositories give: "Failed to
> synchronize cache for repo"
>
> and this is in the contex
On 3/4/22 02:47, Adrian Sevcenco wrote:
Hi! I have a strange situation when trying to update a fedora 30
installation:
dnf is not working because all repositories give: "Failed to synchronize
cache for repo"
and this is in the context of updating earlier a station f29->f32->
Hi! I have a strange situation when trying to update a fedora 30 installation:
dnf is not working because all repositories give: "Failed to synchronize cache for
repo"
and this is in the context of updating earlier a station f29->f32->f35
Any idea what is going on? It feels
Hi! After some update, when starting plasma/kde related applications from
console i started seeing this:
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data
from '/usr/lib64/qt5/plugins/kf5/kio/application
Sorry Jonathan,
But, I did not see your message!
Anyway, thanks to your help. I understood that I did not boot by using the
correct kernel. There was 5 options, and I did not try the right one!
The issue is fixed.
> To: "Community support for Fedora users"
> Subject: Re: faile
On Jul 18, 2021, at 03:24, Patrick Dupre wrote:
>
> It is now 2 days that I am stuck with this issue.
> I search on internet, but I did not find clear solutions which I could trust.
>
> Here is the fstab
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults
ofail let me run the initialization.
> > >
> > > Then,
> > > mount /boot/efi
> > > mount: /boot/efi: unknown filesystem type 'vfat'.
> > >
> > > I also noted during the load:
> > > FAILED: failed to start load kernel modules
> &
;
>
> > nofail let me run the initialization.
> >
> > Then,
> > mount /boot/efi
> > mount: /boot/efi: unknown filesystem type 'vfat'.
> >
> > I also noted during the load:
> > FAILED: failed to start load kernel modules
> >
&g
initrd-switch-root.service: Current command
> vanished>
> [ 12.033261] kernel: audit: type=1131 audit(1626509496.013:47): pid=1 uid=0
> a>
>
> [ 12.462543] systemd[1]: systemd-modules-load.service: Main process exited,
> code=exited, status=1/FA>
> [ 12.462635] syst
t; Then,
> > mount /boot/efi
> > mount: /boot/efi: unknown filesystem type 'vfat'.
> >
> > I also noted during the load:
> > FAILED: failed to start load kernel modules
>
> You appear to be booting into a kernel that doesn’t have any kernel modules
>
On Jul 17, 2021, at 04:29, Patrick Dupre wrote:
>
> Then,
> mount /boot/efi
> mount: /boot/efi: unknown filesystem type 'vfat'.
>
> I also noted during the load:
> FAILED: failed to start load kernel modules
You appear to be booting into a kernel that doesn’t hav
Thanks,
nofail let me run the initialization.
Then,
mount /boot/efi
mount: /boot/efi: unknown filesystem type 'vfat'.
I also noted during the load:
FAILED: failed to start load kernel modules
Now
journalctl -b -o short-monotonic --no-hostname
It is long, I noted (in red):
[
On Fri, Jul 16, 2021 at 1:20 PM Patrick Dupre wrote:
>
> I collected the maximum information that I could
>
> Failed Mounting /boot/efi
> See "systemctl boot-efi" for details
> Dependency failed for local file system
> Dependency failed for mark the ... to relabel after reboot
> Stopped
> You are
ain, as soon that I have been able to
> run properly the fc42, I will upgrade it.
>
> I did the same procedure on another machine and it was absolutely fine.
> I am a bit stuck for now.
> Obviously, there are some interference between the 2 systems.
> Is it only under the cont
another machine and it was absolutely fine.
I am a bit stuck for now.
Obviously, there are some interference between the 2 systems.
Is it only under the control of grub2?
The incomplete booting says:
failed to mount /boot:efi
check journalctl -xb
.etc..
Cannot open access to console the root
On Thu, Jul 15, 2021 at 12:31 PM Patrick Dupre wrote:
>
> I have been able to boot on a rescue kernel!
> Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06
> UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>
> bootctl
> systemd-boot not installed in ESP.
> System:
> Firmwa
tell me how it's failing.
> I get
> failed to mount /boot/efi
> /boot/efi is shared by both machines
>
> Here is the fstab of the fc34 machine
>
> #
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults1 1
> UUID=B2EF
fc34, I cannot boot on the new fc34.
> I get
> failed to mount /boot/efi
> /boot/efi is shared by both machines
>
> Here is the fstab of the fc34 machine
>
> #
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults
Hello,
On a dual boot machine (one fc32, and one fc34).
after I upgraded the fc32 to fc34, I cannot boot on the new fc34.
I get
failed to mount /boot/efi
/boot/efi is shared by both machines
Here is the fstab of the fc34 machine
#
UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39
Solution:
https://bugzilla.redhat.com/show_bug.cgi?id=1960937#c12
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/pro
It turns out the problem is with the radeon driver.
The GDM can be started normally once amdgpu is used instead of radeon
$ cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt3)/ostree/fedora-b84e4d88fe04fad4bc33b6ea17b973b4c73cd56c60843527323ed31290b71b6c/vmlinuz-5.11.20-300.fc34.x86_64
root=UUID=6d7c04a4-9
The screen is hang on a text mode, all black with only the cursor blinking at
the upper left corner.
Ctrl+Alt+F3 switching works, and sway can be started without issues.
Yesterday still worked normally, but after some update, it shows this problem.
Silverblue Rawhide.20210511.n.2 is working (do
On 12/31/20 4:52 AM, Ed Greshko wrote:
On 31/12/2020 20:41, Neal Becker wrote:
I'm not very familiar with restorecon and it's options, what might be
the command?
sudo restorecon -R /var/lib/rpm
Use "-Rv" if you want to see if it makes any changes.
On 31/12/2020 20:41, Neal Becker wrote:
On Wed, Dec 30, 2020 at 7:44 PM Jonathan Billings mailto:billi...@negate.org>> wrote:
On Dec 30, 2020, at 13:49, Neal Becker mailto:ndbeck...@gmail.com>> wrote:
>
> Thanks for the suggestion,
>
> No, rpm -qa runs just fine.
Could
On Wed, Dec 30, 2020 at 7:44 PM Jonathan Billings
wrote:
> On Dec 30, 2020, at 13:49, Neal Becker wrote:
> >
> > Thanks for the suggestion,
> >
> > No, rpm -qa runs just fine.
>
> Could be that the selinux labels are wrong, and cron and the dnf
> subprocesses can’t read the files. A ‘restorecon
On Dec 30, 2020, at 13:49, Neal Becker wrote:
>
> Thanks for the suggestion,
>
> No, rpm -qa runs just fine.
Could be that the selinux labels are wrong, and cron and the dnf subprocesses
can’t read the files. A ‘restorecon’ on the directory probably will fix that
—
Jonathan Billings
Thanks for the suggestion,
No, rpm -qa runs just fine.
On Wed, Dec 30, 2020 at 11:45 AM Jorge Fábregas
wrote:
> On 12/30/20 12:18 PM, Neal Becker wrote:
> > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed
>
> Do you get errors when you perform: rpm -qa ??? If so, this c
On 12/30/20 12:18 PM, Neal Becker wrote:
> Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed
Do you get errors when you perform: rpm -qa ??? If so, this could be a
corrupted RPM database.
If so try Method #1 listed here:
https://www.cyberciti.biz/tips/rebuilding-corrupted-
er8 dnf[1421142]: Error: Error: rpmdb open failed
Dec 30 11:01:29 nbecker8 systemd[1]: dnf-makecache.service: Main process
exited, code=exited, status=1/FAILURE
Dec 30 11:01:29 nbecker8 systemd[1]: dnf-makecache.service: Failed with
result 'exit-code'.
Dec 30 11:01:29 nbecker8 systemd[
URL to point to F33 repo. It will fail, after the
> whole installation is complete and the VM should start one last time,
> with following error:
>
> Failed to start Switch Root.
> Failed to switch root: Specified switch root path '/sysroot' does
> not seem to be an
k-cpu --accelerate \
--graphics none \
--extra-args 'ks=file:/minimal.ks console=tty0 console=ttyS0,115200'
Just change the URL to point to F33 repo. It will fail, after the
whole installation is complete and the VM should start one last time,
with following error:
Failed to st
e and so waiting for another update
doesn't seem like the right choice.
Any suggestions?
Thank-you,
Andrew
- o -
After start-up - the Gnome desktop appears - there's lots of disc
activity and this window appears:
*Failed to Update*
We're sorry that the update failed to install. Plea
After start-up - the Gnome desktop appears - there's lots of disc
> activity and this window appears:
>
> *Failed to Update*
>
> We're sorry that the update failed to install. Please wait for an
> update and try again. If the problem persists, contact your software
> p
be active.
I have repeatedly had this dialogue and so waiting for another update
doesn't seem like the right choice.
Any suggestions?
Thank-you,
Andrew
- o -
After start-up - the Gnome desktop appears - there's lots of disc
activity and this window appears:
*Failed to Upda
Peter Robinson writes:
> > After successfully testing an OpenVPN link on a x86_64, I get the
following
> > error on aarch64, as root:
> >
> > # nmcli connection import type ovpn file .ovpn
> > Error: failed to find VPN plugin for ovpn.
>
> So having tr
On 2020-08-07 21:45, Sam Varshavchik wrote:
> After successfully testing an OpenVPN link on a x86_64, I get the following
> error on aarch64, as root:
>
> # nmcli connection import type ovpn file .ovpn
> Error: failed to find VPN plugin for ovpn.
>
> Both systems have o
After successfully testing an OpenVPN link on a x86_64, I get the following
error on aarch64, as root:
# nmcli connection import type ovpn file .ovpn
Error: failed to find VPN plugin for ovpn.
Both systems have openvn, NetworkManager-openvpn, and NetworkManager-openvpn-
gnome packages
On 2020-05-23 19:07, Patrick Dupre wrote:
> Are they changes for ever?
The issue has been corrected.
You can restore the original settings.
--
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraprojec
But, I also have the issue foro skype:
>
> Errors during downloading metadata for repository 'skype-stable':
> - Curl error (28): Timeout was reached for
> https://repo.skype.com/rpm/stable/repodata/repomd.xml [Operation too slow.
> Less than 1000 bytes/sec transferred th
Sat, 23 May 2020 13:19:21 +0200
"Patrick Dupre" kirjoitti:
> I put
> exclude=skype
> and tried skype=false
> in /etc/dnf/dnf.conf
> but, it still wants to install skype
>
> messing up all installs
>
> > Thanks,
Package name is skypeforlinux, try that..
Jarmo
__
during downloading metadata for repository 'skype-stable':
> - Curl error (28): Timeout was reached for
> https://repo.skype.com/rpm/stable/repodata/repomd.xml [Operation too slow.
> Less than 1000 bytes/sec transferred the last 30 seconds]
> Error: Failed to download
repomd.xml [Operation too slow. Less
than 1000 bytes/sec transferred the last 30 seconds]
Error: Failed to download metadata for repo 'skype-stable': Cannot download
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
> On 2020-05-23 18:31, Patrick Dupre wrote:
>
key was not OK for
> https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-30&arch=x86_64
> [SSL certificate problem: certificate has expired]
> Error: Failed to download metadata for repo 'rpmfusion-free-updates': Cannot
> prepare internal mirrorlist:
ree-fedora-updates-released-30&arch=x86_64
[SSL certificate problem: certificate has expired]
Error: Failed to download metadata for repo 'rpmfusion-free-updates': Cannot
prepare internal mirrorlist: Curl error (60): SSL peer certificate or SSH
remote key was not OK for
https://mirror
1 - 100 of 370 matches
Mail list logo
