https://bugs.kde.org/show_bug.cgi?id=418727
Clodoaldo <clodoaldo.pinto.n...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clodoaldo.pinto.neto@gmail.
| |com
--- Comment #7 from Clodoaldo <clodoaldo.pinto.n...@gmail.com> ---
(In reply to roland from comment #5)
> (In reply to Torsten Maehne from comment #4)
> > I am observing this issue regularly after updates to KDE Plasma packages on
> > Arch Linux. On next reboot, SDDM typically takes much longer than usual to
> > show up. After successful login, I observe a black screen with blinking
> > cursor. If I wait long enough, finally the KDE Plasma desktop will show up
> > with the akonadi_migration_agent "In progress" dialogue spinning. With that
> > dialogue active, KDE Plasma seems to have also trouble to cleanly logout the
> > session, shutdown, or reboot the computer. If one tries to work in that
> > session, I observed freezes of applications after a short time, which
> > normally run without issues, namely Firefox, Thunderbird, and Libreoffice.
> >
> > In the past rebooting typically helped to make the issue go away until the
> > next update of KDE Plasma packages. However today, the issue would persist
> > even after several reboots. Only removing ~/.cache in a console session
> > before logging in via SDDM into KDE Plasma (Wayland session) helped. KDE
> > Plasma is at version 6.3.2 currently on Arch Linux.
>
> Having come up on real computers with real operating systems where actual
> Software Engineering (not Agile) and physical QA teams (not TDD) were used,
> I am always mortified at the roughly 99% of PC applications that can't
> bother to clear their disk cache on startup. Adding insult to injury, the
> format of the files changes between updates, new software is never tested
> with the old cache format and doesn't check for it, then all sorts of
> gastric intestinal application issues happen after an update is pushed out.
>
> If the software development process can't be fixed, at least fix the update
> process so it closes the application and nukes the cache before applying the
> update.
>
> Cache is meant only for the current running instance, not for saving
> settings between runs.
Deleting everything in ~/.cache works for me
--
You are receiving this mail because:
You are watching all bug changes.
