On 15/12/2020 18:52, John Pilkington wrote:
On 15/12/2020 09:54, Ed Greshko wrote:
> On 15/12/2020 16:24, Sreyan Chakravarty wrote:
>>
>>
>> On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, <ed.greshko(a)greshko.com
<mailto:ed.greshko@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 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 been
updated.
>>
>> Did you also happen to try a different user to see if they had similar
issues?
>>
>>
>> This is the third time I tried and I updated using root.
>>
>
> Have you considered trying to narrow down which package may be responsible?
>
> Picking packages to upgrade first which are least likely to be responsible?
>
> Packages such as ModemManager*, NetworkManager*, abrt*, ghostscript*?
>
> It may be helpful if the problem can't be duplicated by others.
>
> ---
> 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 Ctrl/Alt/f2, login and reboot.
That does happen from time to time, depending on what is upgraded.
Another option is to just issue a reboot from the command line.
sudo systemctl reboot
---
The key to getting good answers is to ask good questions.