Re: F33 - KDE broken after dnf update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 16, 2020 at 1:39 PM Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote:
>
> On Tue, Dec 15, 2020 at 4:30 PM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
> >
> > 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@xxxxxxxxxxx <mailto:ed.greshko@xxxxxxxxxxx>> 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
> >
>
> I have found the culprits for the breakages:
>
> kwayland-server
> kf5-plasma
>
> kwayland-server update produces the same original problem in my bug.
> kf5-plasma however breaks the login screen.
>
> Now the question is whether I can run "dnf update" excluding these two
> packages ONLY for this particular update ?
>

Also what should I do with the bug I already filed ?

Should I close it or should I add information to the bug ?

-- 
Regards,
Sreyan Chakravarty
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux