| Summary: | Contents of entire folders unexpectedly deleted after edits | ||
|---|---|---|---|
| Product: | [Applications] kmenuedit | Reporter: | Tristan Miller <psychonaut> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | jay, seorge |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Tristan Miller
2003-10-23 12:01:26 UTC
After hours of searching for what I thought would be the user-customized menu files in ~/.kde/share/applnk, I find that they have been given a new format and moved to the file ~/.config/menus/applications-kmenuedit and the directory ~/.local/share/applications. Deleting these restored my K Menu to the default settings. I'm wondering now if this is some SuSE-engineered nonsense, and whether I should have filed a bug report with them instead. Please let me know either way. .local and .config is the new standard for this stuff and will appear in KDE 3.2. It has been backported to SUSE 9.0. What surprises me is that you say that you upgraded to 8.2. If the KDE 3.1.4 that you use uses .local and .config then that is clearly a KDE version intended for SUSE 9.0 and not for 8.2 Please clearify which SUSE version you are using and from where you obtained the KDE version that you are using. Apologies for the thinko; as is evident from the second sentence, I meant to write that I upgraded from 8.1 to 9.0, not 8.1 to 8.2. I'm currently using SuSE 9.0 with KDE 3.1.4. After starting fresh with a new account, I find I can add, move, and delete K menu items without too much hassle. (There are still some occurrences of Bug #53476 but nothing serious like entire folders appearing empty.) Evidently the problem lay in converting the old K Menu. I want to inform I use SuSE 8.2 and KDE 3.2.0. After some changes I had the same problem as described and found by accident this .local folder to. Because I found the "bad setting" there I renamed that folder and found it reapearing after doing the same change. However now it was working good and the old .local had wrong info in the xyz.desktop file. The worse thing is SuSE made already a mess with there own menu. Now I understand there are 3 menus involved. SuSE, KDE old and KDE new and that explains why i found some entries 3 times. If I want to associate a file to a program I get the available programs from /opt/kde/share/applnk or ~/.kde/share/applnk (in the old 3.1.4 and are the Kmenu entries) and are stored in ~/.kde/share/mimetypes/<type>. If these applnk go to .local and .config it explains another problem why some associates not working anymore. I wonder if there exist a menu layout in the KDE orginal designed way. See http://bugs.kde.org/show_bug.cgi?id=53476#c9 For the mimetypes, services and servicetype it is also handy. I can also say I take care of not installing SuSE 9.0 packs but must confess I did not install kdenetwork3-chat. It comes out the 8.2 upgrade but in the distribution it is 9.0! desktop-data-suse.rpm stores in '/etc/xdg/menus' for suse 9.0 the menu stuff. They refer to the freedesktop update but this is different as KDE is doing. Anyway SuSE is intercepting the build of K-menu and makes the mess bigger in it Do you have a menu named "SuSE" or "KDE"? I discovered a bug that can cause problems in that case. Not in my case, no. No menus named "SuSE" or "KDE". Now using KDE 3.3.1. Sometimes this bug still occurs when I do a lot of menu editing. However, the "deleted" items magically reappear upon reboot. Perhaps it's a caching issue. *** Bug 108259 has been marked as a duplicate of this bug. *** *** Bug 200400 has been marked as a duplicate of this bug. *** Old bug report and can't reproduce using KDE SC 4.9. Feel free to reopen the report if the problem still exists in recent version. |