Bug 437176 - I keep getting a "Could not enter folder tags:/." error dialog box (with this release)
Summary: I keep getting a "Could not enter folder tags:/." error dialog box (with this...
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.82.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-15 21:09 UTC by Xavion
Modified: 2022-07-31 06:44 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Error dialog shown when launching Dolphin (13.04 KB, image/png)
2021-05-15 21:09 UTC, Xavion
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xavion 2021-05-15 21:09:35 UTC
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.
Comment 1 Maciej J . Woloszyk 2021-05-17 06:17:56 UTC
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.
Comment 2 Xavion 2021-05-17 20:29:42 UTC
(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.
Comment 3 Andreas Hartmetz 2021-05-17 20:37:49 UTC
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.
Comment 4 Xavion 2021-05-18 00:05:52 UTC
(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.
Comment 5 Nate Graham 2021-05-19 02:31:30 UTC
Possibly related to Bug 435586?
Comment 6 Ahmad Samir 2021-07-09 18:00:40 UTC
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.
Comment 7 Peter Wu 2021-08-18 14:17:12 UTC
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