Created attachment 138470 [details] Error dialog shown when launching Dolphin Since upgrading from v5.81.0 to v5.82.0 yesterday, I get an error dialog box whenever I launch any KDE-related applications. I have attached a screenshot taken from Dolphin as an example. The same applies to Gwenview -- and those are just the ones I've tested so far. When I take a look at the journal output, I see the following: [ May 16 06:38:52 Desktop kdeinit5[8946]: kf.kio.slaves.tags: tag fetch failed: "Failed to open the database" May 16 06:38:52 Desktop kdeinit5[8946]: kf.kio.slaves.tags: "tags:/" list() invalid url May 16 06:38:52 Desktop dolphin[8911]: kf.kio.core: "Could not enter folder tags:/." May 16 06:38:52 Desktop dolphin[8911]: kf.kio.core: "Could not enter folder tags:/." ] It's important to note that I was getting those last two lines with v5.81.0 as well. The only difference is that v5.82.0 additionally displays it in a dialog box (every single time)! Would you be able to either revert the relevant change made to the code or tell me what I must do to prevent said dialog from displaying in future? Thanks.
Same here. And what's more annoying if any app tries to show any kde-related file dialog (like opening or saving file in Chrome etc.) system first shows the "Could not enter folder tags:/." error I have to close and then shows the required dialog. And after I downgrade kio package to kio-5.79.0-1 (the last one I have in cache) error message goes away.
(In reply to Maciej J . Woloszyk from comment #1) Thanks for confirming. I just want to concur that the same thing (with the KDE file dialogs) is happening here. I should also note that I have Baloo disabled (to keep CPU usage down on my old [early-2014] machine). I saw in a related ticket that this may have some relevance.
Confirming. A few weeks ago I briefly had this problem as well but assumed that it was just my problem due to something strange I may have done (or due to running a new git master all the time). At the time I made it go away by deleting either a Baloo data directory, data file, or config file - I forgot which. But I guess a workaround isn't enough if other people have the same problem.
(In reply to Andreas Hartmetz from comment #3) Yes, I can confirm that running "balooctl purge" fixes the problem. Thanks for letting us know about the workaround. I will leave this ticket open as I imagine the developers may want to suppress the dialog box (or revert the code) anyway.
Possibly related to Bug 435586?
FWIW, the debug message comes from KIO::buildErrorString(), so if you can run dolphin under gdb, and create a breakpoint on that, we might be able to figure what's triggering the message.
Setting a breakpoint on KIO::buildErrorString was unfortunately not that helpful, it just pointed out that a error came from an external connection. Via KIO::ConnectionPrivate::commandReceived it became clear that a task.cmd=KIO::MSG_ERROR was received. With "KDE_FORK_SLAVES=1" set, there was some more helpful output: $ KDE_FORK_SLAVES=1 strace -ftto st.txt -s2000 okular kf.baloo.engine: PostingDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: PositionDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentDB::open docterms MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentDB::open docfilenameterms MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentDB::open docxatrrterms MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: IdTreeDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: IdFilenameDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentTimeDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentDataDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentIdDB::open indexingleveldb MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: DocumentIdDB::open failediddb MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: MTimeDB::open MDB_NOTFOUND: No matching key/data pair found kf.baloo.engine: dbis is invalid kf.kio.slaves.tags: tag fetch failed: "Failed to open the database" kf.kio.slaves.tags: "tags:/" list() invalid url kf.kio.core: "Could not enter folder tags:/." On my system, I have baloo disabled. I can confirm that after "balooctl purge", the error went away. Environment: Arch Linux baloo 5.84.0-1 kio 5.84.0-2
Can't reproduce it. Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-arch1-1 (64-bit) Graphics Platform: Wayland
I can reproduce the error on current Manjaro KDE Plasma 6 (version details at the end). Steps to Reproduce: 1. Add any new, unusued, tag (lets say 'tree') to a file or directory through the Dolphin Information Panel 2. Click the tag name ('tree') that appears in the Dolphin Places Panel --> Dolphin throws the error 'Could not enter folder tags:/tree.' Why it happens: The error is *correct*. This is a symptom of the Dolphin bug that writes mangled tags, actually saving '/tree' instead of 'tree', while inconsistently ignoring the forward slash (depending on where you are in the GUI). When you click 'tree' in the Places Panel, Dolphin puts 'tags:/tree/' in the address bar, which doesn't exist, so it throws the associated error. If you edit the address bar to 'tags://tree/', targeting the tag Dolphin actually wrote, then Dolphin displays the tagged file. If you fix the tag using the Dolphin right click menu or 'setfattrib' in the shell, then 'tags:/tree/' works and 'tags://tree/' throws the error. If you have both '/tree' and 'tree' tags then both addresses work, but each only shows the corresponding tag. An Easy Way For People to Encounter The Bug: That last bit explains how I ran into the bug in the first place. Just use the GUI to show the files with a particular tag, not knowing that a bunch of them are corrupted and missing from the listing, then remove that tag from the files. Now only corrupted versions of the tag exist (and all of the remaining tags on the files that weren't corrupted are now corrupted). The tag remains in the Places Panel, but points to the wrong address for the actual tags that are keeping the tag it in the GUI, so clicking on it throws the error. A related issue? I don't think this is related, and I haven't resolved it yet, but I have two tags that throw the error: "The process for the tags protocol died unexpectedly." I created a perl script that cleans my tags (I got it down to 6 seconds to scan my entire home directory :) which is how I learned the problem described above, so I *think* the tags in question are fine. I know that *some* of the tags in question are fine. My theory is actually that I'm running into an issue based on the number of files with the given tag. If I get a chance to nail that down I'll report it separately. System Information: Manjaro Baloo: 6.6.0 Dolphin: 24.08.1 KDE Plasma: 6.1.5 KDE Frameworks: 6.6.0 Qt: 6.7.2 Kernel: 6.6.54-2-MANJARO (64-bit) X11
Same issue here: tag a file "test" using Dolphin's Information Panel. Navigate to tags:/test. Error: "Could not enter folder tags:/test." However, unlike comment #9, navigating to tags://test gives me the same result. Dolphin doesn't seem to have written a "/test" tag -- tagging is just broken. System info (that I know how to find -- sorry, I am an absolute neophyte here): Kubuntu KDE Plasma 6.1.5 KDE Frameworks 6.6.0 Qt 6.6.2 Kernal 6.11.0-9-generic (64-bit) Wayland