[dolphin] [Bug 475152] New: Automatic update of ksycoca5 cache file sometimes breaks file association
fulalas
bugzilla_noreply at kde.org
Mon Oct 2 21:03:17 BST 2023
https://bugs.kde.org/show_bug.cgi?id=475152
Bug ID: 475152
Summary: Automatic update of ksycoca5 cache file sometimes
breaks file association
Classification: Applications
Product: dolphin
Version: 22.12.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: fulalas123 at gmail.com
CC: kfm-devel at kde.org
Target Milestone: ---
SUMMARY
When ksycoca5 cache (/root/.cache/ksycoca5*) is manually removed or it's
updated automatically, opening dolphin as root fail to make file association
work, and 'open with' shows no application.
STEPS TO REPRODUCE
1. remove /root/.cache/ksycoca5* cache file
2. open dolphin as root (not as admin)
3. double click any file that has an application associated with
OBSERVED
1. can't open them as all file associations are gone in this scenario
2. can't even use 'open with' because there is no application available
You might be wondering why I'm removing ksycoca5* cache file. Because that's
the fastest way to replicate this issue. When using the system normally, if
this cache file is updated automatically (and sometimes it is), the root issue
happens anyway. The only way to fix that is to manually run kbuildsycoca5 as
root and then running dolphin as root, which, of course, is not reasonable.
I noticed that the root ksycoca5* cache file created/updated automatically is
around 100kb smaller than the one created when we manually call kbuildsycoca5
(as root). Also, when we remove ksycoca5* cache file from the normal user
folder (non-root), it gets automatically regenerated, so for this non-root user
everything just works.
I managed to replicate this issue on pretty much any distro that ships Plasma
5.27.x, including Fedora 38, which uses dolphin 22.12.3.
Please, avoid the discussion on the 'why running dolphin as root blahblahblah'
as it won't help, and using admin:// is not a solution either. If you don't
consider this a bug or don't want to fix it, I prefer to hear that.
Thanks in advance :)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list