https://bugs.kde.org/show_bug.cgi?id=431886

            Bug ID: 431886
           Summary: Discover "Housekeeping" - Wishlist
           Product: Discover
           Version: 5.20.5
          Platform: Neon Packages
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: PackageKit
          Assignee: lei...@leinir.dk
          Reporter: tagwer...@innerjoin.org
                CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY:

    System Updates with Discover seem to leave cached installation files
    and older kernel versions on disc (/var/cache/apt/archives, /boot,
    /usr/lib/modules)

    Maybe it is expected that people know that they need to watch for
    and clean up "the debris". However some sanity checks within Discover
    would help to give a heads up about "eaten up" disc space or, maybe,
    include an option to tidy up old files within Discover.

STEPS TO REPRODUCE:

    Install a Neon system, install filelight (because it is a useful
    thing to have), wait and regularly install updates for a few months.
    Keep watch on disc usage with filelight

OBSERVED RESULTS

    The /var/cache/apt/archives folder steadily grows.

    The number of kernels grow, as can be seen in /boot (as is referred
    to in Bug 430296)

    The number of kernel modules directories grow with each kernel update,
    each of which can take 250 Mbyte.

    The number of initrd files also grows and, from the modification dates,
    they may all need to be rebuilt on a kernel update. In that case the
    update takes markedly longer (Discover waits at 99%) 

EXPECTED RESULTS

    Would expect discover to keep the the last three kernels and files
    and delete the older ones (with an option to keep a "preferred number").

    Would expect a warning if the /var/cache/apt/archives folder grows
    beyond a certain threshold and/or to clean-out old downloads.

SOFTWARE/OS VERSIONS

    Neon Testing
    Discover : 5.20.5
    Plasma : 5.20.5
    Frameworks : 5.79.0
    Qt : 5.15.2

ADDITIONAL INFORMATION

    The behaviour seems io be distro specific, Fedora KDE seems to cope.

    There is also the possibility that the behaviour I'm seeing is the
    result of something I've done or installed - and it all works perfectly
    for other people 8-/

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to