Description of problem: dolphin produces tags error Version-Release number of selected component (if applicable): Mageia 9 How reproducible: Always Steps to Reproduce: 1. Install dolphin on a system without kde running (I am running fvwm3). 2. Run dolphin 3. Right-click on any file name This produces the error "kf.kio.core: "Unable to create KIO worker. Unknown protocol 'tags'." and there is no context menu. kio, kio-extras, and a bunch of libraries that start with "lib64kf5kio" including lib64kf5kiocore5 are installed. I assume that either 1) there's a missing dependency that went unnoticed because not a lot of people run dolphin without kde, or 2) I need to run some kind of kde service to be able to right-click. Either way, this makes dolphin unusable.
Try to install dolphin-plugins if it is not.
CC: (none) => arusanu
Also, it seems that dolphin needs "baloo" too.
CC KDE people for knowledge
CC: (none) => fri, kde
(In reply to Aurelian R from comment #2) > Also, it seems that dolphin needs "baloo" too. I disable baloo. $ grep Enable /home/dave/.config/baloofilerc Indexing-Enabled=false dolphin still works including it's search tool, though there may be features I never use that only work if it is enabled.
CC: (none) => davidwhodgins
(In reply to Ken Arromdee from comment #0) > Description of problem: dolphin produces tags error > Steps to Reproduce: > 1. Install dolphin on a system without kde running (I am running fvwm3). > 2. Run dolphin > 3. Right-click on any file name > This produces the error "kf.kio.core: "Unable to create KIO worker. Unknown > protocol 'tags'." and there is no context menu. I have just tried Dolphin under Cinnamon (logged in via SDDM), and cannot reproduce the problem. However, I wonder whether "without kde running" actually means "without KDE/Plasma installed", which would be different. I do have Plasma installed, but use it rarely. Is the error signalled in Dolphin's GUI, or in terminal output?
CC: (none) => lewyssmith
I confirm the bug in my VM with mageia 9 x86_64 lxqt kf.kio.core: couldn't create worker: "Protocolo desconocido «tags»." kf.kio.core: "No se ha podido crear el módulo de trabajo KIO. Protocolo desconocido «tags»."
I installed baloo and Dolphin works now so it looks as though that was the missing dependency. (dolphin-plugins was already installed. And the error actually appears in both the GUI and terminal output.)
A fundmental question remains unanswered: Does this happen on systems without Plasma installed at all? Or also when running a different desktop on systems which have Plasma installed? Accepting the discovery (thank you Ken) that baloo needs to be at least installed, assigning this to Plasma people. $ urpmq --requires-recursive dolphin | grep baloo baloo-widgets lib64kf5baloo5 lib64kf5balooengine5 lib64kf5baloowidgets5 $ urpmq --whatrequires-recursive baloo | grep dolphin $ So dolphin looks to require anyway (but insufficiently) various baloo pkgs, but not baloo itself. $ urpmq -y baloo baloo baloo-widgets lib64kf5baloo-devel lib64kf5baloo5 lib64kf5balooengine5 lib64kf5baloowidgets-devel lib64kf5baloowidgets5
Assignee: bugsquad => kdeCC: lewyssmith => (none)
(In reply to Lewis Smith from comment #8) > A fundmental question remains unanswered: > Does this happen on systems without Plasma installed at all? Yes. "baloo" is part of plasma environment, so it is not pulled in otherwise as Ken found out. > Or also when running a different desktop on systems which have Plasma > installed? Only if "baloo" is forcibly removed(use: rpm -e --nodeps baloo) from a Plasma desktop Ken's bug can be reproduced. The puzzling part is why an indexing software as "baloo" is affecting "dolphin" as such.
(In reply to Aurelian R from comment #9) > The puzzling part is why an indexing software as "baloo" is affecting > "dolphin" as such. Maybe it can optionally be used for searching? But any way that is, it is a bad design choice if Dolphin is not supposed to be able to operate without Baloo. I think this should be asked upstream.
It is described here https://userbase.kde.org/Baloo
Well, it looks like an issue with packaging on Mageia side. The culprit is this file from baloo rpm: /usr/lib64/qt5/plugins/kf5/kio/tag.so with baloo uninstalled, extract the tag.so file from baloo rpm and just copy it in its place then dolphin starts working again. On the packaging, Fedora has kf5-baloo-libs package that removes these libs from main baloo rpm. This can be then tagged as recommendation for dolphin without to have the full baloo installed/running.
Bug Still valid for dolphin-23.04.3-1.mga9 in testing
Blocks: (none) => 32953
I added "Recommends: baloo" in dolphin-23.04.3-1.1.mga9
CC: (none) => geiger.david68210
(In reply to David GEIGER from comment #14) > I added "Recommends: baloo" in dolphin-23.04.3-1.1.mga9 After read Aurelian comment (In reply to Aurelian R from comment #12) > Well, it looks like an issue with packaging on Mageia side. > The culprit is this file from baloo rpm: > /usr/lib64/qt5/plugins/kf5/kio/tag.so > with baloo uninstalled, extract the tag.so file from baloo rpm and just copy > it in its place then dolphin starts working again. > On the packaging, Fedora has kf5-baloo-libs package that removes these libs > from main baloo rpm. This can be then tagged as recommendation for dolphin > without to have the full baloo installed/running. Did you think is the best way?
Created attachment 14448 [details] baloo-plugins spec Attached is a proposed patch for the baloo spec file that separates the plugin baloo libraries in a stand alone package. However, as I'm not that familiar with the whole process of packaging large stacks as Plasma, this is just a shot in the dark. Regards.
Done now for mga9 and Cauldron! Packages in 9/Core/Updates_testing: ====================== baloo-5.114.0-1.1.mga9 baloo-kioslaves-5.114.0-1.1.mga9 lib64kf5baloo-devel-5.114.0-1.1.mga9 lib64kf5baloo5-5.114.0-1.1.mga9 lib64kf5balooengine5-5.114.0-1.1.mga9 libkf5baloo-devel-5.114.0-1.1.mga9 libkf5baloo5-5.114.0-1.1.mga9 libkf5balooengine5-5.114.0-1.1.mga9 dolphin-23.04.3-1.2.mga9 dolphin-handbook-23.04.3-1.2.mga9.noarch.rpm lib64dolphin-devel-23.04.3-1.2.mga9 lib64dolphinprivate5-23.04.3-1.2.mga9 lib64dolphinvcs5-23.04.3-1.2.mga9 libdolphin-devel-23.04.3-1.2.mga9 libdolphinprivate5-23.04.3-1.2.mga9 libdolphinvcs5-23.04.3-1.2.mga9 From SRPMS: baloo-5.114.0-1.1.mga9.src.rpm dolphin-23.04.3-1.2.mga9.src.rpm
Assignee: kde => qa-bugs
MGA9-64 Xfce on HP-Pavillion No installation issues. This laptop has Plasma installed so, first removed baloo as in Comment 9. Then I could reproduce the problem. Installed the updates and now dolphin does searching OK agaain.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA9-64-OK
Created attachment 14451 [details] Log of install dolphin in lxqt VM Mageia 9 x86_64 lxqt Packages installed without issue and no more warnings about tags when click on a file
CC: (none) => andrewsfarm
The amount of testing packages fetched make me suggest wait until close bug#32845
The packages for this bug are part of big update in bug#32845
Depends on: (none) => 32953Blocks: 32953 => (none)
(In reply to katnatek from comment #21) > The packages for this bug are part of big update in bug#32845 You must have meant bug #32953. Since that bug has been sent along, I'm validating this one.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
(In reply to Thomas Andrews from comment #22) > (In reply to katnatek from comment #21) > > The packages for this bug are part of big update in bug#32845 > > You must have meant bug #32953. Since that bug has been sent along, I'm > validating this one. Not sure if this need validation, BTW what prevent the Plasma bugs be closed the last round of updates?
(In reply to katnatek from comment #23) > BTW what prevent the Plasma bugs be closed > the last round of updates? See https://bugs.mageia.org/show_bug.cgi?id=32081#c7
Closing
Status: NEW => RESOLVEDResolution: (none) => FIXED