annoying message on KDE desktop screen
Folks, I've recently done an update from 15.1 to 15.2 using `zypper dup`. Since then I see an annoying message on the middle of my KDE desktop screen: Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „desktop“ kann nicht gestartet werden. I guess an English translation is roughly Can't create in/out module. Socket for in/out module for 'desktop' can't be started. My next step was to switch to the newest KDE version following the instructions from https://en.opensuse.org/SDB:KDE_repositories However, I still get this message. For testing purposes, I called dbus-launch dolphin and get the following output on the console – dolphin shows no files in its window. kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „trash“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „trash“ kann nicht gestartet werden." kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „file“ kann nicht gestartet werden." ... Do you have any idea how I could fix this? Werner
On 23.02.21 08:17, Werner LEMBERG wrote:
Folks,
I've recently done an update from 15.1 to 15.2 using `zypper dup`. Since then I see an annoying message on the middle of my KDE desktop screen:
Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „desktop“ kann nicht gestartet werden.
I guess an English translation is roughly
Can't create in/out module. Socket for in/out module for 'desktop' can't be started.
My next step was to switch to the newest KDE version following the instructions from
https://en.opensuse.org/SDB:KDE_repositories
However, I still get this message.
For testing purposes, I called
dbus-launch dolphin
and get the following output on the console – dolphin shows no files in its window.
kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „tags“ kann nicht gestartet werden." kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „trash“ kann nicht gestartet werden." kf.kio.core: "Erstellung des Ein-/Ausgabemoduls nicht möglich. Socket für Ein-/Ausgabemodul für „trash“ kann nicht gestartet werden." kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create slave: "Socket für Ein-/Ausgabemodul für „file“ kann nicht gestartet werden." ...
Do you have any idea how I could fix this?
Werner
A reboot usually fixed this for me.
On 2021-02-23 11:03, Werner LEMBERG wrote:
I've recently done an update from 15.1 to 15.2 using `zypper dup`. Since then I see an annoying message on the middle of my KDE desktop screen: [...]
A reboot usually fixed this for me.
Nope, this doesn't work, but thanks for the idea.
For fault isolation I'd start with creating a new user and see if it's the system or if it's your current user that's the problem. sudo useradd -m testuser1 sudo passwd testuser1 logout and login with new user If it's still a problem, erase all files and directories in that users home directory to get rid of all skeleton files and newly created files and then relogin again. If it's still a problem I'd say it's your system that gone weird. -- /bengan
On 23/02/2021 11.24, Bengt Gördén wrote:
On 2021-02-23 11:03, Werner LEMBERG wrote:
I've recently done an update from 15.1 to 15.2 using `zypper dup`. Since then I see an annoying message on the middle of my KDE desktop screen: [...]
A reboot usually fixed this for me.
Nope, this doesn't work, but thanks for the idea.
For fault isolation I'd start with creating a new user and see if it's the system or if it's your current user that's the problem.
sudo useradd -m testuser1
I think in *suse it is better to use YaST for user creation, so that directories are properly initialized. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2021-02-23 12:28, Carlos E. R. wrote:
I think in *suse it is better to use YaST for user creation, so that directories are properly initialized.
Actually. It was on purpose. The directories shouldn't be initialized. I think that you need to create an account that doesn't introduce that much from the system side to be able to do the fault isolation. That's why I suggested to remove all created files in the /home/testuser1 that -m introduces if the problem persisted. But it might be a good thing to start with adding a user with yast. 1. from yast 2. useradd -m 3. useradd without -m (remove the created files) -- /bengan
On 23/02/2021 14.30, Bengt Gördén wrote:
On 2021-02-23 12:28, Carlos E. R. wrote:
I think in *suse it is better to use YaST for user creation, so that directories are properly initialized.
Actually. It was on purpose. The directories shouldn't be initialized. I think that you need to create an account that doesn't introduce that much from the system side to be able to do the fault isolation. That's why I suggested to remove all created files in the /home/testuser1 that -m introduces if the problem persisted. But it might be a good thing to start with adding a user with yast.
1. from yast 2. useradd -m 3. useradd without -m (remove the created files)
I don't think that the files and directories created by yast can be an issue, because any desktop or tool you start using on openSUSE assumes that structre was properly created by YaST. If you delete them, the structure is different from "default". -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Actually. It was on purpose. The directories shouldn't be initialized. I think that you need to create an account that doesn't introduce that much from the system side to be able to do the fault isolation. That's why I suggested to remove all created files in the /home/testuser1 that -m introduces if the problem persisted. But it might be a good thing to start with adding a user with yast.
1. from yast 2. useradd -m 3. useradd without -m (remove the created files)
Thanks for the tips. All of them failed. If I add a new user and log in to it, the desktop either doesn't start up, or crashes, or is extremely slow (and plasma crashes soon later on) – and the annoying message about the 'io-slave' doesn't go away either. So it seems that my system setup is somewhat broken, and I can be happy that my (single) user account works as expected for my purposes, more or less. Eventually I have to completely reinstall 15.2. Werner
On 2/23/21 5:28 AM, Carlos E. R. wrote:
I think in *suse it is better to use YaST for user creation, so that directories are properly initialized.
Nope. useradd, groupadd, (and the ...mod flavors) and gpasswd all work just fine and like YAST all draw from /etc/skel/ for their defaults. -- David C. Rankin, J.D.,P.E.
participants (5)
-
Bengt Gördén -
Carlos E. R. -
David C. Rankin -
Fabian Niepelt -
Werner LEMBERG