You are not logged in.
When I do "journalctl -xe" while debugging systemd issues, I see a bunch of this error mingled in with what I'm after that's useful:
May 13 18:38:44 M87 kdeinit5[749]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:38:44 M87 kdeinit5[752]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:14 M87 kdeinit5[749]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:14 M87 kdeinit5[752]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:25 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:44 M87 kdeinit5[749]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:44 M87 kdeinit5[752]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:44 M87 kdeinit5[746]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:39:55 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:40:14 M87 kdeinit5[749]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:40:14 M87 kdeinit5[752]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:40:25 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:40:44 M87 kdeinit5[746]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:40:55 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:41:25 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:41:44 M87 kdeinit5[746]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave
May 13 18:41:55 M87 kdeinit5[768]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slaveI have an ssh share via Dolphin that's liklely the cause, but don't know what 'kio' is to be able to fix it. Google was no help, with stuff from years ago that didn't seem relevant.
Recent activity included removing a number of kde-related group packages after initially installing too many. Stuff like -edu, -pim, -games, etc. At least one package that was removed had 'accounts' in its name, but I connect using a key rather than a user- maybe that's part of it.
Could use a hand.
TIA
Last edited by NginUS (2019-05-14 02:04:44)
Offline
What systemd issues are you troubleshooting? In this case, providing just a snippet of a repeating error isn't going to help much. I would post more relevant log content and describe exactly when you see these errors - is it an action you take? Is it random? It appears those errors are about 20s apart, but not regular enough to be exactly timed, can you explain that with the actions you're taking?
Offline
What systemd issues are you troubleshooting?
I was going through getting ddclient up & running, and wound up revealing an issue where when using the config generator on nsupdate.info's website, it would fail- unless undocumented changes were made. I saw these errors in particular while commenting lines to help narrow down what was happening with it. That thread is here FWIW: https://github.com/nsupdate-info/nsupda … issues/432
I would post more relevant log content and describe exactly when you see these errors - is it an action you take?
Running journalctl -xe as part of obtaining output relevant to why that ddclient.service would fail displayed all those repeating errors I put here.
Is it random? It appears those errors are about 20s apart, but not regular enough to be exactly timed, can you explain that with the actions you're taking?
Again, all I know is they're there whenever I do journalctl -xe. I haven't tinkered with anything else mainly because I don't know what might be relevant with regard to causing it. If I had a clue about where to look I could try turning stuff on/off, or other actions to help narrow it down. I don't quite know where to start.
Last edited by NginUS (2019-05-13 23:57:17)
Offline
Offline
Thanks, Zod.
I fired up the VM with that in mind, & it appears to have resolved itself. It was the first reboot since it was happening, & apparently it was related to something that was going on then & not now.
Thanks for your input, will mark this solved- unless it happens again later I'll update then.
Offline