[frameworks-kservice] [Bug 490685] Dolphin causes compositor to lag when XDG_CONFIG_HOME variable contains a trailing slash

Adam Fontenot bugzilla_noreply at kde.org
Sat Jul 27 06:10:39 BST 2024


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

Adam Fontenot <adam.m.fontenot+kde at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdelibs-bugs at kde.org
            Version|24.05.2                     |6.4.0
            Product|dolphin                     |frameworks-kservice
            Summary|Dolphin causes compositor   |Dolphin causes compositor
                   |to lag when XDG_CONFIG_HOME |to lag when XDG_CONFIG_HOME
                   |variable contains a closing |variable contains a
                   |slash                       |trailing slash
          Component|general                     |general
           Assignee|dolphin-bugs-null at kde.org   |kio-bugs-null at kde.org

--- Comment #8 from Adam Fontenot <adam.m.fontenot+kde at gmail.com> ---
Okay after a bit more debugging I can say for sure this is a KService bug.

In the check at
https://invent.kde.org/frameworks/kservice/-/blob/master/src/sycoca/ksycoca.cpp?ref_type=heads#L662

    return extraFiles.keys() != files;

The left hand side is

    QList("/home/adam/.config/mimeapps.list",
"/home/adam/.local/share/applications/mimeapps.list",
"/usr/share/applications/kde-mimeapps.list")

The right hand side is

    QList("/home/adam/.config//mimeapps.list",
"/home/adam/.local/share/applications/mimeapps.list",
"/usr/share/applications/kde-mimeapps.list")

The lack of path normalization here means that KService thinks the sycoca
database needs to be rebuilt every time an application asks.

Dolphin hitting an endless loop here because of the `databaseChanged` signal
should probably be prevented, but the underlying issue is with KService so I'm
moving this bug there for more attention.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list