Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Pip on 2021/08/30, 15:21:10
-
After doing a full upgrade this morning, I found that my KDevelop couldn't display the file system saying it couldn't find /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so. Dolphin raised the same error.
I went into the directory and did
sudo ln -s kio_file.so file.so
and it seemed to work ok afterwards. Don't know if that's the right solution, but it hasn't caused issues yet.
-
Just had to do a similar thing for (kio_)http.so, for perhaps it will apply to kio_ghelp.so, kio_help.so, kio_kamera.so, kio_remote.so and kio_trash.so as well.
-
I had a problem with kio for a short time yesterday (29.08.2021). After upgrading and restarting KDE, everything worked as usual again. Even after today's upgrades everything is still fine.
----
Ich hatte gestern (29.08.2021) kurzzeitig ein Problem mit kio. Nach einem Upgrade und Neustart von KDE funktionierte alles wieder wie gewohnt. Auch nach den heutigen upgrades ist noch alles in Ordnung.
edlin
-
Good point. I didn't have a kernel update, so I didn't reboot as generally I don't have to.
I'll take away the links and reboot, see if that helps...
-
Yep, that seems to be it. How odd.
Thanks.
-
Had the same problem, fixed by reboot today. Error message was:
Erstellung des Ein-/Ausgabemoduls nicht möglich. Meldung von klauncher: Das Modul „/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so“ wurde nicht gefundenor in EN: [Creation of the input/output module not possible. Message from klauncher: The module "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so" was not found.
Another problem was not solved though. After reboot a lot of apps don't allow keyboard input until I restart the app. I have no idea where to start looking.
-
To clarify, when you reboot, app A isn't accepting keyboard input until you restart app A. Once you've done that, if you reboot again, does app A show the same problem?
Also, going backwards, if app B isn't accepting input and you link the kio_<X>.so files with <X>.so links, does app B accept input?
You've probably already worked through that, but I wanted to be sure of the details.
-
Which version of kio is causing this problem?
kio:
Installed: 5.83.0-2
Candidate: 5.85.0-2
Version table:
5.85.0-2 500
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
*** 5.83.0-2 500
500 http://http.debian.net/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
-
Also, going backwards, if app B isn't accepting input and you link the kio_<X>.so files with <X>.so links, does app B accept input?
Sorry if I gave the impression, this was related to kio. It might be or not. What I wanted to point out is that this was also fallout of the kf5 update.
I will have to find the time to look into that. It seems that not only a reboot triggers the behavior. I reboot ~ once per month, last time 3 days ago. Just now I tried to rename a file in Dolphin - the old name is highlighted but can't be purged and keyboard input is not possible. Works fine in konsole of course.
-
I have not seen this problem. I don't have kdevelop installed but I use dolphin daily, and there's no issue on dolphin.
Here kio is 5.85.0-2. I don't have all the libkf5* packages installed, but the ones I do have are all 5.85.0-2. plasma-desktop is 5.21.5-2.
EDIT: There is no file.so in my /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/ directory (3 systems). So that error message is bogus -- the problem appears to be in the source/cause of the error message.
-
I only have it on my main rig, the rest of the devices is fine. Those are hard to debug.
A little googling led me to this: https://bugs.kde.org/show_bug.cgi?id=376966
Closest I could find. So probably not related to kio.