SUMMARY There is a bug that happens on in KDE, in this case, when using qbittorrent client. When I click to open a file from there, results in this error. ``` ❯ qbittorrent edit: editing failed kf.kio.core: ConnectionServer::listenForRemote failed: "QLocalServer::listen: Name error" kf.kio.core: KIO Connection server not listening, could not connect kf.kio.core: couldn't create worker: "Can not create a socket for launching a KIO worker for protocol 'file'." Unable to create KIO worker. Can not create a socket for launching a KIO worker for protocol 'file'. ``` STEPS TO REPRODUCE 1. Install `sudo pacman -S qbittorrent` 2. Download a file from a torrent/magnet 3. Try to open a file through qbittorrent Content tab. OBSERVED RESULT Shows a dialog with the error. EXPECTED RESULT To open the file SOFTWARE/OS VERSIONS Operating System: CachyOS Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.12.1-2-cachyos (64-bit) Graphics Platform: Wayland
Same error just happened with steam, when you right click in a game > manage > browser local files.
Demonstration https://www.dropbox.com/scl/fi/4fx044x23gjvuhmzsouud/2024-12-06_17-19-31.mp4?rlkey=mfwjs8qo7ep0o6vlmkmuocv5t&st=38grrtxi&dl=0
This is an integration issue in your OS; please report it to them. Thanks!
That seems like an assumption. Though, they were unable to reproduce the issue. https://github.com/CachyOS/distribution/issues/69 And as I didnt do anything related to this, unsure what is the cause of it. All packages seems to be installed. ❯ pacman -Qs kio local/kio 6.9.0-1.1 (kf6) Resource and network access abstraction local/kio-extras 24.12.0-1.1 (kde-applications kde-network) Additional components to increase the functionality of KIO local/kio-fuse 5.1.0-3.2 FUSE interface for KIO local/kio5 5.116.0-1.2 (kf5) Resource and network access abstraction local/kio5-extras 24.02.2-2.2 Additional components to increase the functionality of KIO
I have found the cause, just not a fix while keeping the cause running. Cause was AppArmor with one of it's profile. With the following command, I disabled it, and it worked. sudo aa-teardown
To be more precise, the cause was a profile in the `apparmor.d-git` package.