https://bugs.kde.org/show_bug.cgi?id=508412
--- Comment #7 from Andy <[email protected]> --- (In reply to David Edmundson from comment #6) > From the trace, we're in the code that reads through > $XDG_DATA_DIRS/share/applications . That code hasn't been changed in years, > so we're probably hitting an unusual case rather than it being a regression. > > The code ksycoca uses is based on timestamps of when we last indexed and the > last updates in the relevant folders. I strongly suspect one of these > folders /usr/share/applications .local/share/applications etc. has a > timestamp in the future. > > Output of > QT_LOGGING_RULES=kf.service.services.debug=true plasmashell --replace > > when we're going haywire would be the most helpful. Thank you for looking into this. Yeah I get your frustration about trying to make progress on KDE while being pressured to support versions that are 2-3 years old, and how difficult it must be to try and keep that much code in your head at once. I think everyone wants a good user experience and your strategy (have everyone use the latest version) and their strategy (have everyone use the version that has had the longest time to be debugged and fixed) just aren't aligning. Anyway it's much bigger than you and me. Thank you for your help. Here is some data about your hunch: ``` [<usernameRedacted>@<hostRedacted> tmp]$ echo "$XDG_DATA_DIRS" /usr/share/xfce4:/usr/share/gnome:/home/<usernameRedacted>/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share [<usernameRedacted>@<hostRedacted> tmp]$ sudo su [root@<hostRedacted> tmp]$ find /usr/share/xfce4 /usr/share/gnome /home/<usernameRedacted>/.local/share/flatpak/exports/share /var/lib/flatpak/exports/share /usr/local/share /usr/share -type d -newerct now find: ‘/home/<usernameRedacted>/.local/share/flatpak/exports/share’: No such file or directory [root@<hostRedacted> tmp]$ find /usr/share/xfce4 /usr/share/gnome /home/<usernameRedacted>/.local/share/flatpak/exports/share /var/lib/flatpak/exports/share /usr/local/share /usr/share -type d -newermt now find: ‘/home/<usernameRedacted>/.local/share/flatpak/exports/share’: No such file or directory [root@<hostRedacted> tmp]$ find /usr/share/xfce4 /usr/share/gnome /home/<usernameRedacted>/.local/share/flatpak/exports/share /var/lib/flatpak/exports/share /usr/local/share /usr/share -type d -newerat now find: ‘/home/<usernameRedacted>/.local/share/flatpak/exports/share’: No such file or directory ``` I redacted some parts for privacy. Besides one folder in the $XDG_DATA_DIRS no longer existing, `find` could not find any files with create, modify, or access in the future. Because of the pain of running out of memory every few hours, I've switched to xfce temporarily. I'll try to run the command you requested next time I log in fresh. I do prefer KDE so I hope we can get to the bottom of this together. What is the minimum file set that interacts with the relevant code. Can tar.gz some directories that will allow you to reproduce this on your end and hasten our dev feedback loop? Right now it's gonna be about a 24-48h loop because of time zone differences. As a developer myself I've learned that the faster the loop is, the more effective we are. -- You are receiving this mail because: You are watching all bug changes.
