I recently updated my Ubuntu Studio machine to 24.04 LTS (from 22.04). Ever since that update, kioslave5 is spawning processes that endlessly churn my hard drive (yes, I still have a spinning hard drive) and my network. Killing all kioslave5 will stop both. For example, it’s happening as I type this. I see
Hi, from past reports, this is likely caused by the thumbnail generation. Do you have network-mounted shares and/or do you have a lot of images in your drive(s)?
@mlincett thanks very much for taking the time to look into this and comment. I looked in the KDE Settings under “Online Accounts” and found a link there for Google Drive. I don’t think it was active, because I didn’t see anything in Dolphin under the Network drives. But I deleted the Google Drive entry from the KDE Settings.
As far as thumbnails, yes, I saw some of those discussions. I probably don’t have an unusually large number of images; several hundred photos and whatever thousands of little jpg’s and png’s that are part of the KDE install. Would the suggested thumbnail generation only be when Dolphin or another file manager is active? Would it be a one-time thing, that is, once it’s done generating thumbnails for the images it would know enough not to continue ad infinitum? If the latter were the case I would be content to let it do its one-time thing.
In any case thank you again, it’s much appreciated.
Looks like removing Google Drive from my “Remote → Network” category in Dolphin fixed it. (Google Drive still shows up in the Dolphin pane where the file list is, but I deleted the entry that comes up when double-clicking Google Drive.) Either that or the (hopefully) one-time thumbnail generation task completed. Thanks for the help.
This problem is NOT to many pics on the drive. It started the minute an update was made. I have 1 mounted drive and some pic on it, it is a 500g SDD and is not yet half full.
[KCrash Handler] #4 0x0000000000000000 in ?? () #5 0x000074b4313b55c1 in KExiv2Iface::KExiv2::load(QString const&) const () from /lib/x86_64-linux-gnu/libKF5KExiv2.so.15.0.0 #6 0x000074b4313b5dc9 in KExiv2Iface::KExiv2::KExiv2(QString const&) () from /lib/x86_64-linux-gnu/libKF5KExiv2.so.15.0.0 #7 0x000074b43807d118 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/thumbcreator/jpegthumbnail.so #8 0x000074b4416fc70b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so #9 0x000074b441702482 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so #10 0x000074b4415e50bf in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x000074b4415dc76d in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x000074b4415dd0c6 in KIO::SlaveBase::dispatchLoop() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x000074b4416fe21b in kdemain () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so #14 0x00005a33e720350c in ?? () #15 0x000074b44062a1ca in __libc_start_call_main (main=main@entry=0x5a33e7203320, argc=argc@entry=5, argv=argv@entry=0x7ffd690e04c8) at ../sysdeps/nptl/libc_start_call_main.h:58 #16 0x000074b44062a28b in __libc_start_main_impl (main=0x5a33e7203320, argc=5, argv=0x7ffd690e04c8, init=, fini=, rtld_fini=, stack_end=0x7ffd690e04b8) at ../csu/libc-start.c:360 #17 0x00005a33e7203785 in ?? ()
[Inferior 1 (process 207080) detached]
No net drives, as I posted 1 connected drive, no others mounted. After I DL the updates & then rebooted it started, that was back in February. The big thing that happen is Gwenview has many crashes when trying to one pic as I posted the crash data..
OP here. It’s been quite some time now but according to my notes the one thing that worked for me to eliminate the churn from kioslave5 was to un-install kdeconnect.
I took a subsequent note that removing the KDE comics widget from my desktop helped as well, as strange as that sounds.
Regarding your comment about Gwenview crashes, note that a recent update to the libexiv2 package broke Gwenview (among other applications). Make sure you have this version installed:
libexiv2-27:amd64 0.27.6-1ubuntu0.3
The version released earlier in the week last week definitely had something to do with kioslave5; see the bug report here (as suggested above by @meven):