Can not create a socket for launching a KIO worker for protocol 'file'

[dougg0k]

https://bugs.kde.org/show_bug.cgi?id=497090

[ptr1337]

I can not reproduce this issue

[dougg0k]

This is the second time it happened from a fresh install using cachyos kde. Any idea what kind setting or package that could affect this?

---

I also saw this same error with brave browser before, dont remember what I did to trigger it.

[dougg0k]

There is an error that often occur on the command line, and only have happened on KDE, randomly, even when you type a command like pacman -S.

I wonder if it's related, as the protocol error are related to opening files and sometimes folders depending on the application.

error: could not get current working directory

...
 Total (2/2)
(2/2) checking keys in keyring
(2/2) checking package integrity
(2/2) loading package files
(2/2) checking for file conflicts
:: Processing package changes...
error: could not get current working directory
(1/2) installing ....
(2/2) installing ...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
...

---

I read that, it's related to apparmor.

[nutcasewtf]

Are you using Apparmor?

[nutcasewtf]

Naim had suggested a user to sudo aa-teardown which works per session if you are using Apparmor.

[dougg0k]

I stopped the systemctl service and tried, the issue persist.

---

Nevermind, with that command that also disabled in the kernel, worked. Apparmor was the reason, just unsure how to fix.

[dougg0k]

There is a kioworker profile at /etc/apparmor.d/kioworker.

I wonder what would require to fix it.

[nutcasewtf]

I don't use Apparmor so have no experience in this area.
possibly just disable it for now?
sudo aa-disable /etc/apparmor.d/kioworker

[dougg0k]

I opened a request for a fix. roddhjav/apparmor.d#630