On 03/12/2023 12:37, Michael D. Setzer II wrote:
On 3 Dec 2023 at 10:06, John Pilkington wrote:
Date sent: Sun, 3 Dec 2023 10:06:32 +
Subject:Re: NVIDIA RPM DNF Update Issue?
From: John Pilkington
To: users
On 3 Dec 2023 at 10:06, John Pilkington wrote:
Date sent: Sun, 3 Dec 2023 10:06:32 +
Subject:Re: NVIDIA RPM DNF Update Issue?
From: John Pilkington
To: users@lists.fedoraproject.org
Send reply to: Community support
On 03/12/2023 09:46, John Pilkington wrote:
On 02/12/2023 23:39, Michael D. Setzer II via users wrote:
Finally got it working, but tried lots of info from different pages,
and would get all kinds of different messages.
Cleared out everything, and tried things until this seems to have
run
On 02/12/2023 23:39, Michael D. Setzer II via users wrote:
Finally got it working, but tried lots of info from different pages,
and would get all kinds of different messages.
Cleared out everything, and tried things until this seems to have
run completely and is now showing the Nvidia GPU being
On 2 Dec 2023 at 10:40, Joe Zeff wrote:
Subject:Re: NVIDIA RPM DNF Update Issue?
To: users@lists.fedoraproject.org
From: Joe Zeff
Date sent: Sat, 2 Dec 2023 10:40:35 -0700
Send reply to: Community support for Fedora
On 12/02/2023 10:27 AM, francis.montag...@inria.fr wrote:
xorg-x11-drv-nvidia-cuda comes from rpmfusion and only provides the cuda
driver, not the whole cuda software. If this is sufficient for BOINC, using
only the rpmfusion repository will work and will be simpler to manage.
I've been using
On Sat, 02 Dec 2023 09:49:35 +1000 "Michael D. Setzer II" wrote:
> Followed instruction that removed all nvida packages.
> rpm -qa | grep -i nvidia
> now shows nothing.
> Tried to install but get message about filtering??
> dnf install xorg-x11-drv-nvidia-cuda
> Last metadata expiration check:
On 1 Dec 2023 at 18:43, francis.montag...@inria.fr wrote:
From: francis.montag...@inria.fr
To: Community support for Fedora users
Subject:Re: NVIDIA RPM DNF Update Issue?
Date sent: Fri, 01 Dec 2023 18:43:31 +0100
Send reply
On Sat, 02 Dec 2023 03:32:04 +1030 Tim via users wrote:
> On Fri, 2023-12-01 at 09:43 +, John Pilkington wrote:
>> /!\ Please remember to wait after the RPM transaction ends, until the
>> kmod get built. This can take up to 5 minutes on some systems.
> Don't they bother to do anything to
On Fri, 2023-12-01 at 09:43 +, John Pilkington wrote:
> /!\ Please remember to wait after the RPM transaction ends, until the
> kmod get built. This can take up to 5 minutes on some systems.
Don't they bother to do anything to let you know when it's finished?
--
uname -rsvp
Linux
Hi
On Fri, 01 Dec 2023 09:43:09 + John Pilkington wrote:
> On 01/12/2023 05:57, Michael D. Setzer II via users wrote:
>> rpm -qa | grep -i nvidia
>> xorg-x11-drv-nvidia-kmodsrc-535.129.03-2.fc38.x86_64
>> akmod-nvidia-535.129.03-1.fc38.x86_64
>>
On 01/12/2023 05:57, Michael D. Setzer II via users wrote:
Forgot to add info. In working to get it originally working, had
following instruction from only page that actually worked and
ended up with these packages being installed.
rpm -qa | grep -i nvidia
On 1 Dec 2023 at 15:52, Michael D. Setzer II via user wrote:
To: users@lists.fedoraproject.org
Date sent: Fri, 01 Dec 2023 15:52:13 +1000
Subject:NVIDIA RPM DNF Update Issue?
Priority: normal
Send reply to: mi...@guam.net
Recently replaced an ATI video card with a NVIDIA GTX 1070 card
on one of my Fedora 38 machine.
Seemed to have it working, but today got an error with dnf update.
Went to a number of sites, and with some instructions it shows a
message about module filtering??
Use BOINC and was trying to get
On 14 Nov 2023 at 16:06, Michael D. Setzer II via user wrote:
To: users@lists.fedoraproject.org
Date sent: Tue, 14 Nov 2023 16:06:52 +1000
Subject:Strange problem with phpmyadmin after recent
dnf upate??
Priority: normal
Send reply
On 15/09/2023 10.22, Kevin Fenzi wrote:
On Fri, Sep 15, 2023 at 10:08:25AM +1000, Eyal Lebedinsky wrote:
On 15/09/2023 06.37, Kevin Fenzi wrote:
...snip...
Are you running a fc6 system? Or where do you have this rpm?
I am not running fc6, I run fc38.
ok.
I'd strongly advise you to...
On Fri, Sep 15, 2023 at 10:08:25AM +1000, Eyal Lebedinsky wrote:
> On 15/09/2023 06.37, Kevin Fenzi wrote:
...snip...
> > Are you running a fc6 system? Or where do you have this rpm?
>
> I am not running fc6, I run fc38.
ok.
> > I'd strongly advise you to... not use a fc6 package at this point.
On 15/09/2023 06.37, Kevin Fenzi wrote:
On Fri, Sep 15, 2023 at 12:29:56AM +1000, Eyal Lebedinsky wrote:
The below message shows, then the update proceeds to completion.
Is it a problem? Is there something I should do or is it something at the
repository side (which one?).
I found articles
On Fri, Sep 15, 2023 at 12:29:56AM +1000, Eyal Lebedinsky wrote:
> The below message shows, then the update proceeds to completion.
> Is it a problem? Is there something I should do or is it something at the
> repository side (which one?).
>
> I found articles suggested rebuilding the rpm db.
The below message shows, then the update proceeds to completion.
Is it a problem? Is there something I should do or is it something at the
repository side (which one?).
I found articles suggested rebuilding the rpm db. However, since this problem
happened on two machines
I find it unusual to
peg-free ffmpeg --allowerasing".
Result skip broken dependencies ffmpeg (new !) , ffmpeg-libs ,
libavdevice : So no result.
I solved the problem with dnf update ffmpeg --allowerase and all
problems where sollved.
Now Tom has a new problem with VLC player. Well so have I : What is
wrong
asing".
Result skip broken dependencies ffmpeg (new !) , ffmpeg-libs ,
libavdevice : So no result.
I solved the problem with dnf update ffmpeg --allowerase and all
problems where sollved.
Now Tom has a new problem with VLC player. Well so have I : What is
wrong with ffmpeg ?
Dnf want
answer no
to the question, then call it with nohup and -y. Example:
nohup dnf -y removes --duplicates >& /var/tmp/rm-dups &
I do the same for "dnf update".
--
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubsc
A new issue is best started in a separate thread instead of hijacking
someone else's thread, as you did. It keeps threads neat and tidy too.
On Mon, 31 Jul 2023 15:11:06 -0700
richard emberson wrote:
> I had a "dnf update" interrupted.
At what stage was it interrupted? If
Running "dnf update --allowerasing results in:
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transa
On Mon, Jul 31, 2023 at 5:12 PM richard emberson
wrote:
> I had a "dnf update" interrupted.
>
> Running "dnf clean all" and then "dnf update" again results in:
>
> Running transaction check
> Transaction check succeeded.
> Running transaction
I had a "dnf update" interrupted.
Running "dnf clean all" and then "dnf update" again results in:
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
: Saturday, June 10, 2023 5:08:16 PM
To: Community support for Fedora users
Subject: Broken packages DNF Update.
Hay all,
Little problem : When giving the command dnf update I get the message
"Skipping packages with broken dependencies".
ffmpeg-libs x86_646.0.11.fc38 rpmf
On Sat, 10 Jun 2023 17:08:16 +0200
Ger van Dijck wrote:
> How do I proceed ?
I asked that a while back, and got this advice which worked for me:
dnf sawp ffmpeg-free ffmpeg --allowerasing
Replaces the incompatible stuff in the fedora repos with the
"normal" stuff from rpmfusion.
Hay all,
Little problem : When giving the command dnf update I get the message
"Skipping packages with broken dependencies".
ffmpeg-libs x86_64 6.0.11.fc38 rpmfusion-free-updates
libavdevice x86_64 6.0.11.fc38 rpmfusion-free-updates
How do I proceed ?
Kind rega
On Fri, 05 May 2023 21:14:40 -
Andre Robatino wrote:
> It might be the systemd OOM killer.
Good thought, but no messages that look like OOM. In fact, nothing in the
log looks like anything other than a normal shutdown. No I idea why I got
logged out. I guess there are some things man was not
It might be the systemd OOM killer. You can see the journalctl output for your
current boot with "journalctl -b 0", the previous boot with "journalctl -b -1",
etc. Get the output for whichever boot the logout happened in and grep for the
word "pressure". I had a similar problem with non-DE
Horsley wrote:
>
> I'm in my FVWM session, I run dnf update to get new kernel and other
> updates installed, I watch akmod update the nvidia driver, and I'm
> about to type reboot to get new kernel when suddenly *poof*, I'm
> logged out and the sddm login screen is displayed.
&
I'm in my FVWM session, I run dnf update to get new kernel and other
updates installed, I watch akmod update the nvidia driver, and I'm
about to type reboot to get new kernel when suddenly *poof*, I'm
logged out and the sddm login screen is displayed.
Is this some "helpful" change t
On 4/25/23 13:24, Samuel Sieb wrote:
On 4/25/23 06:12, Robert Moskowitz wrote:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As
On 4/25/23 06:12, Robert Moskowitz wrote:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf -y
Den 2023-04-25 kl. 15:12, skrev Robert Moskowitz:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf -y --exclude='*heif*' update
Sure, that has
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb that
is triggering the dependency.
As someone else pointed out:
# dnf -y --exclude='*heif*' update
___
users
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb that
is triggering the dependency.
On 4/23/23 16:07, Samuel Sieb wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On a F37 system I have not updated in maybe a month or more, I get
the error:
On 4/23/23 13:34, Robert Moskowitz wrote:
Guess I will have to wait, as I got the same error after a "clean
packages" and then the update with --skip-broken.
Right, that error happens after dependency resolution.
Try "--exclude='*heif*'" instead.
___
Guess I will have to wait, as I got the same error after a "clean
packages" and then the update with --skip-broken.
And maybe I will just take this system up to a fresh install with F38
since it hit the doorstep.
On 4/23/23 16:07, Samuel Sieb wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On a F37 system I have not updated in maybe a month or more, I get the
error:
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean
On a F37 system I have not updated in maybe a month or more, I get the
error:
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
file
On Aug 25, 2022, at 17:56, Patrick Dupre wrote:
>
> Hello,
>
> dnf update provides:
>
> Package mozilla-openh264-2.3.0-1.fc36.x86_64.rpm is not signed
> Package openh264-2.3.0-1.fc36.x86_64.rpm is not signed
> The downloaded packages were saved in cache u
Hello,
dnf update provides:
Package mozilla-openh264-2.3.0-1.fc36.x86_64.rpm is not signed
Package openh264-2.3.0-1.fc36.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages
On 7/24/22 01:42, Patrick Dupre wrote:
It seems that fc36 tries to run a dnf update automatically when the machine goes
to shutdown.
If I am correct, how can I avoid it?
That's not quite correct. Gnome Software (or PackageKit) by default
downloads updates in the background
Hello,
It seems that fc36 tries to run a dnf update automatically when the machine goes
to shutdown.
If I am correct, how can I avoid it?
===
Patrick DUPRÉ | | email: pdu...@gmx.com
On Thu, 16 Jun 2022 19:22:12 +1000
"Michael D. Setzer II via users" wrote:
> So not sure why this one got left over, or why there isn't a
> newer kernel-headers for the active kernels.
The kernel-headers is a separate package, and it is only updated if the
header files actually change. So,
On 16 Jun 2022 at 15:24, Eyal Lebedinsky wrote:
Date sent: Thu, 16 Jun 2022 15:24:01 +1000
Subject:Re: error messages during dnf update??
To: users@lists.fedoraproject.org
From: Eyal Lebedinsky
Send reply to: Community
On 16/06/2022 15.04, Michael D. Setzer II via users wrote:
Just did a dnf update and notice a whole lot of messages
like this.
hardlink: cannot link ./include/net/devlink.h to
/usr/src/kernels/5.17.11-200.fc35.x86_64/./include/net/de
vlink.h.hardlink-temporary: File exists
Just did a dnf update and notice a whole lot of messages
like this.
hardlink: cannot link ./include/net/devlink.h to
/usr/src/kernels/5.17.11-200.fc35.x86_64/./include/net/de
vlink.h.hardlink-temporary: File exists
++
Michael D
to correct the error). And you
don't know exactly what rpm is doing it nor what file it is
trying to write to.
On Tue, Mar 22, 2022 at 11:55 AM Robert McBroom via users
wrote:
The following message was sent to the terminal just before
the verifying step on a dnf
wrote:
> The following message was sent to the terminal just before the verifying
> step on a dnf update.
>
> Creating group sgx with gid 106.
> Creating group users with gid 100.
> Creating group systemd-oom with gid 951.
> Creating user systemd-oom (systemd Userspace OOM Killer)
The following message was sent to the terminal just before the verifying
step on a dnf update.
Creating group sgx with gid 106.
Creating group users with gid 100.
Creating group systemd-oom with gid 951.
Creating user systemd-oom (systemd Userspace OOM Killer) with uid 951
and gid 951.
/etc
Michael D. Setzer II via users wrote:
> Shows these updates with broken dependences
>
> nodejsi6861:14.19.0-2.fc34
>updates 199 k
> nodejsx86_64 1:14.19.0-2.fc34
>
Shows these updates with broken dependences
nodejsi6861:14.19.0-2.fc34
updates 199 k
nodejsx86_64 1:14.19.0-2.fc34
updates 199 k
- Databases Team
Red Hat
--
On Sun, Jan 16, 2022 at 5:37 PM Robert Moskowitz wrote:
>
>
>
> On 1/16/22 11:31, Grumpey wrote:
> > On Sun, Jan 16, 2022 at 11:25 AM Robert Moskowitz
> > wrote:
> >> Did a dnf update this morning before updating my bios and
On 1/16/22 11:31, Grumpey wrote:
On Sun, Jan 16, 2022 at 11:25 AM Robert Moskowitz wrote:
Did a dnf update this morning before updating my bios and installing
more memory (more on that in a separate missive)
...
2022-01-16T10:41:04-0500 INFO Regex version mismatch, expected: 10.39
2021
On Sun, Jan 16, 2022 at 11:25 AM Robert Moskowitz wrote:
>
> Did a dnf update this morning before updating my bios and installing
> more memory (more on that in a separate missive)
>
> I saw some messages during the update process about "Regex version
> mismatch&qu
Did a dnf update this morning before updating my bios and installing
more memory (more on that in a separate missive)
I saw some messages during the update process about "Regex version
mismatch" but it said it completed successfully. I did my hardware
changes, booted back into
On Mon, 1 Nov 2021 14:15:14 -0400
Neal Becker wrote:
> Just to followup, after dnf removing papirus-icon-theme (which I
> didn't need), dnf update completes normally.
>
> On Mon, Nov 1, 2021 at 1:30 PM Neal Becker
> wrote:
> >
> > dnf seems to just hang on
Just to followup, after dnf removing papirus-icon-theme (which I
didn't need), dnf update completes normally.
On Mon, Nov 1, 2021 at 1:30 PM Neal Becker wrote:
>
> dnf seems to just hang on this update, using 100% cpu:
>
> papirus-icon-theme-20210901-2.fc35.noarch.rpm
>
> --
dnf seems to just hang on this update, using 100% cpu:
papirus-icon-theme-20210901-2.fc35.noarch.rpm
--
Those who don't understand recursion are doomed to repeat it
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
On Tue, 5 Oct 2021 13:40:51 -0500
Ian Pilcher wrote:
> I use systemd-boot, so I try to avoid having unneeded GRUB packages
> installed. When I run dnf update, grub2-tools-efi and
> grub2-tools-extra get installed, even though they aren't required by
> any of my other installed pack
> On 7 Oct 2021, at 18:38, Ian Pilcher wrote:
>
> On 10/5/21 16:36, Barry wrote:
>>> On 5 Oct 2021, at 19:41, Ian Pilcher wrote:
>>>
>>> I use systemd-boot, so I try to avoid having unneeded GRUB packages
>>> installed. When I run dnf update,
On 10/5/21 16:36, Barry wrote:
On 5 Oct 2021, at 19:41, Ian Pilcher wrote:
I use systemd-boot, so I try to avoid having unneeded GRUB packages
installed. When I run dnf update, grub2-tools-efi and grub2-tools-extra
get installed, even though they aren't required by any of my other
On 10/5/21 3:36 PM, Barry wrote:
Try dnf remove package and see what dnf wants to remove.
Just answer no so that dns does no damage.
That’s the trick I used to find out why a package is needed.
You can also do rpm queries, but I do recall the incantation.
Just to be safe, add -n to the dnf
> On 5 Oct 2021, at 19:41, Ian Pilcher wrote:
>
> I use systemd-boot, so I try to avoid having unneeded GRUB packages
> installed. When I run dnf update, grub2-tools-efi and grub2-tools-extra
> get installed, even though they aren't required by any of my other
> installe
I use systemd-boot, so I try to avoid having unneeded GRUB packages
installed. When I run dnf update, grub2-tools-efi and grub2-tools-extra
get installed, even though they aren't required by any of my other
installed packages.
I already have install_weak_deps=False set in dnf.conf.
Anyone have
On 2021-07-03 10:09 a.m., Ger van Dijck wrote:
When dnf update I get the following message : Errors during downloading
fedora-cisco-openh264. etc etc
How to resolve this problem ?
There must be more lines than that. It's pretty hard to say how to fix
it without knowing what the problem
Ger van Dijck wrote:
> When giving dnf update I get the following message:invalid value
> failovermethod = priority in /etc/yum.repo.d/teamviewer.repo . Configuration
> : Optionbinding with failovermethod does not excist.
>
> What does it mean ? and how can I prevent it ?
Rem
8:54:11 MESZ schrieb Ger van Dijck
>:
>>Hi all,
>>
>>
>>
>>
>>When giving dnf update I get the following message:invalid value
>>failovermethod = priority in /etc/yum.repo.d/teamviewer.repo .
>>Configuration : Optionbinding with failovermethod does no
Perhaps this guide might help:
https://coteamviewermputingforgeeks.com/how-to-install--on-fedora/
Am 3. Juli 2021 18:54:11 MESZ schrieb Ger van Dijck :
>Hi all,
>
>
>
>
>When giving dnf update I get the following message:invalid value
>failovermethod = priority in /etc/yum.r
them.
Hi Tom ,
Dnf update did functionates a few days agoo with the noraml update
sessions , so no problems , I just agree with you. But I stay curious
why I get these kind of messages and as you pionted out there is no
reatl problem . Lets hope Joahanna.
Ger van Dijck
Hi Linux world,
When dnf update I get the following message : Errors during downloading
fedora-cisco-openh264. etc etc
How to resolve this problem ?
Regards,
Ger van Dijck.
___
users mailing list -- users@lists.fedoraproject.org
On 04/07/2021 00:54, Ger van Dijck wrote:
When giving dnf update I get the following message:invalid value failovermethod
= priority in /etc/yum.repo.d/teamviewer.repo . Configuration : Optionbinding
with failovermethod does not excist.
What does it mean ? and how can I prevent it ?
Well
On Sat, 3 Jul 2021 18:54:11 +0200
Ger van Dijck wrote:
> What does it mean ? and how can I prevent it ?
No idea, but I see so many weird messages during dnf
updates that I just ignore them and wait to see if
I notice a real problem before worrying about them.
Hi all,
When giving dnf update I get the following message:invalid value
failovermethod = priority in /etc/yum.repo.d/teamviewer.repo .
Configuration : Optionbinding with failovermethod does not excist.
What does it mean ? and how can I prevent it ?
Ger van Dijck
On 5/22/21 7:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https://...
On 5/22/21 8:54 PM, Scott Beamer wrote:
Right after I posted, the problem seems to have resolved itself.
Never mind. :)
Glad to see that, but it's still a good idea to remember my suggestion
if/when it happens again.
___
users mailing list --
On 5/22/21 7:49 PM, Joe Zeff wrote:
On 5/22/21 8:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl
error (23): Failed writing received data to
On 5/22/21 8:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https://...
Greetings,
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https://...
Any suggestions?
Pastebin:
On 8 Mar 2021 at 6:12, Michael D. Setzer II via user
wrote:
To: users@lists.fedoraproject.org
Date sent: Mon, 08 Mar 2021 06:12:15 +1000
Subject:dnf update of wine shows error??
Priority: normal
Send reply to: Community
010c:err:process:exec_process failed to load
L"C:\\windows\\syswow64\\rundll32.exe" error c018
wine: configuration in L"H:\\.wine" has been updated.
Just ran dnf update and it installed updates to wine.
Then ran wine notepad to test, and noticed
On Wed, 16 Dec 2020, 3:08 pm Ed Greshko, wrote:
> On 16/12/2020 17:22, Sreyan Chakravarty wrote:
> > Will it be excluded just for this update or will it be excluded for
> > all future updates as well.
>
> Just the one update.
>
> If you want to exclude the packages for all updates you'll need to
On 16/12/2020 17:22, Sreyan Chakravarty wrote:
Will it be excluded just for this update or will it be excluded for
all future updates as well.
Just the one update.
If you want to exclude the packages for all updates you'll need to put the
"exclude" statement in
/etc/dnf/dnf.conf
man
ilto:ed.gres...@greshko.com>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> In the bugzilla you wrote:
> >>>>>>
> >>>>>> How reproducible:
> >>>>>> Always when I update.
> >&
:
On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, mailto:ed.gres...@greshko.com>> wrote:
In the bugzilla you wrote:
How reproducible:
Always when I update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you att
gt;>
> > >> ---
> > >> The key to getting good answers is to ask good questions.
> > >>
> > >
> > > In F32 I have found that a reboot instruction in Plasma will often not
> > > complete after a kernel or nvidia update. Now I use
m Ed Greshko, >>> <mailto:ed.gres...@greshko.com>> wrote:
> >>>
> >>>
> >>> In the bugzilla you wrote:
> >>>
> >>> How reproducible:
> >>> Always when I update.
> >>>
> >>
update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you attempted the update?
I ask since I've looked over the list of packages updated and it seems I
have all of those which are
related to plasma and have no tr
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you attempted the update?
I ask since I've looked over the list of packages updated and it
seems I have all of those which are
related to plasma and have no troubles. With multiple systems
having bee
> > How reproducible:
> > Always when I update.
> >
> > Steps to Reproduce:
> > 1. Open terminal.
> > 2. sudo dnf update -y
> > 3. Reboot.
> >
> > How many times have you attempted the update?
> >
> >
On 15/12/2020 16:24, Sreyan Chakravarty wrote:
On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, mailto:ed.gres...@greshko.com>> wrote:
In the bugzilla you wrote:
How reproducible:
Always when I update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
;>> https://pastebin.com/raw/iHgwrKjv
> >>>
> >>> Since you wanted the package list it is also there.
> >>>
> >>> Any ideas ?
> >>
> >> Luckily I had a snapshot. Just got back to normal.
> >>
> > Filed the bug:
> &g
Filed the bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1907759
In the bugzilla you wrote:
How reproducible:
Always when I update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you attempted the update?
I ask since I've looked over the list of packages updated
On Tue, Dec 15, 2020 at 11:07 AM Sreyan Chakravarty wrote:
>
> On Tue, Dec 15, 2020 at 12:27 AM Sreyan Chakravarty
> wrote:
> >
> > On Sat, Dec 12, 2020 at 2:27 AM Ed Greshko wrote:
> > >
> > > You use the "dnf history" commands.
> > >
> > > Do a "man dnf" and you should be able figure out how
On Tue, Dec 15, 2020 at 12:27 AM Sreyan Chakravarty wrote:
>
> On Sat, Dec 12, 2020 at 2:27 AM Ed Greshko wrote:
> >
> > You use the "dnf history" commands.
> >
> > Do a "man dnf" and you should be able figure out how to do it.
> >
>
>
> Well I just got screwed.
>
> I really thought that you
1 - 100 of 333 matches
Mail list logo
