https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #8 from Shmerl <shm...@mykolab.com> --- (In reply to Christoph Feck from comment #7) > You are probably using the Plasma calender with KDEPIM integration. That > needs akonadi, which in turn needs mysql. I suggest to disable the Plasma > KDEPIM integration. Please ask in a forum of your distribution if they offer > separate packages for that (openSUSE, for example, does). I'm using Kmail. Disabling it helps only slightly. The problem is there by design. Any I/O heavy process that kicks in on startup chokes plasmashell. Like for example starting Firefox which reads its cache and other data. It's the design that needs some change IMHO. I.e. plasmashell should load fully before any intense I/O slows it down. I understand that on SSD this is not an issue, and you on the contrary want everything to start right away, to reduce log-in time. On HDD, to reduce that time different startup strategy is needed, not wild west race for I/O resources. May be Plasma can determine, whether HDD or SSD is used, and apply needed strategy accordingly. -- You are receiving this mail because: You are watching all bug changes.
