Version: (using KDE KDE 3.3.0) Installed from: SuSE RPMs OS: Linux One day I found that I could no longer add items to the kmenu using kmenuedit. I could make the changes, but they wouldn't show up in the kmenu. If I restarted kmenuedit I would find that the changes to individual items (including the titles) had stuck, but they would not be apparent in the kmenuedit tree pane. New menu items I created would still appear in ~/.local, but they would not show up in kmenuedit. I was also starting to get weird blank entries showing up in kmenuedit. I presume these were ones I had deleted. This problem only occurred with one user. Other existing and new users didn't have this problem. By way of diagnostics, I started renaming various directories and I even moved my entire home directory and replaced it with a blank one, but the corrupt menu remained. I even, as root, deleted myself and arose, phoenix-like as a new user with the same name, but a brand new home directory, and I still got the same problem. But I don't have the problem any more because I deleted my /var/tmp/kdecache-$USER (while not logged into a kde session). I would assume that the cached ksycoca or ksycocastamp was the culprit. What should be done: 1. Fix the bug(s) that cause the corruption. 2. Allow kmenuedit or KDE to purge a corrupt version of the kmenu from kde's caches so that end-users do not have to mess about with consoles or the /var directory. Normally you should be able to solve any problem with a particular user's account by changing/deleting something in $HOME, just as you can usually solve problems on a Mac by deleting the preferences file. If you can't rely on doing that then you are heading for a nightmare like the Windows registry which is as impenetrable to most users as an accident in a jigsaw puzzle factory. This bug was a serious problem for me that took me weeks to sort out, primarily because deleting a cache file in /var, a directory I rarely even look at, was not at all an obvious thing to do.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!